From: "Jim Schutt" <jaschut@sandia.gov>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>
Cc: kuznet@ms2.inr.ac.ru, "Andi Kleen" <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: tulip vs. de4x5 (was Re: Linux 2.4 Status / TODO page ...)
Date: Wed, 08 Nov 2000 10:48:58 -0700 [thread overview]
Message-ID: <3A09920A.F6F298AD@sandia.gov> (raw)
In-Reply-To: <200011031937.WAA10753@ms2.inr.ac.ru> <3A032E32.39E7B151@mandrakesoft.com>
Jeff Garzik wrote:
>
>
> de4x5 is becoming EISA-only in 2.5.x too, since its PCI support is
> duplicated now in tulip driver.
>
I've got some DEC Miatas with DECchip 21142/43 ethernet cards, and I
don't get the same link speeds when using the de4x5 and tulip drivers,
as of 2.4.0-test10. The machines are connected to a Netgear 16-port
10/100 hub. With the tulip driver the hub shows a 10 Mb/s connection;
with the de4x5 driver the hub shows a 100 Mb/s connection. In both
cases the drivers are configured into the kernel, not as modules, if
it matters.
Am I doing something wrong, or is this a known issue?
FWIW, these machines are diskless, and according to the hub they download
the kernel at 100 Mb/s. When the tulip-based kernel initializes the
card, the hub shows the link speed switching to 10 Mb/s.
from lspci -v:
00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev
30)
Flags: bus master, medium devsel, latency 255, IRQ 24
I/O ports at 8000 [size=128]
Memory at 0000000009000000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at 0000000009040000 [disabled] [size=256K]
de4x5 boot messages:
eth0: DC21143 at 0x8000 (PCI bus 0, device 3), h/w address 00:00:f8:76:3c:74,
and requires IRQ24 (provided by PCI BIOS).
de4x5.c:V0.545 1999/11/28 davies@maniac.ultranet.com
tulip boot messages:
Linux Tulip driver version 0.9.10 (September 6, 2000)
eth0: Digital DS21143 Tulip rev 48 at 0x8000, 00:00:F8:76:3C:74, IRQ 24.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2)
block.
eth0: Index #2 - Media 10base2 (#1) described by a 21142 Serial PHY (2) block.
eth0: Index #3 - Media AUI (#2) described by a 21142 Serial PHY (2) block.
eth0: Index #4 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth0: MII transceiver #5 config 2000 status 784b advertising 01e1.
-- Jim
-----
James A. Schutt
jaschut@sandia.gov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001103202911.A2979@gruyere.muc.suse.de>
2000-11-03 19:37 ` Linux 2.4 Status / TODO page (Updated as of 2.4.0-test10) kuznet
2000-11-03 21:29 ` Jeff Garzik
2000-11-04 19:41 ` kuznet
2000-11-06 9:10 ` Jeff Garzik
2000-11-06 17:45 ` kuznet
2000-11-08 17:48 ` Jim Schutt [this message]
2000-11-03 22:01 ` Bill Wendling
2000-11-03 22:30 ` Jeff Garzik
2000-11-03 23:41 ` Andi Kleen
2000-11-03 23:57 ` Jeff Garzik
2000-11-04 9:04 ` Andi Kleen
2001-01-07 1:48 ` David C. Davies
2001-01-07 2:14 ` David C. Davies
2000-11-04 0:19 ` Alan Cox
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=3A09920A.F6F298AD@sandia.gov \
--to=jaschut@sandia.gov \
--cc=ak@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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).