[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B6F13@saturn3.aculab.com>
Date: Mon, 21 May 2012 14:42:13 +0100
From: "David Laight" <David.Laight@...LAB.COM>
To: "Paul Gortmaker" <paul.gortmaker@...driver.com>,
"Ondrej Zary" <linux@...nbow-software.org>
Cc: <davem@...emloft.net>, <netdev@...r.kernel.org>,
"Alan Cox" <alan@...ux.intel.com>
Subject: RE: [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver.
> Regardless, to answer your questions:
>
> 1) No, obviously an rm-rf of all drivers that can't probe quietly was
> not going to happen; that was never implicilty or explicitly proposed.
>
> 2) From memory while working on the 3c503 driver 15 odd years ago, it
> could probe silently and semi reliably, which was impressive
> then, given it was pre ISA-PnP. It was worlds ahead of a 3c501 card.
Probing for non-pnp ISA cards is definitely unreliable.
Maybe some of these drivers should need to be explicitly
enabled in the kernel config.
That should let people with the cards use them, without
the danger of unexpected error messages and possible
system lockups!
ISTR that the Olicom ISA-pnp token ring card would lock
the bus solid if hit by the probe for the non-pnp variant!
(or maybe it was the other way around).
I hadn't realised how bad some of the 3cxxx cards were!
I thought the 'parallel tasking' was all about starting
to tx a frame while the host was still copting it to the
tx fifo (and rx copies before end of frame), not that
it couldn't receive while the host was reading out a
packet. I was writing drivers for the amd lance at
much the same time...
(Mind you, the intel device of that era was somewhat
difficult to use as well.)
David
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists