From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: "make emu" build and start QEMU target
Date: Fri, 19 Apr 2013 09:08:39 +0200 (CEST) [thread overview]
Message-ID: <503878220.1752654.1366355319386.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CAEBucnBMtJ-_E0bwkAZ_anhShJD8cz6TVrs9JSuBkqVSMMRYkA@mail.gmail.com>
Cordialement
J?r?my Rosen
fight key loggers : write some perl using vim
----- Mail original -----
> Jeremy,
>
> Thanks for responding.
>
> > 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)
>
> Very much so this is a good use case. I looked in patchwork but
> couldn't find any patches related to QEMU. Can you point me to them?
>
they are not in patchwork we work on QEMU and submit upstream stuff that is
not buildroot specific and shouldn't be a buildroot patch
> > hmm... not sure if target emulation makes sense as a separate entry
> > or if the qemu targets should be simply different machines.
>
> I'm not sure what you mean by this can you explain further?
>
I was commenting on the idea of having an emulation sub-menu
> Spenser
>
> --
> Spenser Gilliland
> Computer Engineer
> Doctoral Candidate
>
next prev parent reply other threads:[~2013-04-19 7:08 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
2013-04-18 18:22 ` Spenser Gilliland
2013-04-19 7:08 ` Jeremy Rosen [this message]
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=503878220.1752654.1366355319386.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox