From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <andreas.faerber@web.de>,
"François Revol" <revol@free.fr>
Subject: Re: [Qemu-devel] atapi on ppc issue (was Re: qemu-system-ppc broken ?)
Date: Sun, 16 Nov 2008 21:32:35 +0200 [thread overview]
Message-ID: <f43fc5580811161132y77ade0b6h488c5786d120354e@mail.gmail.com> (raw)
In-Reply-To: <1226433268.3978.7.camel@frecb07144>
On 11/11/08, Laurent Vivier <Laurent.Vivier@bull.net> wrote:
> Le lundi 10 novembre 2008 à 21:01 +0100, Andreas Färber a écrit :
>
> > Am 09.11.2008 um 23:07 schrieb François Revol:
> >
> > >>>> Though I still can't seem to get OpenHackware to read the CD:
> > >>>> ERROR: ATAPI TEST_UNIT_READY : status 50 != 0x40
> > >>>
> > >>> I suppose OpenHackware only compares instead of checking the ready
> > >>> bit...
> > >>
> > >
> > > The attached patch makes OpenHackware happy again.
> > > At least qemu-system-ppc can now start debian iso, and mine as well
> > [...]
> > > OpenHackware should be fixed instead, but it seems the binary in svn
> > > has been updated after the last sources I found
> > [...]
> > > Seems the last update was already about ATAPI...
> > > Anyone has the latest source used ?
> > > I could at least fix it to check for bits on errors...
> >
> > Rene Rebe recently posted some diff against qemu's OHW diff, but it
> > appeared to be whitespace-damaged.
> >
> > > Of course it'd be much better to switch to a real OF instead...
> > > but I don't have the time for that, couldn't find usable OpenBIOS
> > > images,
> >
> > I once tried to get OpenBIOS working but failed, Laurent appeared to
> > get some further - any update on that?
>
>
> No, I stopped working on this because I had no time.
>
> In fact, if I remember correctly, OpenHW initializes PCI devices whereas
> OpenBIOS doesn't, I've started working on this but it is too much work
> form me. I had a working OpenBIOS, able to start a kernel (at some
> time), but stopping during boot.
>
> If someone is interested (perhaps) I can find my patches and send them
> (privately).
I would be interested. I finally created a PowerPC cross compiler and
I'd like to test OpenBIOS for PPC.
next prev parent reply other threads:[~2008-11-16 19:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 3:16 [Qemu-devel] qemu-system-ppc broken ? François Revol
2008-11-07 7:08 ` Aurelien Jarno
2008-11-07 7:53 ` François Revol
2008-11-07 8:19 ` [Qemu-devel] atapi on ppc issue (was Re: qemu-system-ppc broken ?) François Revol
2008-11-07 8:28 ` François Revol
2008-11-09 22:07 ` François Revol
2008-11-09 22:11 ` François Revol
2008-11-10 20:01 ` Andreas Färber
2008-11-10 20:27 ` François Revol
2008-11-10 20:56 ` Andreas Färber
2008-11-10 21:16 ` François Revol
2008-11-11 17:31 ` Blue Swirl
2008-11-11 17:58 ` Andreas Färber
2008-11-11 17:28 ` Blue Swirl
2008-11-11 19:54 ` Laurent Vivier
2008-11-16 19:32 ` Blue Swirl [this message]
2008-11-16 19:40 ` Laurent Vivier
2008-11-23 18:55 ` Blue Swirl
2008-11-24 8:34 ` René Rebe
2008-11-24 16:32 ` Andreas Färber
2008-11-27 15:13 ` Shin-ichiro KAWASAKI
2008-11-07 16:38 ` [Qemu-devel] qemu-system-ppc broken ? Laurent Desnogues
2008-11-08 8:57 ` 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=f43fc5580811161132y77ade0b6h488c5786d120354e@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=andreas.faerber@web.de \
--cc=qemu-devel@nongnu.org \
--cc=revol@free.fr \
/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).