LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 3/3] x86: drop support for 1995 era EISA based platforms
Date: Tue, 20 Jan 2015 19:50:45 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1501201922110.28301@eddie.linux-mips.org> (raw)
In-Reply-To: <CA+55aFzN2PvWJ6g1Vbe-_oODyX7EiSeDhw5SD=wJeyENnHX41A@mail.gmail.com>

On Tue, 20 Jan 2015, Linus Torvalds wrote:

> >  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.
> 
> So if we actually have a user, and it works, then no, we're not
> removing EISA support. It's not like it hurts us or is in some way
> fundamentally broken, like the old i386 code was (i386 kernel page
> fault semantics really were broken, and the lack of some instructions
> made it more painful to maintain than needed - not like EISA at all,
> which is just a pure add-on on the side).

 Thanks.  Last version I tried was 3.18.0-rc1-next-20141023 sometime last 
November.  It worked just fine, booted to the multiuser mode with no 
issue.  I'll have to refresh the build sometime.

 It's a plain EISA box, no PCI.  The EISA FDDI board referred works fine 
(it uses our DMA API for bus mastering) as does an ISA 3c509B Ethernet 
adapter configured for the EISA mode.  The card supports it -- it looks 
like a true EISA board to software then, there's no need to poke at random 
port I/O locations anymore to detect it -- as does our driver.

 I have a small patch outstanding to reserve the BIOS area at 0xffff0000 
(used at reset as per the x86 architecture definition) so that systems 
that do not support the 0xe820 call do not attempt to allocate MMIO in 
that range.  It may matter for some old PCI systems as well, I suppose.  
I just need to verify it does not cause a conflict with systems that do 
support that call.

 Other than that it seems maintenance-free to me.

  Maciej

  reply	other threads:[~2015-01-20 19:50 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
2015-01-20  6:16     ` Linus Torvalds
2015-01-20 19:50       ` Maciej W. Rozycki [this message]
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:
  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=alpine.LFD.2.11.1501201922110.28301@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --subject='Re: [PATCH 3/3] x86: drop support for 1995 era EISA based platforms' \
    /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

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