From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Kosina <jkosina@suse.cz>, Adam Osuchowski <adwol@zonk.pl>,
linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Is 386 processor still supported?
Date: Tue, 13 Jan 2009 01:06:55 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0901130047160.10547@ftp.linux-mips.org> (raw)
In-Reply-To: <20090108151046.GK18120@elte.hu>
On Thu, 8 Jan 2009, Ingo Molnar wrote:
> > So our minimal spec for SMP is probably 486DX + external Intel APIC.
> >
> > In practice I doubt there is a single Intel APIC type 486 SMP box on the
> > planet running Linux (or quite possibly running at all)
>
> yeah, that's very likely true. I think we could eliminate some of the SMP
> complications by requiring cmpxchg presence for CONFIG_SMP, agreed?
I failed to track down a single 486 SMP system that would adhere to the
MP spec. There were and possibly still are APIC-based 486 SMP systems out
there, but most likely they are not Intel MPS-compliant, by not providing
the MP header at the very least. Thus Linux would have to be ported and I
gather the interest in doing so is epsilon.
Myself, I could not resist trying an APIC-based 486 SMP box and possibly
fixing issues if I found one and it was MPS-compliant, but nothing beyond
that I would say. Life's too short.
Maciej
next prev parent reply other threads:[~2009-01-13 1:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 12:03 Adam Osuchowski
2009-01-08 13:05 ` Jiri Kosina
2009-01-08 13:24 ` Cyrill Gorcunov
2009-01-08 13:48 ` Jiri Kosina
2009-01-08 14:13 ` Peter Zijlstra
2009-01-08 14:21 ` Jiri Kosina
2009-01-08 14:27 ` Peter Zijlstra
2009-01-08 15:04 ` Alan Cox
2009-01-08 15:10 ` Ingo Molnar
2009-01-13 1:06 ` Maciej W. Rozycki [this message]
2009-01-15 12:36 ` Jan-Benedict Glaw
2009-01-15 13:22 ` Maciej W. Rozycki
2009-01-15 13:32 ` Alan Cox
2009-01-15 14:15 ` Maciej W. Rozycki
2009-01-15 14:17 ` Ingo Molnar
2009-01-16 9:00 ` Pavel Machek
2009-01-16 10:13 ` Jan-Benedict Glaw
2009-01-16 11:18 ` Andrey Panin
2009-01-16 13:46 ` Ingo Molnar
2009-01-16 18:17 ` H. Peter Anvin
2009-01-15 14:20 ` Jan-Benedict Glaw
2009-01-15 14:37 ` Bastien ROUCARIES
2009-01-15 14:25 ` Alan Cox
2009-01-15 14:44 ` Maciej W. Rozycki
2009-01-15 20:11 ` H. Peter Anvin
2009-01-15 14:46 ` Jan-Benedict Glaw
2009-01-08 16:45 ` Sam Ravnborg
2009-01-08 16:27 ` Andi Kleen
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.1.10.0901130047160.10547@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=adwol@zonk.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome