From: john slee <indigoid@higherplane.net>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Etherworks3 driver now obsolete?
Date: Sat, 3 Feb 2001 23:38:28 +1100 [thread overview]
Message-ID: <20010203233828.A32071@higherplane.net> (raw)
In-Reply-To: <200102010822.f118Mlu02001@gate.dodgy.net.au> <Pine.LNX.3.96.1010203034048.26992C-100000@mandrakesoft.mandrakesoft.com>
In-Reply-To: <Pine.LNX.3.96.1010203034048.26992C-100000@mandrakesoft.mandrakesoft.com>; from jgarzik@mandrakesoft.mandrakesoft.com on Sat, Feb 03, 2001 at 03:42:48AM -0600
On Sat, Feb 03, 2001 at 03:42:48AM -0600, Jeff Garzik wrote:
> On Thu, 1 Feb 2001, Darren Tucker wrote:
> > I decided to try a shiny new 2.4.0 kernel but I couldn't configure the driver
> > for my etherworks3 ISA ethernet card (AMD K6III PC hardware).
> >
> > A bit of grepping showed that it only appears if CONFIG_OBSOLETE is defined
> > but nothing in the configuration tools seems to set it (at least for i386).
>
> If you are willing to be a target^H^H^Htester, then I can probably whip
> up a patch to fix it.
i have two ewrk3 cards here. if you want stuff tested that can
certainly be arranged, as i'd like to use them. (i used them with 2.2,
they worked very well)
unfortunately can't test both cards in one machine until i install
linux on a box with more than one isa slot. maybe a project for
tomorrow :-)
j.
-
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/
prev parent reply other threads:[~2001-02-03 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 8:22 Etherworks3 driver now obsolete? Darren Tucker
2001-02-01 10:54 ` Alan Cox
2001-02-03 9:42 ` Jeff Garzik
2001-02-03 12:38 ` john slee [this message]
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=20010203233828.A32071@higherplane.net \
--to=indigoid@higherplane.net \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--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