[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b33b072e-f44a-9450-cbe9-52300ab971a3@linux-m68k.org>
Date: Tue, 7 Jan 2025 11:57:25 +1100 (AEDT)
From: Finn Thain <fthain@...ux-m68k.org>
To: Josh Juran <jjuran@...il.com>
cc: Daniel Palmer <daniel@...f.com>, geert@...ux-m68k.org,
linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Bootloaders, was Re: [RFC PATCH 0/3] m68k goes DT
On Mon, 6 Jan 2025, Josh Juran wrote:
>
> I'm not in a position to do testing on hardware or development relating
> to Linux bootup, but as before, I can maintain and build Mac OS
> programs.
>
I've entered the Penguin-19 bugs that I know of into the mac68k bug
tracker on sourceforge. I didn't add feature requests, like support for
the Mac LC II 12 MB RAM configuration, or support for zstd-format
compressed vmlinux. (Nevermind netbsd support, or device tree support...)
Some of those bugs and missing features apply to EMILE as well. IMHO, what
EMILE really needs is a MacOS GUI like Penguin. So my advice to
prospective mac bootloader developers is, add a GUI to EMILE rather than
try to maintain both packages.
That's easier said than done -- Penguin is a hard act to follow. But, in
theory, thanks to Retro68, it could be done without resorting to
proprietary tooling. Both the Linux executables and the MacOS application
could be built with a modern GCC.
Consider that, without a modern GCC, it will be difficult to re-use the
available code e.g. for kernel image decompression. Hence, it will be more
difficult to fix the long standing Penguin bug relating to gzip
decompression (which does not affect EMILE).
Powered by blists - more mailing lists