Re: PCI device search.

From: Stelian Pop (stelian.pop@fr.alcove.com)
Date: Sat Oct 13 2001 - 07:51:00 EST

Next message: Keith Owens: "Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck"
Previous message: Keith Owens: "Corrupt ext2/ext3 directory entries not recovered by e2fsck"
In reply to: Jeff Garzik: "Re: PCI device search."
Next in thread: Jeff Garzik: "Re: PCI device search."
Reply: Jeff Garzik: "Re: PCI device search."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Oct 12, 2001 at 04:15:54PM -0500, Jeff Garzik wrote:

> > I'd say 1. If a device is hotpluggable or not does not matter. For
> > 2.5, the boot process will be able to load modules for all PCI
> > devices seen in the system. In order for that to happen, they need to
> > use the MODULE_DEVICE structure and the 2.4 pci driver subsystem.
>
> I'd say 1.5. :) For the "newer hardware" consider using the PCI host
> bridge or ISA bridge for your "container" PCI device.

You mean putting PCI_CLASS_BRIDGE_PCI as pattern in the pci
search table, yes ?

Thanks.

Stelian.

-- 
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|
-
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: Keith Owens: "Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck"
Previous message: Keith Owens: "Corrupt ext2/ext3 directory entries not recovered by e2fsck"
In reply to: Jeff Garzik: "Re: PCI device search."
Next in thread: Jeff Garzik: "Re: PCI device search."
Reply: Jeff Garzik: "Re: PCI device search."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:48 EST