From: Erik Mouw <mouw@nl.linux.org>
To: netdev@vger.kernel.org
Subject: Support for Intel 82562V-2?
Date: Mon, 6 Aug 2007 18:38:19 +0200 [thread overview]
Message-ID: <20070806163819.GA18130@gateway.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
Hi,
Just got a brand new Dell Vostro and it appears to have an unsupported
Intel network card:
00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network Connection (rev 02)
Subsystem: Dell Unknown device 0238
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 10
Region 0: Memory at fdfc0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at fdfff000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at fe00 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Vendor Specific Information
00: 86 80 c0 10 07 00 10 00 02 00 00 02 00 00 00 00
10: 00 00 fc fd 00 f0 ff fd 01 fe 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 38 02
30: 00 00 00 00 c8 00 00 00 00 00 00 00 0a 01 00 00
The e100 driver doesn't recognise it and the "old" eepro100 also
doesn't. Would it be enought to add the PCI ID to one of these drivers
to get the card supported?
Erik
--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-08-06 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 16:38 Erik Mouw [this message]
2007-08-06 17:54 ` Support for Intel 82562V-2? Allan, Bruce W
2007-08-06 19:54 ` Erik Mouw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070806163819.GA18130@gateway.home \
--to=mouw@nl.linux.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox