From: Alan Cox <alan@linux.intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Ondrej Zary <linux@rainbow-software.org>, <davem@davemloft.net>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver.
Date: Sat, 19 May 2012 13:30:38 +0100 [thread overview]
Message-ID: <20120519133038.282d0a7d@bob.linux.org.uk> (raw)
In-Reply-To: <20120518220305.GC15256@windriver.com>
> You miss the point. We've got someone with a modern i7 machine who is
> getting confused by seeing messages from some ancient 3c501 driver,
> but he doesn't have the context to know it is ancient and the message
> is a red herring. Will it fix a distro's broken init that tries to
> modprobe everything? No. Will it help by not muddying the waters
> with meaningless printk from 3c501 that confuse users? Yes.
That seems a totally bogus reason for removing stuff. The kernel cannot
manage every possible distribution and user screw up. They have more
variety so they will always win the battle.
Removing it because nobody is running one even in a museum might be a
good reason, but then the driver still works fine.
Also btw: the 3c501 isn't all TTL it's integrated. The 3c500 is all TTL
and an amazing beast, its so big it won't fit a 16bit slot as it has to
drop down after the connector to get all the chips on.
(and yes I have a 3c500)
However I don't think this is the right way to tackle the ethernet
history situation. As with MCA we should pull *all* the real historical
interest only bits in one go so it's immediately obvious where the
break point is for all devices.
That or we'll replace confused distros and uses with confused ancient
machine owners, and the latter can be far more persistent and
irritating ;)
So should we dump ISA ?
Alan
next prev parent reply other threads:[~2012-05-19 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 17:39 [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver Paul Gortmaker
2012-05-18 18:16 ` Ondrej Zary
2012-05-18 22:03 ` Paul Gortmaker
2012-05-19 8:58 ` Ondrej Zary
2012-05-20 16:41 ` Paul Gortmaker
2012-05-21 13:42 ` David Laight
2012-05-21 18:46 ` Alan Cox
2012-05-19 12:30 ` Alan Cox [this message]
2012-05-19 22:33 ` David Miller
2012-05-20 16:08 ` Paul Gortmaker
2012-05-19 3:54 ` David Miller
2012-05-19 12:31 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2012-05-20 16:02 Emmanuel Fusté
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=20120519133038.282d0a7d@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=linux@rainbow-software.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).