Hi,
having the various constants in pci_ids.h is a really good thing for
grepping through the kernel source. And if they were used, it would be
even better (if you e.g. are looking for which driver claims an SIImage
3112 card...). However, the sata_xxx.c files in the drivers/scsi
directory are
Henning Schmiedehausen wrote:
Hi,
having the various constants in pci_ids.h is a really good thing for
grepping through the kernel source. And if they were used, it would be
even better (if you e.g. are looking for which driver claims an SIImage
3112 card...). However, the sata_xxx.c files in the
Hi Jeff,
then what sense does it make to have pci_ids.h at all?
Regards
Henning
On Sun, 2005-02-27 at 13:08 -0500, Jeff Garzik wrote:
Henning Schmiedehausen wrote:
Hi,
having the various constants in pci_ids.h is a really good thing for
grepping through the
Let me rephrase:
What sense does it make to have PCI_VENDOR_ID and PCI_DEVICE_ID
constants if using them is optional/discouraged?
Regards
Henning
On Sun, 2005-02-27 at 14:52 -0500, Jeff Garzik wrote:
Henning Schmiedehausen wrote:
Hi Jeff,
then what sense does
On Sun, Feb 27, 2005 at 09:05:06PM +0100, Henning Schmiedehausen wrote:
Let me rephrase:
What sense does it make to have PCI_VENDOR_ID and PCI_DEVICE_ID
constants if using them is optional/discouraged?
Only PCI_DEVICE_ID_xxx is discouraged. Not PCI_VENDOR_ID_xxx.
Jeff
-
To
Recently, Mark Hahn wrote:
getting 25 MB/s out of older-generation udma33 controllers isn't bad;
I don't remember ever getting better than about 28 out of 33, regardless
of which chipset/memory/cpu.
...
Thanks Mark.
Using gcc-2.95.3 instead of gcc-3.3.4 cut kernel compile time
for 'time make
