From: Martin Costabel <costabel@wanadoo.fr>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Request for Tulip 2.2.x testing...
Date: Sat, 25 Mar 2000 02:06:00 +0100 [thread overview]
Message-ID: <38DC10F8.89ED2074@wanadoo.fr> (raw)
In-Reply-To: 38DA7CF0.BC2E49D9@mandrakesoft.com
HI,
I did some testing with both versions. They both work for me in the same
way. The only difference I can see is one more line in /var/log/messages
when I start the patched module. The unpatched one gives me
kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
kernel: eth0: Digital DC21041 Tulip rev 33 at 0x400, 00:00:C5:47:6A:7C,
IRQ 25.
kernel: eth0: 21041 Media table, default media 0800 (Autosense).
kernel: eth0: 21041 media #0, 10baseT.
kernel: eth0: 21041 media #4, 10baseT-FD.
The patched one gives an additional line
kernel: eth0: 21143 10baseT link beat good.
Otherwise I see no difference in performance between the two (nor with
the de4x5 driver which I am normally using).
Do you need more information?
# cat /proc/version
Linux version 2.2.15-pre15 (root@chezmoi) (gcc version 2.95.2 19991024
(release/franzo)) #22 Sat Mar 25 00:46:00 CET 2000
--
Martin
Jeff Garzik wrote:
>
> Hi all!
>
> I was wondering if I could find anyone on here with a Tulip 21041 chip
> that could do some simple testing under 2.2.15-pre15?
>
> Questions for which answers are sought:
>
> Does tulip.c work with your 21041 chip unmodified?
> If yes, does the below patch break the tulip driver?
> If no, does the below patch get your 21041 working again?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-03-25 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-23 20:22 Request for Tulip 2.2.x testing Jeff Garzik
2000-03-25 1:06 ` Martin Costabel [this message]
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=38DC10F8.89ED2074@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=jgarzik@mandrakesoft.com \
--cc=linuxppc-dev@lists.linuxppc.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).