From: Darren Tucker <dtucker@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: Etherworks3 driver now obsolete?
Date: Thu, 1 Feb 2001 19:22:46 +1100 (EST) [thread overview]
Message-ID: <200102010822.f118Mlu02001@gate.dodgy.net.au> (raw)
Hi all.
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).
CONFIG_OBSOLETE is checked for by Config.in for a couple of drivers (net and
char), but the only place it seems to be defined is for the ARM architecture.
Is this deliberate? Are some of the older drivers to be phased out?
Should there be a "bool 'Prompt for obsolete code/drivers' CONFIG_OBSOLETE"
in the config.in for other architectures, too?
Thanks.
-Daz.
-
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/
next reply other threads:[~2001-02-01 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 8:22 Darren Tucker [this message]
2001-02-01 10:54 ` Etherworks3 driver now obsolete? Alan Cox
2001-02-03 9:42 ` Jeff Garzik
2001-02-03 12:38 ` john slee
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=200102010822.f118Mlu02001@gate.dodgy.net.au \
--to=dtucker@zip.com.au \
--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