More NIC-related queries,
Under the 2.4.13 kernel, the 3c59x.o driver misdetects my 3c980 as a 3c982
(the dual port version of what I assume is the same card):
3c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html
00:09.0: 3Com PCI 3c982 Dual Port Server Cyclone at 0xdc00. Vers LK1.1.16
Here is the output of lspci -v:
00:09.0 Ethernet controller: 3Com Corporation: Unknown device 9805 (rev 78)
Subsystem: 3Com Corporation: Unknown device 1000
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at dc00 [size=128]
Memory at db000000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
It all seems to work fine, but I was wondering if this might cause a
hiccup anywhere? 2.2.19 identified my card correctly, and I have some
earlier 3c980 models in another box still running 2.2.19, which get
detected correctly too:
00:0a.0 Class 0200: 10b7:9800
Subsystem: 10b7:9800
Flags: bus master, medium devsel, latency 32, IRQ 17
I/O ports at d880
Memory at efffaf80 (32-bit, non-prefetchable)
Expansion ROM at effc0000 [disabled]
Capabilities: [dc] Power Management version 1
Cheers
Matt
--
"Phase plasma rifle in a forty-watt range?"
"Only what you see on the shelves, buddy."
Matt wrote:
>
> More NIC-related queries,
>
> Under the 2.4.13 kernel, the 3c59x.o driver misdetects my 3c980 as a 3c982
> (the dual port version of what I assume is the same card):
>
> 3c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html
> 00:09.0: 3Com PCI 3c982 Dual Port Server Cyclone at 0xdc00. Vers LK1.1.16
>
> Here is the output of lspci -v:
>
> 00:09.0 Ethernet controller: 3Com Corporation: Unknown device 9805 (rev 78)
> Subsystem: 3Com Corporation: Unknown device 1000
> Flags: bus master, medium devsel, latency 32, IRQ 10
> I/O ports at dc00 [size=128]
> Memory at db000000 (32-bit, non-prefetchable) [size=128]
> Expansion ROM at <unassigned> [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
>
> It all seems to work fine, but I was wondering if this might cause a
> hiccup anywhere? 2.2.19 identified my card correctly, and I have some
> earlier 3c980 models in another box still running 2.2.19, which get
> detected correctly too:
>
No, that's OK - it's just the identification string which is
incorrect. I was "updating" the ID strings from the latest Becker
driver and one of us got it wrong...