Re: PNP and bus association

From: Adam Belay (ambx1_at_neo.rr.com)
Date: 01/28/05

  • Next message: Ove Kaaven: "PROBLEM: SysV semaphore race vs SIGSTOP"
    Date:	Fri, 28 Jan 2005 17:47:52 -0500
    To: Pierre Ossman <drzeus-list@drzeus.cx>
    
    

    Hi Pierre,

    The platform bus does not show the actual physical relationship either. For
    x86, ACPI is typically needed to determine this. It would be easy to bind to
    spawn pnp devices off of an ISA bridge device, attached to the pci bus, but
    whether it's the actual physical parent would be very difficult to determine
    without firmware assistance.

    At the moment the pnp bus is only showing a logical bus relationship. If we
    were to use ACPI to aid in the generation of the physical device tree, we
    could put these devices in the correct physical location.

    Thanks,
    Adam

    On Thu, Jan 27, 2005 at 10:16:50PM +0100, Pierre Ossman wrote:
    > I recently tried out adding PNP support to my driver to remove the
    > hassle of finding the correct parameters for it. This, however, causes
    > it to show up under the pnp bus, where as it previously was located
    > under the platform bus.
    >
    > Is the idea that PNP devices should only reside on the PNP bus or is
    > there some magic available to get the device to appear on several buses?
    > It's a bit of a hassle to search in two different places in sysfs
    > depending on if PNP is used or not.
    >
    > Also, the PNP bus doesn't really say that much about where the device is
    > physically connected. The other bus types usually give a hint about this.

    It's normal for ISA devices to not tell us much about their physical
    properties.

    >
    > Rgds
    > Pierre
    > -
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Ove Kaaven: "PROBLEM: SysV semaphore race vs SIGSTOP"

    Relevant Pages

    • Re: PNP and bus association
      ... >The platform bus does not show the actual physical relationship either. ... ACPI is typically needed to determine this. ... >At the moment the pnp bus is only showing a logical bus relationship. ...
      (Linux-Kernel)
    • ACPI hangs on HP 7915
      ... I'll rebuild the kernel without ACPI. ... acpi0: on motherboard ... <ACPI PCI bus> on pcib0 ... Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a35000. ...
      (freebsd-current)
    • take a lot of time to boot
      ... ACPI: PM-Timer IO Port: 0x808 ... Probing PCI hardware (bus 00) ... PCI Interrupt Link enabled at IRQ 11 ... USB Universal Host Controller Interface driver v2.2 ...
      (alt.os.linux.suse)
    • [BUG 2.6.26-rc1] scsi (or sysfs or vm?) oops in sr_probe()
      ... Driver 'sr' needs updating - please use bus_type methods ... ACPI: DMI detected: Hewlett-Packard ... PERCPU: Allocating 33552 bytes of per cpu data ... bus: 00 to node: 00 ...
      (Linux-Kernel)
    • Interrupt storm on an MS-1029 (AMD Turion 64)
      ... FreeBSD 6.1 runs very slowly out of the box on my MS-1029 AMD Turion ... Booting in safe mode and with ACPI disabled did not help. ... driver was still using irq19 and was having an interrupt storm. ... <ACPI PCI bus> on pcib0 ...
      (freebsd-questions)