From: Sven Schnelle <svens@stackframe.org>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
Arlie Davis <arlied@google.com>, Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: Bug report (with fix) for DEC Tulip driver (de2104x.c)
Date: Thu, 19 Sep 2019 22:31:32 +0200 [thread overview]
Message-ID: <20190919203132.GA9107@t470p.stackframe.org> (raw)
In-Reply-To: <f71e9773-5cfb-f20b-956f-d98b11a5d4a7@gmx.de>
Hi,
On Wed, Sep 18, 2019 at 07:56:16AM +0200, Helge Deller wrote:
> On 18.09.19 00:51, John David Anglin wrote:
> > On 2019-09-17 5:36 p.m., Arlie Davis wrote:
> >> Likewise, I'm at a loss for testing with real hardware. It's hard to
> >> find such things, now.
> > How does de2104x compare to ds2142/43? I have a c3750 with ds2142/43 tulip. Helge
> > or some others might have a machine with a de2104x.
>
> The machines we could test are
> * a C240 with a DS21140 tulip chip (Sven has one),
My C240 identifies as C240+:
[ 0.000000] model 9000/782/C240+
which has a 21143 (verified by looking at the board):
root@c240:/# lspci -kvvnn -s 00:14.0
00:14.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21142/43 [1011:0019] (rev 30)
Subsystem: Hewlett-Packard Company DECchip 21142/43 [103c:104f]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 255 (5000ns min, 10000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 23
Region 0: I/O ports at 0080 [size=128]
Region 1: Memory at f2802000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at f2f80000 [disabled] [size=256K]
Kernel driver in use: tulip
Regards
Sven
next prev parent reply other threads:[~2019-09-19 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 21:50 Bug report (with fix) for DEC Tulip driver (de2104x.c) Arlie Davis
2019-09-17 21:28 ` Andrew Lunn
2019-09-17 21:36 ` Arlie Davis
2019-09-17 22:51 ` John David Anglin
2019-09-18 5:56 ` Helge Deller
2019-09-18 13:27 ` Thomas Bogendoerfer
2019-10-03 1:29 ` Maciej W. Rozycki
2019-09-19 20:31 ` Sven Schnelle [this message]
2019-09-23 10:43 ` C8000, which is the max MTU of the built-in net card? Carlo Pisani
2019-09-23 11:42 ` John David Anglin
2019-09-20 10:43 ` Bug report (with fix) for DEC Tulip driver (de2104x.c) Thomas Bogendoerfer
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=20190919203132.GA9107@t470p.stackframe.org \
--to=svens@stackframe.org \
--cc=andrew@lunn.ch \
--cc=arlied@google.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.