qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cutting a new QEMU release
Date: Thu, 12 Feb 2009 23:44:48 +0900	[thread overview]
Message-ID: <499435E0.7010100@juno.dti.ne.jp> (raw)
In-Reply-To: <200902111549.18621.rob@landley.net>

Rob Landley wrote:
> On Saturday 07 February 2009 09:29:42 Shin-ichiro KAWASAKI wrote:
>> Anthony Liguori wrote:
>>> What do people think?  TCG seems to be in a good place.  We've got
>>> virtio, KVM, live migration, tons of new devices, bsd-user, etc.
>> The development of sh4 is rather slow, you know. Then there is no need to
>> think about it to decide when to cut the next version.
>>
>> From the point of view from sh4 system emulation, that's a good news.
>> It is a good way to provide current features for sh4 developers.
>> But before release, I hope these two points would handled by anyone.
>>
>> [1] USB support
>>
>> Current sh4 system emulation (r2d board) does not support USB host.
>> Without it, the graphic console does not receive any key input
>> via USB keyboard emulation.  Then, graphics console is not available
>> now.  I guess sh4 developers would feel it strange.
>>
>> Following patch adds usb host.
>>
>>     http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg01620.html
>>
>> It does not apply to current svn head, because of line mismatch.
>> I'm willing to post new version, if the patch is OK.
>> Could anyone review it?
>>
>>
>> [2] sh4 kernel & disk image on QEMU's download page
>>
>> It's a bothering work to make kernel & disk image for sh4.  Not to obstruct
>> sh4 developers with it, I provide a small (4MB) set at following URL.
>>
>> http://www.assembla.com/spaces/qemu-sh4/documents/b18oeq850r3AhNab7jnrAJ/do
>> wnload?filename=sh-test-0.1.tar.bz2
> 
> I downloaded this and tried it out with an svn snapshot from today (svn 6613), 
> built on Ubuntu 8.10 with default "./configure; make; sudo make install".

Thank you Rob for trying, and sorry for my mistakes in the package.
I thought again about the contents again, and have uploaded it on the same
URL as before.


> Your README has a typo, it says "-kernel r2d_zImage" but the one you've 
> packaged is just "zImage".  Once that's worked around, it pops up a qemu 
> window within which it boots to a login prompt, but I can't type anything.  
> This is the USB issue you mentioned, confirmed by the stdout from qemu:
> 
>   char device redirected to /dev/pts/14
>   Warning: could not add USB device keyboard
>   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
> 
> I thought I'd work around that with a serial console (which is what I actually 
> use for in my FWL project anyway), but I can't get that to work either.  Your 
> command line -appends "console=ttySC0,115200" and "early_printk=serial" but 
> ctrl-alt-2 shows nothing, and booting with
> -nographic gives no output.
> 
> Also, going back to ctrl-alt-1 doesn't redraw the vga screen.  (The screen 
> will partially redraw itself if it's still producing output, but it never 
> redraws the penguin logo at the top of the frame buffer, and if the console 
> has finished producing output it just stays black from then on.)

Sorry to say, I completely missed to add '-serial null -serial stdio' in the
command line example.  Could you try following line again?

  % ./qemu-system-sh4 -M r2d -kernel zImage -hda sh-linux-mini.img -serial null -serial stdio -nographic

I hope you'll see the shell prompt.


> This is more functionality than I've ever gotten out of sh4, and I really look 
> forward to adding sh4 support to http://impactlinux.com/fwl .  If I can get a 
> serial console working I'm probably good to go, but right now it's not quite 
> working for me yet...
> 
> Your README says that you can extract the config.gz from the kernel with 
> linux/scripts/extract-ikconfig, but when I tried it it said:
> 
>   ERROR: Unable to extract kernel configuration information.
>          This kernel image may not have the config info.
> 
> Obviously, I can't get it by logging in and catting /proc/config.gz without a 
> working keyboard or serial console...

On my Ubuntu 8.04 env, I can't get config with scripts/extract-ikconfig.
On the other hand, with Ubuntu 8.10 env, I can.  I'm not sure about the reason.
Anyway, I removed the explanation about the way to get config before booting.

Additionally, I modified the default kernel boot options slightly,
and ran fsck.ext2 on the disk image before packing.
I hope the package is appropriate for qemu-sh users, now.

I'm looking forward the fwl system image.  I've been struggling
to get stable userland on which gcc is available.


Regards,
Shin-ichiro KAWASAKI

  reply	other threads:[~2009-02-12 14:45 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 20:48 [Qemu-devel] Cutting a new QEMU release Anthony Liguori
2009-02-03 20:58 ` Glauber Costa
2009-02-03 21:35   ` Laurent Desnogues
2009-02-03 21:50     ` Anthony Liguori
2009-02-03 22:05       ` Laurent Desnogues
2009-02-03 22:47         ` Anthony Liguori
2009-02-03 23:48           ` Glauber Costa
2009-02-04 13:09       ` Ulrich Hecht
2009-02-04  0:31     ` David Turner
     [not found]     ` <74222928-D24B-4780-BDB0-D537A83C4F68@hotmail.com>
2009-02-04  5:08       ` C.W. Betts
2009-02-03 21:48 ` Rick Vernam
2009-02-03 22:07 ` Daniel P. Berrange
2009-02-04 14:50 ` Aurelien Jarno
2009-02-04 15:23   ` Tristan Gingold
2009-02-04 15:43     ` Lennart Sorensen
2009-02-04 16:01       ` Tristan Gingold
2009-02-04 18:17         ` [Qemu-devel] " Consul
2009-02-04 17:39   ` [Qemu-devel] " Blue Swirl
2009-02-04 17:50     ` Jonathan Kalbfeld
2009-02-04 20:07   ` Blue Swirl
2009-02-07 14:15   ` Stuart Brady
2009-02-04 15:58 ` Glauber Costa
2009-02-07 15:29 ` Shin-ichiro KAWASAKI
2009-02-11 21:49   ` Rob Landley
2009-02-12 14:44     ` Shin-ichiro KAWASAKI [this message]
2009-02-12 21:08       ` Rob Landley
2009-02-12 21:44       ` Rob Landley
2009-02-09 12:43 ` Mark McLoughlin
2009-02-09 21:36   ` Anthony Liguori
2009-02-10  0:47   ` Rob Landley
2009-02-10  7:22     ` M. Warner Losh
2009-02-13  8:40 ` Riku Voipio
2009-02-13  9:59   ` Stefano Stabellini
2009-02-13 16:30   ` Jamie Lokier
2009-02-13 17:00     ` Anthony Liguori
2009-02-13 19:04       ` [Qemu-devel] [PATCH] Revert block-qcow2.c to kvm-72 version due to corruption reports Jamie Lokier
2009-02-14 22:23         ` Dor Laor
2009-02-15  2:20           ` Jamie Lokier
2009-02-14 23:13         ` Anthony Liguori
2009-02-15  2:01           ` Jamie Lokier
2009-02-15  4:09             ` Anthony Liguori
2009-02-15 15:42               ` Jamie Lokier
2009-02-15 18:19                 ` Anthony Liguori
2009-02-15 18:34                   ` Johannes Schindelin
2009-02-16  1:01                     ` Anthony Liguori
2009-02-17  0:52                       ` Jamie Lokier
2009-02-17  2:55                         ` Anthony Liguori
2009-02-16  1:19                     ` Anthony Liguori
2009-02-17  1:01                   ` 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=499435E0.7010100@juno.dti.ne.jp \
    --to=kawasaki@juno.dti.ne.jp \
    --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 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).