All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-sh4 broken again.
Date: Sat, 13 Mar 2010 11:26:47 +0100	[thread overview]
Message-ID: <20100313102647.GA26216@hall.aurel32.net> (raw)
In-Reply-To: <201003130151.36065.rob@landley.net>

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:

~/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


-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

  parent reply	other threads:[~2010-03-13 10:26 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 [this message]
2010-03-13 21:11   ` Rob Landley
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=20100313102647.GA26216@hall.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    /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.