From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Request for Tulip 2.2.x testing...
Date: Thu, 23 Mar 2000 15:22:08 -0500 [thread overview]
Message-ID: <38DA7CF0.BC2E49D9@mandrakesoft.com> (raw)
[-- 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, };
next reply other threads:[~2000-03-23 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-23 20:22 Jeff Garzik [this message]
2000-03-25 1:06 ` Request for Tulip 2.2.x testing Martin Costabel
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=38DA7CF0.BC2E49D9@mandrakesoft.com \
--to=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).