From: Riku Voipio <riku.voipio@iki.fi>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: marcin.juszkiewicz@linaro.org, peter.maydell@linaro.org,
riku.voipio@iki.fi, Juha.Riihimaki@nokia.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] usb-musb: make qdev-aware
Date: Fri, 2 Sep 2011 11:00:39 +0300 [thread overview]
Message-ID: <20110902080039.GA6478@afflict.kos.to> (raw)
In-Reply-To: <4E608AD4.3010705@redhat.com>
On Fri, Sep 02, 2011 at 09:50:44AM +0200, Gerd Hoffmann wrote:
> On 09/02/11 09:03, Juha.Riihimaki@nokia.com wrote:
>>>> How to you test musb?
>>>
>>> Unfortunately I don't have any test cases which actively use the musb,
>>> so I settle for testing an n810 image (and a beagle image in my omap3
>>> tree) and confirming that the init part of things still works ok.
>>> (I'm not entirely happy with this but init is really all we're changing
>>> with these patches so we should be ok...)
>>>
>>> Riku/Juha -- do you have any musb test images/command lines?
>>
>> With an existing n810 image I guess you can test USB networking by adding
>> "-usb -net user,vlan=0 -net nic,model=usb,vlan=0 -usbdevice net -redir
>> tcp:2022::22" to qemu command line parameters. In the guest, launch X
>> terminal and command "sudo gainroot" followed by "udhcpc". You should now
>> be able to ssh to the guest from the host with "ssh -p 2022
>> root@localhost". Would this be sufficient for your needs?
> For starters just "qemu-system-arm -M n810" is better than nothing, this
> does at least make sure it doesn't blow up somewhere when creating the
> device tree.
> Booting an image and operating some usb device is even better. Are n810
> images are freely available for download somewhere? Failing that, is it
> possible to just install some linux distro (say debian) on the virtual
> n810 or another arm device which has a musb controller?
n800/n810 qemu images based on official are not redistributable, as
they carry propiertary software. Instructions howto convert a firmare
to qemu image exist, but to get your hands on a firmware you need to
know a n800/n810 serial number:
http://marcin.juszkiewicz.com.pl/2008/04/11/nokia-n800-emulation/
http://www.rkeene.org/projects/info/wiki/106
Marcin might have a poky image still somehere thou?
Riku
next prev parent reply other threads:[~2011-09-02 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 20:49 [Qemu-devel] [PATCH 0/3] usb-musb: make qdev-aware Peter Maydell
2011-08-31 20:49 ` [Qemu-devel] [PATCH 1/3] usb: Remove leading underscores from __musb_irq_max Peter Maydell
2011-08-31 20:49 ` [Qemu-devel] [PATCH 2/3] usb-musb: Take a DeviceState* in init function Peter Maydell
2011-08-31 20:49 ` [Qemu-devel] [PATCH 3/3] usb-musb: Add reset function Peter Maydell
2011-09-01 14:38 ` [Qemu-devel] [PATCH 0/3] usb-musb: make qdev-aware Gerd Hoffmann
2011-09-01 15:57 ` Peter Maydell
2011-09-02 7:03 ` Juha.Riihimaki
2011-09-02 7:50 ` Gerd Hoffmann
2011-09-02 8:00 ` Riku Voipio [this message]
2011-09-02 8:42 ` Marcin Juszkiewicz
2011-09-02 14:23 ` Gerd Hoffmann
2011-09-02 8:55 ` Peter Maydell
2011-09-02 10:27 ` Peter Maydell
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=20110902080039.GA6478@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=Juha.Riihimaki@nokia.com \
--cc=kraxel@redhat.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=peter.maydell@linaro.org \
--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 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).