From: Peter Zijlstra <peterz@infradead.org>
To: "Luís Mendes" <luis.p.mendes@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Thomas Gleixner <tglx@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun@kernel.org>, Gary Guo <gary@garyguo.net>,
Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-um@lists.infradead.org
Subject: Re: Some observations regarding the ongoing x86-32 CPU configuration cleanups
Date: Mon, 9 Nov 2026 13:29:08 +0100 [thread overview]
Message-ID: <20261109122908.GU2668804@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAEzXK1pdhEyOgQ4owkeRmyEP6Pyfhk=OsMHdzU4xwNMCmCsd6g@mail.gmail.com>
On Mon, Nov 09, 2026 at 10:34:54AM +0000, Luís Mendes wrote:
> Hi everyone,
>
> First of all i would like to say that i both admire and appreciate all
> your hard work with this lovely OS. I do understand that maintaining
> some systems can cause additional burden on maintenance, but there are
> some aspects that i would like you to reconsider.
>
> I am writing because I believe that some aspects have not been taking
> into consideration regarding the removal of the 80486 32-bit support
> from the kernel, namely:
> - There is this active Linux distribution:https://tinycorelinnux.net/
> and the Damn Smal Linux DSL (https://damnsmalllinux.org).
> - There are also these CPUs: https://www.vortex86.com/products/Vortex86EX
> - There may be only a few vintage 486 systems still working, but there
> are also other new x86 CPUs systems, especially in FPGAs like the
> https://github.com/MiSTer-devel/ao486_MiSTer which is a 486SX core
> that operates at 90MHz and can use up to 256MB RAM memory. There are
> plans to update this CPU IP core to become a full 486DX core, by
> adding a FPU unit to it and would turn this into a usable Desktop
> system with tineycorelinux. There is a considerable retro-computing
> community that utilizes the AO486 core on the MiSTer FPGA platform.
> There is even a Voodoo 3dfx accelerator card:
> https://github.com/victor-fisyuk/voodoo-fpga-public.
>
> Overall i just want to inform you that some new x86 32-bit systems are
> still being sold brand new and can be utilized with Linux. I would
> like that you consider this with regard to how much 80486 support
> should be removed from Linux.
>
> Personally i do have plans to extend the AO486 core to have the FPU
> and would like to be able to run a modern Linux on it. It would have
> entertainment and educational applications. With tinycoreinux it can
> have a usable desktop.
I don't realistically see 486 support coming back -- the thing doesn't
even have TSC. Getting rid of all the horrible (and completely untested)
code for no-tsc alone was worth deleting 486 support for.
The other option is you actually implementing RDTSC, CPUID (and possibly
CMPXCHG8B) on your FPGA. I'm sure that's actually a *LOT* simpler than
doing i487 support.
Just add whatever instructions are required to get the bare minimal
32bit build working.
prev parent reply other threads:[~2026-11-09 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 10:34 Luís Mendes
2026-11-09 12:29 ` Peter Zijlstra [this message]
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=20261109122908.GU2668804@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexander.usyskin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=arnd@arndb.de \
--cc=boqun@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gary@garyguo.net \
--cc=hpa@zytor.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@rasmusvillemoes.dk \
--cc=luis.p.mendes@gmail.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richard@nod.at \
--cc=tglx@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®