linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Josh Juran <jjuran@gmail.com>, linux-m68k@lists.linux-m68k.org
Subject: Re: penguin (was Re: Linux-mac68k project account maintenance)
Date: Thu, 18 Jun 2020 23:33:22 -0700	[thread overview]
Message-ID: <20200619063322.GA18201@allandria.com> (raw)
In-Reply-To: <alpine.LNX.2.22.394.2006190949530.11@nippy.intranet>

On Fri, Jun 19, 2020 at 11:39:49AM +1000, Finn Thain wrote:
> MAME/MESS can boot MacOS. There is work under way to boot MacOS in 
> qemu-system-m68k.
> 
> But outside of A/UX, I don't know of any way to get hardware assisted 
> virtualization for 68k MacOS applications.

It didn't work on Linux last I checked, but Basilisk II has support for
running directly on the CPU in NetBSD while only emulating the
supervisor instructions (it used a signal handler to detect and handle
anything that would cause an exception). I looked at the code, and it
appeared to be possible to do the same on Linux with some tweaks to
the signal handler (Linux passes the extra context differently).

However, Basilisk II can only boot MacOS because it doesn't actually
emulate all the hardware. In a few cases, it emulates synthetic
devices and inserts its own drivers with fake expansion ROMs. This
means you can't run Linux, NetBSD, or A/UX.

	Brad Boyer
	flar@allandria.com


      reply	other threads:[~2020-06-19  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LNX.2.22.394.2006151113030.17@nippy.intranet>
2020-06-15  3:29 ` Linux-mac68k project account maintenance (fwd) Josh Juran
2020-06-15  4:21   ` penguin (was Re: Linux-mac68k project account maintenance) Finn Thain
2020-06-18  7:11     ` Josh Juran
2020-06-19  1:39       ` Finn Thain
2020-06-19  6:33         ` Brad Boyer [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=20200619063322.GA18201@allandria.com \
    --to=flar@allandria.com \
    --cc=fthain@telegraphics.com.au \
    --cc=jjuran@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).