LKML Archive on
help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <>
To: Paul Gortmaker <>
Cc:, "H. Peter Anvin" <>,
	Ingo Molnar <>,
	Thomas Gleixner <>,, Linus Torvalds <>
Subject: Re: [PATCH 3/3] x86: drop support for 1995 era EISA based platforms
Date: Tue, 20 Jan 2015 04:05:37 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 19 Jan 2015, Paul Gortmaker wrote:

> The Kconfig text says it all, with "The EISA bus saw limited use
> between 1988 and 1995 when it was made obsolete by the PCI bus."
> That means typically 486/586 CPUs in the 33-166MHz range, and
> 8-64MB of installed RAM in typical EISA machines of that era.
> With the additional cost, they were also typically rare, and not
> getting widescale deployment.
> Given that it is 20 years on since its demise, and the above specs
> might seem just barely acceptable for a wireless router today, lets
> stop forcing everyone to build EISA infrastructure and assoc. drivers
> during their routine build coverage testing for no value whatsoever.
> We'd already removed some obsolete 10Mbit EISA network drivers in
> commit bca94cffabf5c9f2399da34eab00bd534bf3735b ("drivers/net: delete
> 8390 based EISA drivers") over two years ago for the same reason.
> If we don't immediately expire EISA completely, we can at least limit
> its impact and support/testing overhead to the arch like alpha and
> parisc that are essentially frozen in time from a hardware perspective.
> Signed-off-by: Paul Gortmaker <>
> ---

 Well, I'd like to keep my x86 box up and alive, to support EISA FDDI 
equipment I maintain if nothing else -- which in particular means the 
current head version of Linux, not some ancient branch.

 Is the maintenance overhead for this stuff really that high?  The amount 
of code you're dropping here does not really impress me.  And it's almost 
exclusively APIC stuff that's straightforward and I can probably give it 
some attention too -- as you may have been aware I have some experience in 
this area, especially where older hardware is concerned.  Unfortunately my 
EISA box is UP, so I can't offer run-time validation for APIC/SMP code at 
the moment, but as I say, this is really plain stuff.

 I don't require that everyone around the planet validates EISA support of 
course -- if that is what really concerns you (quite validly, IMHO), then 
how about a configuration option instead to annotate more exotic stuff 
with, so that people who have, say, commercial interest in Linux only, can 
tick it off and care of what brings them income only?


  reply	other threads:[~2015-01-20  4:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20  3:18 [PATCH 0/3] x86: drop EISA support from x86_32 builds Paul Gortmaker
2015-01-20  3:18 ` [PATCH 1/3] x86: rename eisa_set_level_irq to elcr_set_level_irq Paul Gortmaker
2015-01-20  3:18 ` [PATCH 2/3] x86: delete EISA_VLB_PRIMING Kconfig option and code Paul Gortmaker
2015-01-20  3:18 ` [PATCH 3/3] x86: drop support for 1995 era EISA based platforms Paul Gortmaker
2015-01-20  4:05   ` Maciej W. Rozycki [this message]
2015-01-20  6:16     ` Linus Torvalds
2015-01-20 19:50       ` Maciej W. Rozycki
2015-01-21 16:42 tedheadster

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 3/3] x86: drop support for 1995 era EISA based platforms' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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