Subject: Ethernet problems on PWS 500au solved / de(4) vs. tlp(4)
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 10/03/2001 11:31:40
On 2 Oct, I wrote:
> but the kernel can't get a single packet out of the physical interface.
[when using de(4) for the PWS 500au build in 21143]
It seams that I solved the problem. When I use the tlp(4) driver it
tlp* at pci? dev ? function ? # DECchip 21x4x and clones
tlp0 at pci0 dev 3 function 0: DECchip 21143 Ethernet, pass 3.0
tlp0: interrupting at dec 550 irq 0
tlp0: DEC , Ethernet address 00:00:f8:75:99:6a
nsphy0 at tlp0 phy 5: DP83840 10/100 media interface, rev. 1
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
tlp0: 10baseT, 10baseT-FDX, 10base2, 10base5
I got 950kB/s out of my old coax wire. So I asume de(4) had problems
with the phy of the build in 21143.
The tlp driver does not match the DECchip 21040, 21041, 21140, 21142, and
21143 chips on the PCI bus by default. That is because another driver,
de, which is more functional in some circumstances, exists for them.
Now comes the question to mind: What is better in de(4) than tlp(4)?