From: Finn Thain <fthain@linux-m68k.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Josh Juran <jjuran@gmail.com>,
geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: Bootloaders, was Re: [RFC PATCH 0/3] m68k goes DT
Date: Wed, 5 Mar 2025 14:42:02 +1100 (AEDT) [thread overview]
Message-ID: <3893637a-0a03-5782-a61d-18fbaf9938d3@linux-m68k.org> (raw)
In-Reply-To: <CAFr9PXmXsW=RqJsWPCUDvQO+vst-wSj__Fi3nuxCo7ZRAi0wOA@mail.gmail.com>
On Tue, 4 Mar 2025, Daniel Palmer wrote:
> FWIW I have started to move EMILE over to using meson to build (so
> it's easier to build on modern systems) and fixing up some of the
> issues it has with building with recent GCC.
Thanks for doing that.
> I have it working enough to boot HEAD on a LC475 and on QEMUs Q800
> machine. While the penguin ui is nice EMILE seems to work well enough
> and it can be used to generate bootable CDs.
That's good news -- I've long wondered whether QEMU's emulated q800 had
reached a point where it could run EMILE. That will make development
easier.
> I have a setup now that can generate a bootable CD with the kernel and a
> buildroot based userland that I can drop on the SD card for my bluescsi
> and boot into Linux without any macos intervention.
>
I guess it's only a matter of time before someone puts EMILE into EEPROM.
(Many of these systems have a ROM SIMM slot.)
> So basically, for 68k mac I think EMILE is the way to go.
>
And there is a way to go...
Penguin 19 works on every 68k Mac model. That's hard to achieve and
running under MacOS helps a lot. EMILE doesn't have that advantage so it
isn't expected to enjoy the same level of hardware compatibility without
further work.
For systems that have the standard ROM, booting MacOS is an easy first
step for system recovery purposes or just experimentation. So I think
EMILE needs a MacOS UI which, though it might not boot Linux, could do the
bootloader installation and config (a bit like what XPostFacto did for Mac
OS X) so the ROM could then boot into EMILE (and Linux).
next prev parent reply other threads:[~2025-03-05 3:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 7:14 Daniel Palmer
2025-01-05 7:14 ` [RFC PATCH 1/3] m68k: bootinfo: Add tag for FDT address Daniel Palmer
2025-01-05 7:14 ` [RFC PATCH 2/3] m68k: bootinfo: Add generic machine type Daniel Palmer
2025-01-05 7:14 ` [RFC PATCH 3/3] m68k: Add dt support (proof of concept) Daniel Palmer
2025-01-05 9:40 ` [RFC PATCH 0/3] m68k goes DT Finn Thain
2025-01-05 11:00 ` Daniel Palmer
2025-01-06 3:28 ` Finn Thain
2025-01-06 15:51 ` Josh Juran
2025-01-07 0:57 ` Bootloaders, was " Finn Thain
2025-03-04 10:43 ` Daniel Palmer
2025-03-05 3:42 ` Finn Thain [this message]
2025-01-09 10:06 ` Geert Uytterhoeven
2025-01-05 14:59 ` Greg Ungerer
2025-01-06 2:10 ` Daniel Palmer
2025-01-06 11:37 ` Brad Boyer
2025-01-06 22:14 ` Finn Thain
2025-01-09 10:29 ` Geert Uytterhoeven
2025-01-14 0:42 ` Finn Thain
2025-01-09 10:31 ` Geert Uytterhoeven
2025-01-09 14:08 ` Daniel Palmer
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=3893637a-0a03-5782-a61d-18fbaf9938d3@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--cc=jjuran@gmail.com \
--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
all inboxes | Powered by JetHome®