From: Chuck Ebbert <cebbert@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Netdev <netdev@vger.kernel.org>
Subject: [patch] NET: remove support for Davicom 9102 from the Tulip driver
Date: Wed, 02 Apr 2008 18:46:57 -0400 [thread overview]
Message-ID: <47F40CE1.2080708@redhat.com> (raw)
NET: remove support for Davicom 9102 from the Tulip driver
We have two reports that agree the tulip driver doesn't work for
the Davicom 9102 (PCI id 1282:9102). The dmfe driver does work
and also claims the same PCI ID.
https://bugzilla.redhat.com/show_bug.cgi?id=277731
https://bugzilla.redhat.com/show_bug.cgi?id=236928
Signed-off-by: Chuck Ebbert <cebbert@redhat.com>
---
drivers/net/tulip/tulip_core.c | 1 -
1 file changed, 1 deletion(-)
--- linux-2.6.24.noarch.orig/drivers/net/tulip/tulip_core.c
+++ linux-2.6.24.noarch/drivers/net/tulip/tulip_core.c
@@ -231,7 +231,6 @@ static struct pci_device_id tulip_pci_tb
{ 0x11F6, 0x9881, PCI_ANY_ID, PCI_ANY_ID, 0, 0, COMPEX9881 },
{ 0x8086, 0x0039, PCI_ANY_ID, PCI_ANY_ID, 0, 0, I21145 },
{ 0x1282, 0x9100, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DM910X },
- { 0x1282, 0x9102, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DM910X },
{ 0x1113, 0x1216, PCI_ANY_ID, PCI_ANY_ID, 0, 0, COMET },
{ 0x1113, 0x1217, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MX98715 },
{ 0x1113, 0x9511, PCI_ANY_ID, PCI_ANY_ID, 0, 0, COMET },
next reply other threads:[~2008-04-02 22:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 22:46 Chuck Ebbert [this message]
2008-04-04 5:46 ` [patch] NET: remove support for Davicom 9102 from the Tulip driver Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2008-04-03 9:10 Meelis Roos
2008-04-04 21:38 ` Jeff Garzik
2008-04-04 22:02 ` David Miller
2008-04-04 22:06 ` Jeff Garzik
2008-04-04 22:28 ` David Miller
2008-04-04 23:26 ` Grant Grundler
2008-04-07 14:28 ` Meelis Roos
2008-04-09 15:54 ` Grant Grundler
2008-04-04 8:56 Meelis Roos
2008-04-04 19:43 ` David Miller
2008-04-04 21:27 ` Jeff Garzik
2008-04-04 21:59 ` Jeff Garzik
2008-04-04 22:05 ` David Miller
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=47F40CE1.2080708@redhat.com \
--to=cebbert@redhat.com \
--cc=jeff@garzik.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;
as well as URLs for NNTP newsgroup(s).