From: "François Revol" <revol@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] atapi on ppc issue (was Re: qemu-system-ppc broken ?)
Date: Fri, 07 Nov 2008 09:28:52 +0100 CET [thread overview]
Message-ID: <3916532044-BeMail@laptop> (raw)
In-Reply-To: <3383842040-BeMail@laptop>
> > Though I still can't seem to get OpenHackware to read the CD:
> > ERROR: ATAPI TEST_UNIT_READY : status 50 != 0x40
>
> Replying to myself, it seems this works around the issue, at least it
> goes further.
> I suppose OpenHackware only compares instead of checking the ready
> bit...
It seems I'm not the only one:
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/6937d731e3d4d4a8
I could try to fix the code in OH but I likely don't have the toolchain
required to rebuild it.
François.
next prev parent reply other threads:[~2008-11-07 8:24 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 [this message]
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
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=3916532044-BeMail@laptop \
--to=revol@free.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.