From: Jes Sorensen <jes@sunsite.dk>
To: "Torrey Hoffman" <Torrey.Hoffman@myrio.com>
Cc: "Stevie O" <stevie@qrpff.net>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.20: pci-scan+natsemi & Device or resource busy
Date: 20 Feb 2002 15:10:23 +0100 [thread overview]
Message-ID: <d3vgcs6y7k.fsf@lxplus050.cern.ch> (raw)
In-Reply-To: <D52B19A7284D32459CF20D579C4B0C0211CB45@mail0.myrio.com>
In-Reply-To: "Torrey Hoffman"'s message of "Mon, 28 Jan 2002 10:22:22 -0800"
"Torrey Hoffman" <Torrey.Hoffman@myrio.com> writes:
> You have probably learned this by now, but I haven't seen anyone
> say it on the list, so I'll summarize...
>
> The 2.2.x kernels did not come with drivers for the natsemi. The
> Donald Becker / Scyld add-on drivers were much better than nothing,
> and we were grateful to have them, but they don't work reliably for
> our hardware. We are using motherboards with a soldered-on natsemi
> chip, not the Netgear FA-311. We did hack up a version of the
> driver that worked for us under 2.2.19, and you can get it from
> www.myrio.com/opensource if you are interested.
>
> However, the 2.4.x kernels come with much improved natsemi drivers.
> These are Donald Becker's drivers, still copyright by him, but have
> been updated a lot for 2.4 with new PCI code and lots of bugfixes.
I ran into the same problem with the natsemi driver in 2.2.x (and
rtl8139 as well). I gave up trying to fix the 2.2 drivers and instead
ended up backporting the 2.4.x drivers to 2.2.x which seems to behave
much better.
You can find the backported drivers at
http://www.wildopensource.com/proj/download/SG_drivers.html if you
find they may be useful to you.
Cheers,
Jes
next prev parent reply other threads:[~2002-02-20 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 18:22 2.2.20: pci-scan+natsemi & Device or resource busy Torrey Hoffman
2002-02-20 14:10 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-26 23:37 Stevie O
2002-01-27 0:07 ` Jeff Garzik
2002-01-27 2:06 ` Stevie O
2002-01-27 2:13 ` Stevie O
2002-01-27 13:22 ` Daniel J Blueman
2002-01-28 4:48 ` J Sloan
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=d3vgcs6y7k.fsf@lxplus050.cern.ch \
--to=jes@sunsite.dk \
--cc=Torrey.Hoffman@myrio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stevie@qrpff.net \
/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