erm..  0x10B7 is 3Com.  I suspect you've dropped a bit in the
device's EEPROM and it's loading the wrong manufacturer ID
into the PCI config registers.
Grab vortex-diag from http://www.scyld.com/diag/index.html and
run `vortex-diag -aaee'.  Look at the EEPROM section.  I get:
EEPROM contents (64 words, offset 0x30):
 0x000: 2978 6056 0040 8060 0040 0000 0000 0080
 0x008: 0000 0000 0000 0000 0000 0000 0000 0000
 0x010: 0000 0000 0000 0000 0000 0000 10b7 6356
 0x018: 0000 0000 0000 0000 0000 0000 0000 0a0a
 0x020: ff29 2829 0008 0000 0000 0000 0000 0000
 0x028: 0000 ff01 0000 0000 0000 0000 0000 0000
 0x030: 0000 8642 002e 6056 0061 0009 0000 6d50
 0x038: 2970 0009 0000 8642 002e 0010 0000 00aa
See the 10b7 at offset 0x016?  That's the manufacturer ID.
You _might_ be able to fix it with 3com's DOS-based setup
tool ftp://ftp.3com.com/pub/nic/3c90x/3c90xx2.exe or you
can just run with your patch and be happy ;)
-
-
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/