From: Jeff Garzik <jeff@garzik.org>
To: Meelis Roos <mroos@linux.ee>
Cc: cebbert@redhat.com, netdev@vger.kernel.org,
Grant Grundler <grundler@parisc-linux.org>
Subject: Re: [patch] NET: remove support for Davicom 9102 from the Tulip driver
Date: Fri, 04 Apr 2008 17:38:06 -0400 [thread overview]
Message-ID: <47F69FBE.3020308@garzik.org> (raw)
In-Reply-To: <Pine.SOC.4.64.0804031209540.2017@math.ut.ee>
Meelis Roos wrote:
> CE> We have two reports that agree the tulip driver doesn't work for
> CE> the Davicom 9102 (PCI id 1282:9102). The dmfe driver does work
> CE> and also claims the same PCI ID.
>
> NAK, dmfe does not work on some Sparc64 machines but tulip does.
>
> I happent to have a Sun Fire V100 with 2 Davicom NICs (1282:9102 (rev
> 31)).
> tulip driver works for them, dmfe doesn't. Tried with 2.6.25-rc7, first
> it
> gets MAC addresses all zeroed and second, it only results in Tx
> timeouts.
At the very least, it sounds like some SROM parsing problems on dmfe's
part -- assuming a standard SROM when sparc64 provides a more
complicated one.
> This issue was debugged somemonths ago on sparclinux mailing list. DaveM
> fixed some bugs IIRC but it still does not work.
URL to more info?
Overall we need someone to either (a) work on tulip to get it working
with popular 9102's, or (b) work on dmfe to get it working on sparc64...
Installers and users will continue to be confused by the present
situation, where the same PCI ID is claimed by two different drivers,
and you just sorta haveta "know" which one is right.
Jeff
next prev parent reply other threads:[~2008-04-04 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 9:10 [patch] NET: remove support for Davicom 9102 from the Tulip driver Meelis Roos
2008-04-04 21:38 ` Jeff Garzik [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2008-04-02 22:46 Chuck Ebbert
2008-04-04 5:46 ` Jeff Garzik
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=47F69FBE.3020308@garzik.org \
--to=jeff@garzik.org \
--cc=cebbert@redhat.com \
--cc=grundler@parisc-linux.org \
--cc=mroos@linux.ee \
--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).