From: Milton Miller <miltonm@bga.com>
To: l_indien@magic.fr
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] I got a kernel booted under qemu-system-ppc !
Date: Fri, 19 Oct 2007 13:10:27 -0500 [thread overview]
Message-ID: <d9b2d9cb68e61a779eca669f1a13af52@bga.com> (raw)
In-Reply-To: <1192815587.11576.32.camel@jma4.dev.netgem.com>
On Oct 19, 2007, at 12:39 PM, Jocelyn Mayer wrote:
> On Fri, 2007-10-19 at 17:19 +0200, Aurelien Jarno wrote:
>> The small patch below fixes the IDE problem, but not the NE2000 ISA
>> one.
>> Please apply.
>
> Interesting, thanks. I'll test this and apply or check for more fixes
> if
> needed... I'll also try to check what's happening with the NE2000.
> Could
> it be the ne2000_irq table in ppc_prep.c would not be correct ?
I started to look at ne2k also but don't remember the details.
Evenutally the driver shoudl learn the interrupt thorugh the
information in the device tree but I'm sure the isa driver does not
presently.
> It may
> also be usefull to be able to use PCI network devices, if the target
> runs properly, isn't it ?
It would mean the interrupt code could eb discovered easily, once we
get pci to fully work.
> If the proposed ROM image is best suitable to make PreP target run (and
> as I don't spend a lot of time hacking OHW those days), it may also be
> interesting to add a ppc_prep_rom.bin to the repository... In fact, it
> was maybe not a good idea to try to use the same BIOS image on all
> PowerPC targets...
The code has drawbacks, as I mentioned. Its very linux specific and
the only error it finds is no load segement in the presumed elf header.
It wouldn't be that hard to add some error checking and even print
error to the serial. The code itself is not platform specific but the
device tree attached to it is. As I said, we could link multiple
copies together (one for each platform) and search until we got the
right one; or just search trees based on the platform with the fixups
in code specific to that tree. In that regard, this would be an
option to use when using -kernel instead of being tied to the prep
platform.
next prev parent reply other threads:[~2007-10-19 18:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 0:12 [Qemu-devel] I got a kernel booted under qemu-system-ppc ! Rob Landley
2007-10-18 23:46 ` J. Mayer
2007-10-19 17:57 ` Milton Miller
2007-10-23 9:17 ` J. Mayer
2007-10-19 6:00 ` [Qemu-devel] " Milton Miller
2007-10-19 15:03 ` [Qemu-devel] " Aurelien Jarno
2007-10-19 15:19 ` Aurelien Jarno
2007-10-19 17:39 ` Jocelyn Mayer
2007-10-19 18:10 ` Milton Miller [this message]
2007-10-19 19:39 ` Aurelien Jarno
2007-10-19 20:33 ` Aurelien Jarno
2007-10-20 6:08 ` Rob Landley
2007-10-20 8:50 ` J. Mayer
2007-10-21 9:55 ` Rob Landley
2007-10-21 10:24 ` J. Mayer
2007-10-21 12:28 ` J. Mayer
2007-10-21 22:37 ` Rob Landley
2007-10-20 14:23 ` Aurelien Jarno
2007-10-20 14:49 ` Aurelien Jarno
2007-10-20 21:49 ` Aurelien Jarno
2007-10-21 9:01 ` J. Mayer
2007-10-20 7:52 ` Rob Landley
2007-10-20 9:03 ` J. Mayer
2007-10-20 9:42 ` Aurelien Jarno
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=d9b2d9cb68e61a779eca669f1a13af52@bga.com \
--to=miltonm@bga.com \
--cc=aurelien@aurel32.net \
--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).