From: "François Revol" <revol@free.fr>
To: Eagle <eagle@linuxcrypt.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] A dream of mine: the ability to run m68k NeXT applications
Date: Tue, 19 May 2009 22:10:02 +0200 CEST [thread overview]
Message-ID: <11711693974-BeMail@laptop> (raw)
In-Reply-To: <C0C4391A-BFD1-4091-ABF8-1F0EF06C3303@linuxcrypt.com>
> Greetings, all.
>
> I have a dream. Well, several actually, but two that are applicable
> here.
>
> The first is: I am interested in having the ability to run m68k NeXT
> applications. There are potentially several ways to do this, but two
> come to mind:
> 1- a CPU-only emulator that runs on i386 NeXTSTEP/OPENSTEP, similar
> to
> what Apple used during the transition from m68k to PPC.
It should be possible to port qemu to *STEP and add the needed syscall
translations, I suppose.
> 2- a full-blown NeXT hardware emulator.
This would help porting other OSes too...
I'd really like to add NeXT to the possible targets of my m68k Haiku
port...
Though I admit it's only just for fun :)
AFAIK the m68k support in QEMU is not finished, and is mostly coldfire
only.
Another option is to start from an existing 68k emulator.
There is UAE, ARAnyM...
ARAnyM is based on UAE cpu code, but has 040 mmu support (it has now
been backported to UAE as a patch).
> The second dream that I have is: I am interested in a PPC Mac
> emulator
> that is capable of running OS X Server v1.2 (AKA Rhapsody). I am
> interested in this because I no longer have a PPC Mac that is capable
> of running OS X Server.
Tried PearPC ?
François.
next prev parent reply other threads:[~2009-05-19 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 19:40 [Qemu-devel] A dream of mine: the ability to run m68k NeXT applications Eagle
2009-05-19 20:10 ` François Revol [this message]
2009-05-19 21:39 ` Laurent Vivier
2009-05-21 15:53 ` Eagle
2009-05-19 20:18 ` Jamie Lokier
2009-05-19 20:26 ` Eagle
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=11711693974-BeMail@laptop \
--to=revol@free.fr \
--cc=eagle@linuxcrypt.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.