From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Joshua Schmidlkofer <menion@srci.iwpsd.org>,
Thomas Zehetbauer <thomasz@hostmaster.org>,
linux-kernel@vger.kernel.org
Subject: Re: tulip driver still broken
Date: Mon, 30 Jul 2001 17:30:04 -0600 [thread overview]
Message-ID: <20010730173004.A20131@mail.harddata.com> (raw)
In-Reply-To: <01073016571903.25803@widmers.oce.srci.oce.int> <Pine.LNX.3.96.1010730180814.27870D-100000@mandrakesoft.mandrakesoft.com>
In-Reply-To: <Pine.LNX.3.96.1010730180814.27870D-100000@mandrakesoft.mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, Jul 30, 2001 at 06:09:33PM -0500
On Mon, Jul 30, 2001 at 06:09:33PM -0500, Jeff Garzik wrote:
> On Mon, 30 Jul 2001, Joshua Schmidlkofer wrote:
> > I am afraid of post these days. However, I must comment that I too am having
> > trouble with the tulip driver, on several SMC nic's that use the DEC
> > chipset. I tried mii_tool, with no success.
> >
> > I have just been copying the tulip driver from 2.4.4 forward... because I
> > don't have enough time to try and create an intelligent error report.
>
> Thanks for the report!
>
> Currently there are problems with 21041 old chipsets, which include SMC
> and several other cards.
Hm, I reported few times problems with DS21143 Tulip rev 65, which is
not exactly old, and with anything above tulip-0.9.14, and did not get
back even a half line acknowledment not mentioning annoucements of fixes.
I also posted mii-diag output from a card in working and not working
state.
I have to admit, though, that I did not test that really recently.
RSN...
Michal
next prev parent reply other threads:[~2001-07-30 23:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 22:19 tulip driver still broken Thomas Zehetbauer
2001-07-30 22:57 ` Joshua Schmidlkofer
2001-07-30 23:09 ` Jeff Garzik
2001-07-30 23:30 ` Michal Jaegermann [this message]
2001-08-01 14:36 ` Patrick Cole
2001-07-31 13:23 ` Chris Friesen
2001-07-31 18:00 ` Jeff Garzik
2001-08-01 15:51 ` Ben Greear
2001-08-01 16:45 ` joseph.bueno
2001-08-01 21:14 ` Justin Guyett
2001-08-02 7:35 ` joseph.bueno
2001-08-01 21:52 ` Jeff Garzik
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=20010730173004.A20131@mail.harddata.com \
--to=michal@harddata.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menion@srci.iwpsd.org \
--cc=thomasz@hostmaster.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