From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: "make emu" build and start QEMU target
Date: Thu, 18 Apr 2013 09:16:08 +0200 (CEST) [thread overview]
Message-ID: <511091893.1715486.1366269368744.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CAEBucnDgqjO+3RpdXOgqJzkitSG6P-L=cbOEJws09WZXnnD5kQ@mail.gmail.com>
----- Mail original -----
> Hi,
>
> I'm proposing a project where a "make emu" target would be added to
> Buildroot in order to start a virtualized version of the target.
> This
> would provide developers with the ability to quickly test and
> validate
> their configuration.
I'd be interested in that, I have a few patch for qemu flying around
and having a quick way to test them would help
(I know testing qemu is not the point of your patch, but it would
be usefull for that)
>
> To configure the emu target a new top-level menu, "Target Emulation,"
> would be added. This menu would contain the following options.
>
> Emulation Method -> QEMU
> QEMU Version -> Custom Git Tree | Custom tarball | Custom Version |
> X.Y.Z
> ... Source Configuration similar to Kernel ...
> Machine -> list of machines
> Memory -> Memory in Megabytes
> Additional QEMU Options -> (additional options for command line)
>
> This will start the qemu-system-$(ARCH) version of QEMU with the
> appropriate configuration.
>
hmm... not sure if target emulation makes sense as a separate entry
or if the qemu targets should be simply different machines.
> Thanks,
> Spenser
>
> --
> Spenser Gilliland
> Computer Engineer
> Doctoral Candidate
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2013-04-18 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 18:32 [Buildroot] RFC: "make emu" build and start QEMU target Spenser Gilliland
2013-04-18 7:16 ` Jeremy Rosen [this message]
2013-04-18 18:22 ` Spenser Gilliland
2013-04-19 7:08 ` Jeremy Rosen
2013-04-19 21:20 ` Arnout Vandecappelle
2013-04-19 22:56 ` Thomas Petazzoni
2013-04-20 16:40 ` Spenser Gilliland
2013-04-21 5:21 ` Rob Landley
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=511091893.1715486.1366269368744.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--cc=buildroot@busybox.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 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.