netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alan@linux.intel.com
Cc: paul.gortmaker@windriver.com, linux@rainbow-software.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver.
Date: Sat, 19 May 2012 18:33:27 -0400 (EDT)	[thread overview]
Message-ID: <20120519.183327.201650385299478436.davem@davemloft.net> (raw)
In-Reply-To: <20120519133038.282d0a7d@bob.linux.org.uk>

From: Alan Cox <alan@linux.intel.com>
Date: Sat, 19 May 2012 13:30:38 +0100

> 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.

I don't think ISA is ever going to be something we can completely
eradicate.

Bits of ISA'ness show up everywhere, from random PC southbridges
to specialized busses shipped on 64-bit sparcs for 8-bit devices
like floppies and serial ports.

Therefore, unlike MCA, ISA is more of a kind of entity we'll have to
eradicate piecemeal I think.

  reply	other threads:[~2012-05-19 22:35 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
2012-05-19 22:33       ` David Miller [this message]
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=20120519.183327.201650385299478436.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alan@linux.intel.com \
    --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).