All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 14 Mar 2010 18:08:40 -0600	[thread overview]
Message-ID: <201003141908.41360.rob@landley.net> (raw)
In-Reply-To: <20100314212832.GE2381@hall.aurel32.net>

On Sunday 14 March 2010 16:28:32 Aurelien Jarno wrote:
> On Sat, Mar 13, 2010 at 05:11:43PM -0600, Rob Landley wrote:
> > I found out that "-serial stdio" is apparently trying to open /dev/stdio,
> > which Ubuntu 9.04 hasn't got.  If I say -serial /dev/tty it works from
> > the command line (but not in scripts).
>
> This is actually not specific at all to sh4. See this thread:
> http://www.mail-archive.com/qemu-devel@nongnu.org/msg20920.html

http://www.mail-archive.com/qemu-devel@nongnu.org/msg22763.html

> This is redundant.  -nographic implies -serial stdio.

Trying with just -nographic and no -serial lines, I get:

$ qemu-system-sh4 -M r2d -nographic -no-reboot -kernel zImage-sh4 -hda image-
sh4.sqf -append "root=/dev/sda rw init=/usr/sbin/init.sh panic=1 PATH=/usr/bin 
console=ttySC0 noiotrap HOST=sh4"
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

And it hangs.  No output from any of the kernel serial writes.

http://www.mail-archive.com/qemu-devel@nongnu.org/msg22775.html

> >    eg this should work as you'd expect it
> >
> >      qemu -nodefaults -nographic -serial stdio
>
> -nographic is basically equivalent to -serial mon:stdio,signal=on -vga none
> except it operates on defaults. Your invocation actually ends up being very
> different as it doesn't multiplex the monitor and it doesn't disable ctrl-c.
> Basically, your invocation is equivalent to qemu -vga none -serial stdio

http://www.mail-archive.com/qemu-devel@nongnu.org/msg22775.html

$ qemu-system-sh4 -M r2d -nographic -no-reboot -kernel zImage-sh4 -hda image-
sh4.sqf -append "root=/dev/sda rw init=/usr/sbin/init.sh panic=1 PATH=/usr/bin 
console=ttySC0 noiotrap HOST=sh4"  -vga none -serial stdio
chardev: opening backend "stdio" failed
qemu: could not open serial device 'stdio': Inappropriate ioctl for device

http://www.mail-archive.com/qemu-devel@nongnu.org/msg22777.html

$ qemu-system-sh4 -M r2d -nodefaults -nographic -serial stdio -no-reboot -
kernel zImage-sh4 -hda image-sh4.sqf -append "root=/dev/sda rw 
init=/usr/sbin/init.sh panic=1 PATH=/usr/bin console=ttySC0 noiotrap HOST=sh4"
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

And the hang's back, no output...

Ok, this seems to work:

qemu-system-sh4 -M r2d -nodefaults -nographic -serial null -serial stdio -no-
reboot -kernel zImage-sh4 -hda image-sh4.sqf -append "root=/dev/sda rw 
init=/usr/sbin/init.sh panic=1 PATH=/usr/bin console=ttySC0 noiotrap HOST=sh4"

I no longer even pretend to know why...

Do I have to say "-nodefaults" on every other target as well to disable the 
unwanted monitor I never knew was there?

Rob
-- 
Latency is more important than throughput. It's that simple. - Linus Torvalds

  reply	other threads:[~2010-03-15  0:10 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
2010-03-13 23:11     ` Rob Landley
2010-03-14 21:28       ` Aurelien Jarno
2010-03-15  0:08         ` Rob Landley [this message]
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=201003141908.41360.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 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.