From: "Blue Swirl" <blauwirbel@gmail.com>
To: Laurent Vivier <laurent@lvivier.info>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: First OOPS
Date: Mon, 22 Dec 2008 18:23:25 +0200 [thread overview]
Message-ID: <f43fc5580812220823qd24a4a8l32b3ea7d919ab9c4@mail.gmail.com> (raw)
In-Reply-To: <1B2D7E4F-B258-4CDF-B1B0-ED53829284E5@lvivier.info>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On 12/22/08, Laurent Vivier <laurent@lvivier.info> wrote:
>
> Le 22 déc. 08 à 12:20, Blue Swirl a écrit :
>
>
>
> > On 12/22/08, Laurent Vivier <laurent@lvivier.info> wrote:
> >
> > > On an install CD there is a forth script which start yaboot with good
> > > parameters but currently OpenBIOS is not able to decode this script
> (inside
> > > XML tags).
> > >
> >
> > Did OHW ever handle this?
> >
>
> It does, but it is a hack: it computes the checksum of the script to
> identify it, and according the checksum the things to do are hardcoded into
> OHW.
>
> You have a big "switch()" and a "case" for each known script (for instance
> "debian etch install CD", "debian sarge install CD", etc).
Well, it wasn't that hard. The patch o_2_use_bootinfo.diff adds
parsing of CHRP file ppc\bootinfo.txt. Still, the loaded yaboot does
not work. Maybe a problem with ELF loader?
I've shuffled the patch series a bit, so here are all pending patches.
Would anyone mind if I applied them?
[-- Attachment #2: q_1_ppc_openbios.diff --]
[-- Type: plain/text, Size: 2924 bytes --]
[-- Attachment #3: q_2_ppc_use_prom_env.diff --]
[-- Type: plain/text, Size: 4414 bytes --]
[-- Attachment #4: q_3_ppc_use_fw_cfg.diff --]
[-- Type: plain/text, Size: 1222 bytes --]
[-- Attachment #5: o_1_ppc_add_boot.diff --]
[-- Type: plain/text, Size: 3628 bytes --]
[-- Attachment #6: o_2_use_bootinfo.diff --]
[-- Type: plain/text, Size: 3279 bytes --]
[-- Attachment #7: o_3_ppc_use_fw_cfg.diff --]
[-- Type: plain/text, Size: 5114 bytes --]
next prev parent reply other threads:[~2008-12-22 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 23:47 [Qemu-devel] First OOPS Laurent Vivier
2008-12-22 0:17 ` [Qemu-devel] First OOPS ARM User Mode Martin Mohring
2008-12-22 9:33 ` Laurent Desnogues
2008-12-22 18:15 ` Martin Mohring
2008-12-22 6:22 ` [Qemu-devel] Re: First OOPS Blue Swirl
2008-12-22 10:37 ` Laurent Vivier
2008-12-22 11:20 ` Blue Swirl
2008-12-22 12:34 ` Laurent Vivier
2008-12-22 16:23 ` Blue Swirl [this message]
2008-12-22 16:38 ` Laurent Vivier
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=f43fc5580812220823qd24a4a8l32b3ea7d919ab9c4@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aurelien@aurel32.net \
--cc=laurent@lvivier.info \
--cc=openbios@openbios.org \
--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).