qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Natalia Portillo <iosglpgc@teleline.es>
To: "J. Mayer" <l_indien@magic.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Open Hack'Ware 0.4 release candidate
Date: Tue, 22 Mar 2005 23:27:37 +0000	[thread overview]
Message-ID: <5bf6f0b0ace55dd7680555502f76c7d3@teleline.es> (raw)
In-Reply-To: <1111493483.31144.21.camel@rapid>

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.
Ok but surely they are x86 only

> 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.
Uh, as far as I know the BeFS filesystem for Linux is in the kernel ^o)
You can download a fully explanation of the BeFS from Dominic 
Giampaolo's webpage (the designer of BeFS).
Also the OpenBeOS project has a working filesystem driver (at least 
readonly)

Without that in OHW or a BeOS/PPC compatible machine I'm not able to 
extract the kernel (the drivers I said are for little endian BeFS and 
not for big endian one)

>> 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...
Say me

>> 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.
The qemu prep emulation currently emulates the serial controller?
Remember that we debugged the mos kernel and find that it was trying to 
access a non implemented command in the rs232 controller

  reply	other threads:[~2005-03-23  3:53 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
2005-03-22 23:27         ` Natalia Portillo [this message]
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=5bf6f0b0ace55dd7680555502f76c7d3@teleline.es \
    --to=iosglpgc@teleline.es \
    --cc=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 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).