linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Request for Tulip 2.2.x testing...
@ 2000-03-23 20:22 Jeff Garzik
  2000-03-25  1:06 ` Martin Costabel
  0 siblings, 1 reply; 2+ messages in thread
From: Jeff Garzik @ 2000-03-23 20:22 UTC (permalink / raw)
  To: linuxppc-dev

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

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?

Thanks!

	Jeff




--
Jeff Garzik              | Tact is the ability to tell a man
Building 1024            | he has an open mind when he has a
MandrakeSoft, Inc.       | hole in his head.  (-random fortune)

[-- Attachment #2: tulip-2.2.15p15.patch --]
[-- Type: text/plain, Size: 771 bytes --]

Index: tulip.c
===================================================================
RCS file: /g/cvslan/linux_2_2/drivers/net/tulip.c,v
retrieving revision 1.1.1.6
diff -u -r1.1.1.6 tulip.c
--- tulip.c	2000/01/22 13:52:13	1.1.1.6
+++ tulip.c	2000/03/21 17:22:08
@@ -420,7 +420,7 @@
 {0,0,0,16,  3,19,16,24,  27,4,7,5, 0,20,23,20 };
 static u8 t21040_csr13[] = {2,0x0C,8,4,  4,0,0,0, 0,0,0,0, 4,0,0,0};
 /* 21041 transceiver register settings: 10-T, 10-2, AUI, 10-T, 10T-FD*/
-static u16 t21041_csr13[] = { 0xEF01, 0xEF09, 0xEF09, 0xEF01, 0xEF09, };
+static u16 t21041_csr13[] = { 0xEF05, 0xEF0D, 0xEF0D, 0xEF05, 0xEF05, };
 static u16 t21041_csr14[] = { 0xFFFF, 0xF7FD, 0xF7FD, 0x7F3F, 0x7F3D, };
 static u16 t21041_csr15[] = { 0x0008, 0x0006, 0x000E, 0x0008, 0x0008, };


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Request for Tulip 2.2.x testing...
  2000-03-23 20:22 Request for Tulip 2.2.x testing Jeff Garzik
@ 2000-03-25  1:06 ` Martin Costabel
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Costabel @ 2000-03-25  1:06 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: linuxppc-dev


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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-03-25  1:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-03-23 20:22 Request for Tulip 2.2.x testing Jeff Garzik
2000-03-25  1:06 ` Martin Costabel

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).