From: Rob Landley <rob@landley.net>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-sh4 broken again.
Date: Sat, 13 Mar 2010 15:11:03 -0600 [thread overview]
Message-ID: <201003131511.03651.rob@landley.net> (raw)
In-Reply-To: <20100313102647.GA26216@hall.aurel32.net>
On Saturday 13 March 2010 04:26:47 Aurelien Jarno wrote:
> On Sat, Mar 13, 2010 at 01:51:35AM -0600, Rob Landley wrote:
> > Using qemu-system-sh4, this commit:
> >
> > e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
> > commit e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
> > Author: Gerd Hoffmann <kraxel@redhat.com>
> > Date: Tue Dec 8 13:11:44 2009 +0100
> >
> > zap serial_monitor_mux
> >
> > The logic in this code obviously predates the multiple monitor
> > capability of qemu and looks increasingly silly these days.
> >
> > I think the intention of this piece of code is to get a reasonable
> > default for the -nographic case: have monitor and serial line muxed
> > on stdio.
> >
> > With the new default_serial and default_monitor variables we have now
> > doing just that became much easier ;)
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> >
> > Made "-serial stdio" now do:
> >
> > chardev: opening backend "stdio" failed
> > qemu: could not open serial device 'stdio': Inappropriate ioctl for
> > device
> >
> > Am I using it wrong?
> >
> > If I don't override it, I instead get:
> >
> > long read to SH7750_WCR1_A7 (0x000000001f800008) ignored
> > long read to SH7750_WCR2_A7 (0x000000001f80000c) ignored
> > long read to SH7750_WCR3_A7 (0x000000001f800010) ignored
> > long read to SH7750_MCR_A7 (0x000000001f800014) ignored
> > long read to SH7750_MCR_A7 (0x000000001f800014) ignored
> > sh_serial: unsupported read from 0x10
> > qemu-system-sh4: /home/landley/qemu/git/hw/sh_serial.c:285:
> > sh_serial_ioport_read: Assertion `0' failed.
> >
> > Is anybody out there actually using the sh4 emulator? I've gotten it to
> > work several times before on various random git snapshots, but never in a
> > release version...
>
> Would be nice to give that you give the actual command line to try to
> use. I am using the stable-0.12 branch (plus some backporting patches
> for the MMU) to do development on sh4. HEAD still works correctly here.
> I am using the following command line:
Mine's:
And the kernel and root filesystem images to use with it are at:
http://impactlinux.com/fwl/downloads/binaries/system-image-sh4.tar.bz2
Note the binaries in that tarball used to work, they haven't been rebuilt
since the last time I had a qemu that could run them. The problem it was a
random -git snapshot (no release version has ever worked for me on sh4, that
I'm aware of) and I don't remember which version. However, my blog says that
on November 5, 2009 I had it working with unpatched git, so presumably I could
grab a qemu from there and bisect...
> ~/git/qemu/sh4-softmmu/qemu-system-sh4 -M r2d -kernel zImage -drive
> file=sh4.img -serial null -serial stdio -usb -append "root=/dev/sda1
> console=tty0 console=ttySC0,115200 noiotrap" -usbdevice keyboard -usbdevice
> mouse
I found my blog entries about getting sh4 to work back in February 2009:
http://landley.net/notes-2009.html#13-02-2009
Which told me when to look in the archives to find the threads where I learned
how to make it work in the first place. This one is where I got the -serial
null -serial stdio advice:
http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg00825.html
And here's where I got an actual command prompt:
http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg00961.html
Meaning I've figured out who I should have cc'd in the first place. :)
Rob
--
Latency is more important than throughput. It's that simple. - Linus Torvalds
next prev parent reply other threads:[~2010-03-13 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 7:51 [Qemu-devel] qemu-system-sh4 broken again Rob Landley
2010-03-13 8:54 ` Roy Tam
2010-03-13 10:26 ` Aurelien Jarno
2010-03-13 21:11 ` Rob Landley [this message]
2010-03-13 23:11 ` Rob Landley
2010-03-14 21:28 ` Aurelien Jarno
2010-03-15 0:08 ` Rob Landley
2010-05-10 14:42 ` Shin-ichiro KAWASAKI
2010-05-10 15:48 ` Aurelien Jarno
2010-05-11 14:08 ` Shin-ichiro KAWASAKI
2010-03-15 2:04 ` Jamie Lokier
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=201003131511.03651.rob@landley.net \
--to=rob@landley.net \
--cc=aurelien@aurel32.net \
--cc=kawasaki@juno.dti.ne.jp \
--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).