Re: Better device probe values

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 02/23/05

  • Next message: Garance A Drosihn: "Bug in #! processing - One More Time" 
    To: Warner Losh <imp@bsdimp.com>
Date: Wed, 23 Feb 2005 16:38:46 -0500

    On Wednesday 23 February 2005 03:50 pm, Warner Losh wrote:
    > > Several typos, but that's minor. Sounds ok to me. Note that I think
    > > BUS_PROBE_GENERIC might not really be enough though (PCI bridge drivers
    > > are actually somewhat tricky, on x86 for PCI-PCI you have ACPI, PCIBIOS,
    > > MPTable, and generic for example), but for more tricky cases we can still
    > > use numeric values.
    >
    > Well, on x86 we have 3 different pci busses, but they aren't in any
    > more complicated a heirarchy than 'generic' or something that replaces
    > 'generic.' You won't have PCIBIOS and MPTable fighting for control of
    > a system, will you?

    Yes, you do. MPTable is just preferred to PCIBIOS, and ACPI is preferred to
    PCIBIOS. MPTable probably should be preferred to ACPI though (since
    MPTable's probe is only going to succeed if we are using the MPTable to
    enumerate APICs, in which case we can't trust ACPI's interrupt routing)
    though I might have this one wrong. All three are preferred over the generic
    bridge driver. Actually, the ACPI vs. MPTable case is probably a bit more
    muddy than that. It's probably wrong now. We shouldn't ever use those two
    together, but I'm not sure how best to do that. I don't think that is
    currently an issue though because I don't know of any machines that include
    an MP Table and ACPI but don't include an MADT table in ACPI. 

    -- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Garance A Drosihn: "Bug in #! processing - One More Time"

    Relevant Pages

    • Re: Better device probe values
      ... On Wednesday 23 February 2005 03:50 pm, Warner Losh wrote: ... >> Several typos, but that's minor. ... MPTable is just preferred to PCIBIOS, and ACPI is preferred to ...
      (freebsd-arch)
    • Re: HEADS UP! 6.0-RELEASE coming
      ... On Mon, 31 Oct 2005, Warner Losh wrote: ... >> Well, in my case at least, what ACPI says about the sio resources is ... >> Linux nor Solaris required users to read the ACPI 2.0 spec to get their ... I could have sworn that the AML that you'd posted a while ago ...
      (freebsd-stable)
    • Re: FDC/ACPI/GEOM problems
      ... On Tue, 2004-09-28 at 16:04, M. Warner Losh wrote: ... I have spent a little time today looking at this problem in more detail. ... Apparently systems only hang with ACPI ...
      (freebsd-current)
    • Re: HEADS UP! 6.0-RELEASE coming
      ... Warner Losh wrote: ... > Right now acpi tells us there's a device, ... > specific port that comes out the back. ... Well, in my case at least, what ACPI says about the sio resources is ...
      (freebsd-stable)
    • Re: HEADS UP: PCI Chnages
      ... : On Fri, 23 Apr 2004, M. Warner Losh wrote: ... :>: We probably just need to reprogram the PCI link devices on resume. ... Or are your comments just for the!acpi case? ... I was consuing PCI link devices and PCI devices. ...
      (freebsd-current)