From: Meelis Roos <mroos@linux•ee>
To: Grant Grundler <grundler@parisc-linux•org>
Cc: Jeff Garzik <jeff@garzik•org>,
cebbert@redhat•com, netdev@vger•kernel.org
Subject: Re: [patch] NET: remove support for Davicom 9102 from the Tulip driver
Date: Mon, 7 Apr 2008 17:28:03 +0300 (EEST) [thread overview]
Message-ID: <Pine.SOC.4.64.0804071726210.29033@math.ut.ee> (raw)
In-Reply-To: <20080404232650.GE27826@colo.lackof.org>
> jeff and davem already answered the basic SROM/MAC address issue.
> Patches to fix this are associated with
> http://bugzilla.kernel.org/show_bug.cgi?id=9106
> >> I happent to have a Sun Fire V100 with 2 Davicom NICs (1282:9102 (rev
> >> 31)).
> >> tulip driver works for them, dmfe doesn't.
>
> This experience doesn't agree with the bug report.
> Meelis, can you please take a look at the bug report and add comments?
Comments added.
> We tried (b) but didn't get it working on V100 previously.
> Several patches are attached to the bug report.
There was one patch (for getting the MAC from OpenFirmware) but as
people reported that the Tx timeouts still happen, I didn't try it. Any
reason to try?
--
Meelis Roos (mroos@linux•ee)
next prev parent reply other threads:[~2008-04-07 14:28 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
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 [this message]
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=Pine.SOC.4.64.0804071726210.29033@math.ut.ee \
--to=mroos@linux$(echo .)ee \
--cc=cebbert@redhat$(echo .)com \
--cc=grundler@parisc-linux$(echo .)org \
--cc=jeff@garzik$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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