From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NqxtL-00084I-CA for qemu-devel@nongnu.org; Sun, 14 Mar 2010 20:10:43 -0400 Received: from [199.232.76.173] (port=42547 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NqxtK-000843-Tm for qemu-devel@nongnu.org; Sun, 14 Mar 2010 20:10:42 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NqxtF-0003On-QY for qemu-devel@nongnu.org; Sun, 14 Mar 2010 20:10:42 -0400 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5]:37784 helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NqxtE-0003LT-AC for qemu-devel@nongnu.org; Sun, 14 Mar 2010 20:10:37 -0400 From: Rob Landley Subject: Re: [Qemu-devel] qemu-system-sh4 broken again. Date: Sun, 14 Mar 2010 18:08:40 -0600 References: <201003130151.36065.rob@landley.net> <201003131711.44849.rob@landley.net> <20100314212832.GE2381@hall.aurel32.net> In-Reply-To: <20100314212832.GE2381@hall.aurel32.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201003141908.41360.rob@landley.net> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aurelien Jarno Cc: Shin-ichiro KAWASAKI , qemu-devel@nongnu.org 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