All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Open Hack'Ware 0.4 release candidate
Date: Tue, 22 Mar 2005 13:11:23 +0100	[thread overview]
Message-ID: <1111493483.31144.21.camel@rapid> (raw)
In-Reply-To: <1386bfaa70cddb03aa9ce283d55e5c12@teleline.es>

On Mon, 2005-03-21 at 23:43 +0000, Natalia Portillo wrote:
> Hi!

Hi,

> >> What you say about the BeOS:
> >>
> >> The BeOS kernel isn't in the ISO part of the CD-ROM, but in the Big
> >> Endian BeFS part of it.
> >
> > I did not say the kernel was in the El-Torito image.
> > I just said the CDROMs I got contain ISO filesystems.
> It should have three tracks, one in HFS/ISO with El-Torito, one in 
> little endian BeFS (BeOS/x86) and one in big endian BeFS (BeOS/PPC),
> if not, the CD is incorrect.

Seems that it depends on which CDROMs. I have some BeOS ones that really
don't look this way.

> >> The BeBox firmware understand this system and loads the PEFF kernel as
> >> I commented you a time ago.
> >> The BeOS Loader for MacOS seems to load the kernel from the BeFS also
> >> and then let control to it removing MacOS from memory.
> >
> > I though I remembered booting directly BeOS CDROM on a Mac, but I may 
> > be
> > wrong on this point...
> I don't think you got that, as the zbeos in the ISO/HFS partition seems 
> to be a x86 executable (I should see this in more detail), and OF 
> doesn't recognize BeFS.

Right. The El-torito image I checked is for x86.

> >> For getting BeOS compatibility there are two ways:
> >> First of all, emulate a BeBox. This shouldn't be a very hard way, as
> >> the BeBox is simply a PReP machine with a lot of chips (SCSI, UARTs,
> >> etc) and with an specific BIOS (I think, not similar to OpenFirmware 
> >> at
> >> any point).
> >> Second of all, see how the BeOS Loader loads the kernel in a MacOS. 
> >> The
> >> loader don't like at all the software ROM, and probably ignores 
> >> totally
> >> OpenFirmware and relies to ToolBox to get loaded and then do hardware
> >> probes (it does directly SCSI commands to load the system on a real
> >> Macintosh.)
> >
> > For now, I'm not in a hurry to see BeOS booting...
> > I just made a try and saw that it failed. Moreover, I think it would
> > only boot on OldWorld Macs, that are not supported in qemu.
> Yes, it will only boot on OldWorld, but also on BeBox (that are PReP 
> machines).
> There is one person interested on emulating a BeBox.
> Do you think will be easy to add BeFS support to OHW using OpenBeOS or 
> Linux's BeFS code?

It seems BeFS is not well documented. There was a BeFS project for Linux
but it seems that it has been stopped (no activity for a few years) and
was never integrated into standard kernels.
If BeBox is just a PREP machine, the first step to emulate it would be
to try to boot the BeOS kernel using Qemu PREP target with -kernel
argument.
Then, we may don't need any BeFS emulation to start it.

> >> About Windows NT did you get the kernel to load?
> >> I have also 3.5 and 3.51 so I can help you also in this.
> >>
> >> About Pegasos and MorphOS did you pass ago the UART check we had
> >> problems before?
[...]
> I think NT should boot with only the support for the executable format, 
> at least to a point that shows anything interesting on screen (surely a 
> big blue screen of death xD).

Well, I'd have to merge the code I got for NT XCOFF loading, then and
retry...

> MorphOS SHOULD work if we mix the qemu's PC emulation with OHW and 
> PowerPC cpu, as Pegasos is a standard PC motherboard with an OF clone 
> and a PowerPC G3/G4 chip.

Then, it's exactly what a PREP board is...
So, a few modifications from PREP target (mostly base addresses, I
guess) should be OK.

[...]

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2005-03-22 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 13:39 [Qemu-devel] Open Hack'Ware 0.4 release candidate J. Mayer
2005-03-21  2:56 ` Natalia Portillo
2005-03-21 22:59   ` J. Mayer
2005-03-21 23:43     ` Natalia Portillo
2005-03-22 12:11       ` J. Mayer [this message]
2005-03-22 23:27         ` Natalia Portillo
2005-03-23 14:30           ` J. Mayer

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=1111493483.31144.21.camel@rapid \
    --to=l_indien@magic.fr \
    --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.