Re: 2.6.0-test1: include/linux/pci.h inconsistency?

[Rahul Karnik <rahul@genebrew.com>]

Jeff Garzik wrote:

> I really would love some person with an nForce NIC to try and use
> amd8111e.c or pcnet32.c with their nForce2 NIC, and see what happens.

Added the IDs (0066 in my case, one of three according to Nvidia 
sources) to pci_ids.h and to the drivers. Assuming that is all that is 
needed, here's what happened:

amd8111e.c:

PCI: Setting latency timer of device 0000:00:04.0 to 64
eth1: AMD-8111e Driver Version: 3.0.3
eth1: [ Rev 0 ] PCI 10/100BaseT Ethernet 00:00:00:00:00:00

Loaded fine, but note the incorrect MAC address.

pcnet32.c (with debug=7):

PCI: Setting latency timer of device 0000:00:04.0 to 64
pcnet32.c:v1.27b 01.10.2002 tsbogend@alpha.franken.de
PCI: Setting latency timer of device 0000:00:04.0 to 64
pcnet32: io address range already allocated
pcnet32.c:v1.27b 01.10.2002 tsbogend@alpha.franken.de
kobject_register failed for pcnet32 (-17)
Call Trace:
  [<c01ab94c>] kobject_register+0x4c/0x60
  [<c01d93d4>] bus_add_driver+0x54/0xc0
  [<c01d9891>] driver_register+0x31/0x40
  [<c01b27ef>] pci_register_driver+0x6f/0xa0
  [<fc8b8044>] pcnet32_init_module+0x44/0x9e [pcnet32]
  [<c01310ca>] sys_init_module+0x14a/0x2a0
  [<c010930b>] syscall_call+0x7/0xb

Any other likely candidates? Is there any way to probe this?

Thanks,
Rahul