ACPI 5 PCI removal

Matthew Dillon dillon at
Thu Jul 1 19:35:21 PDT 2004

:On Fri, Jul 02, 2004 at 01:52:03AM +0900, YONETANI Tomokazu wrote:
:> How "broken" is it for you by the way? And is it broken for other people
:> as well?
:I'm not sure _how_ broken exactly it is. It can't work as intended, because
:DF works still differently than FreeBSD 5 [and will be]. The reason I want
:to not include or disable it is to ensure that it doesn't cause problems
:and to avoid the clutter it generates e.g. by adding another nexus-pci
:Let me ask the question reverse, do you know of any use of this specific
:code? I can live with Matt's suggestion to switch the default meaning of
:the driver [and use a tunable in hw.acpi or so for it], but right now
:don't want to work on a patch, if I can simple skip this code with the
:same result.

    I was under the impression that the difference is related to 
    FreeBSD-5's two-pass interrupt routing code, or other changes in
    that area which we have not yet imported.

    The more I think about it, the more I think it may be presenting too
    many options to the user.  We should probably leave it in so all the
    user has to do is decide to boot with or without ACPI, then bring in
    all the FreeBSD stuff post-release.  Even the FreeBSD stuff is not likely
    to fix much relative to what we have now, but we can probably use 
    FBSD's two pass code as a springboard.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Submit mailing list