From: Finn Thain <fthain@linux-m68k.org>
To: Daniel Palmer <daniel@thingy.jp>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: m68k: 68000 port for megadrive
Date: Sat, 27 Jun 2026 10:45:22 +1000 (AEST) [thread overview]
Message-ID: <8c8fc514-0a95-e25d-9af5-c9329134b11f@linux-m68k.org> (raw)
In-Reply-To: <CAFr9PXnh7cxzLYpkxXDx9UVrxZmywmbByU386XdijAtVKECzXg@mail.gmail.com>
On Fri, 26 Jun 2026, Daniel Palmer wrote:
> I'm not going to send patches* for this but I thought it'd at least be
> funny to someone.
Not funny to me. I think it's valuable work.
> I've used my DeviceTree enabled version of the 68000 code to do a
> quick port to the megadrive.
>
> https://github.com/LinuxMD/linuxmd (screenshot is near the end)
>
...
> Calibrating delay loop... 0.72 BogoMIPS (lpj=5984)
...
> Memory: 2532K/4096K available (1002K kernel code, 54K rwdata, 108K rodata,
> 72K init, 39K bss, 1368K reserved, 0K cma-reserved)
My old laptop has about 1000x the bogomips and 1000x the memory shown in
your console log. Your work shows me what 1000 virtual machines might look
like here.
Shrinking the operating system in that way (no block layer, no network
stack etc.) is important work and is a real step towards comfortably
hosting a million busy containers on a single system.
next prev parent reply other threads:[~2026-06-27 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 12:35 Daniel Palmer
2026-06-26 12:47 ` John Paul Adrian Glaubitz
2026-06-26 12:55 ` Daniel Palmer
2026-06-27 0:45 ` Finn Thain [this message]
2026-07-07 12:58 ` Atari Jaguar port - was: " John Paul Adrian Glaubitz
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=8c8fc514-0a95-e25d-9af5-c9329134b11f@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=daniel@thingy.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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