From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [Qemu-devel] Status of SH4 support in repository
Date: Fri, 13 Feb 2009 23:27:14 +0900 [thread overview]
Message-ID: <49958342.4080803@juno.dti.ne.jp> (raw)
In-Reply-To: <200902130245.53417.rob@landley.net>
Rob Landley wrote:
> On Wednesday 11 February 2009 06:28:05 Shin-ichiro KAWASAKI wrote:
>> Kristoffer Ericson wrote:
>>> On Wed, 11 Feb 2009 01:53:45 +0900
>>>
>>> Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp> wrote:
>>>> Hi, Kristoffer.
>>>>
>>>> Kristoffer Ericson wrote:
>>>>> Greetings,
>>>>>
>>>>> Just interested in an update of the current status. I built a fresh
>>>>> qemu from the repository today and Im currently I get no output.
>>>> I do not catch 'no output' mean. Could you explain it more?
>>>>
>>>> FYI, here's the log how I built qemu-sh at Feb. 6th.
>>>> http://www.assembla.com/wiki/show/qemu-sh4/BuildingEnvironment
>>> My mistake I did something wrong when I built it earlier, currently
>>> it works somewhat. What doesnt work is keyboard,mouse and booting
>>> from image file (seems like to bootstring isnt being aknowledged).
>> Current qemu sh4 system emulation does not support either usb host
>> or kernel boot command line. You still need to apply some patches
>> to use those features.
>>
>> Please check qemu-sh patch staging repository, which holds patches
>> for qemu-sh. README in it explains how to apply.
>> http://git.kernel.org/?p=virt/qemu/lethal/qemu-sh.git;a=summary
>
> My blocker is the lack of a working -append. You have a git tree for a
> collection of 5 patches, which then wants to invoke "quilt" to apply them.
> (Seems like overkill.)
>
> At a guess, this seems like the patch that implements it is
> staging/sh4-r2d-update-pci-usb-and-kernel-management.patch
>
>> To apply all them, you need to role back qemu to rev 6215, for now.
>
> No you don't, you just need a chainsaw and some duct tape...
>
>> The patch for usb host is already posted to qemu-ml. But I guess
>> patch for kernel boot command line for r2d is not yet posted.
>
> I adjusted the above patch to apply to current qemu svn, and attached the
> result, but it didn't make -append work. It's still using the hardwired one.
>
> Any suggestions? (Do I need to look at the other patches? This one looked
> like it was _trying_ to fix the problem...)
Yoshii-san already turned on the chainsaw the day before yeterday. :)
http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg00727.html
And I guess, -append option is valid only if the kernel zImage does
not contain built in kernel arguments : the kernel in sh-test-0.1.tar.bz2
contains it. Here's the one without arguments, I hope it helps.
http://www.assembla.com/spaces/qemu-sh4/documents/aVMOyC-DGr3y5PeJe5afGb/download?filename=r2d_nokernelarg_zImage
Regards,
Shin-ichiro KAWASAKI
next prev parent reply other threads:[~2009-02-13 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:23 [Qemu-devel] Status of SH4 support in repository Kristoffer Ericson
2009-02-10 16:53 ` Shin-ichiro KAWASAKI
2009-02-10 17:29 ` Kristoffer Ericson
2009-02-11 12:28 ` Shin-ichiro KAWASAKI
2009-02-13 8:45 ` Rob Landley
2009-02-13 14:27 ` Shin-ichiro KAWASAKI [this message]
2009-02-14 9:31 ` Rob Landley
2009-02-10 17:38 ` takasi-y
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=49958342.4080803@juno.dti.ne.jp \
--to=kawasaki@juno.dti.ne.jp \
--cc=linux-sh@vger.kernel.org \
--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).