From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: testing with qemu, was Re: Angstrom and h2200
Date: Mon, 26 Feb 2007 21:05:31 +0000 [thread overview]
Message-ID: <1172523931.24429.6.camel@localhost.localdomain> (raw)
In-Reply-To: <45E2CC8E.5040505@4g-systems.com>
On Mon, 2007-02-26 at 13:03 +0100, Patrick Fischer wrote:
> Nicola Ranaldo wrote:
> > I already use it to emulate x86 machines, but i was not able before to find
> > the qemu-system-arm command!!! the poky-runqemu documentation seems to be
> > complex, to run the test images at
> > http://www.angstrom-distribution.org/unstable/images/20070120/qemuarm/ i
> > simply used the following command:
> >
> > qemu-system-arm -M versatilepb -kernel
> > zImage-2.6.18-qemuarm-20070120215313.bin -hda
> > Angstrom-gpe-image-test-20070120-qemuarm.rootfs.ext2 -append "root=/dev/sda"
> > When the system asked to calibrate to touchscreen i pressed ESC and gpe
> > appeared!
> >
> This is my test script for qemu
> ./testqemu.sh tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/bootstrap-image-qemux86-20070112211142.rootfs.ext2.gz
Lets reinvent the wheel too...
This should work just the same as
poky-runqemu tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/bootstrap-image-qemux86-20070112211142.rootfs.ext2
(except the same command works with qemuarm and several zaurus images if
you have the right qemu)
Note you have to use an ext2 image, not a gzipped one but my setup
generates ext2 files, not ext2.gz ones...
> > I did not use the file modules-2.6.18-qemuarm.tgz.... is there a
> > reason it's there?
Anyone developing a kernel finds it useful, otherwise just ignore it.
Regards,
Richard
prev parent reply other threads:[~2007-02-26 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 12:26 Angstrom and h2200 Nicola Ranaldo
[not found] ` <7010259346.20070225203430@gmail.com>
2007-02-26 10:44 ` Nicola Ranaldo
2007-02-26 11:15 ` testing with qemu, was " Nicola Ranaldo
2007-02-26 12:03 ` Patrick Fischer
2007-02-26 21:05 ` Richard Purdie [this message]
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=1172523931.24429.6.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.