From: Bastien ROUCARIES <roucaries.bastien@gmail.com>
To: David Turner <digit@google.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Merge qemu android
Date: Fri, 29 Jan 2010 18:08:30 +0100 [thread overview]
Message-ID: <195c7a901001290908n780bbabbhd56d98bf2329472@mail.gmail.com> (raw)
In-Reply-To: <60cad3f1001281841m24cd0cd0t485cf97b1da60585@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
On Fri, Jan 29, 2010 at 3:41 AM, David Turner <digit@google.com> wrote:
> On Thu, Jan 28, 2010 at 2:44 AM, Bastien ROUCARIES <
> roucaries.bastien@gmail.com> wrote:
>
>> They use also craps like sdl :S
>>
>>
> That's totally orthogonal to upstream QEMU. The code for our SDL-supported
> interface is totally separate from the rest
> of QEMU changes (or so I hope), and also different from mainline's sdl.c
>
>
>> I think a total rewritte will be better .
>>
>>
>
>> How can incremently add a new arch to qemu or a new plateform ?
>>
>> Depends on what your goal is. If all you want is to be able to run Android
> system images in an upstream qemu executable,
> you will need essentially the following:
>
> - the content of hw/goldfish_<xxxx>.c in the Android codebase,
> corresponding to the emulated hardware
> - hw/android_arm.c to be ported to upstream too
> - a few changes to the slirp code to setup the default network redirections
> - a few changes to vl.c for setup.
>
It is exactly that I asked.
Thank you :)
> that should be it, though I cannot guarantee success at this point. Also
> you will miss many features of the emulator, but
> as I already said, this should not be a concern for upstream maintainers at
> all.
>
>
>
>> Bastien
>>
>> Regards,
>>>
>>> Anthony Liguori
>>>
>>> Regards
>>>>
>>>> Bastien
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 3480 bytes --]
next prev parent reply other threads:[~2010-01-29 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:27 [Qemu-devel] Merge qemu android Bastien ROUCARIES
2010-01-21 18:13 ` [Qemu-devel] " Bastien ROUCARIES
2010-01-23 22:40 ` [Qemu-devel] " Anthony Liguori
[not found] ` <195c7a901001280244i36d09907gb1e9ea387c526255@mail.gmail.com>
2010-01-28 10:44 ` Fwd: " Bastien ROUCARIES
2010-01-28 19:43 ` Laurent Desnogues
2010-01-29 2:41 ` David Turner
2010-01-29 8:51 ` [Qemu-devel] " Jan Kiszka
2010-01-29 15:51 ` [Qemu-devel] " Anthony Liguori
2010-01-29 17:08 ` Bastien ROUCARIES [this message]
2010-01-29 2:35 ` David Turner
2010-01-29 12:22 ` Luiz Capitulino
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=195c7a901001290908n780bbabbhd56d98bf2329472@mail.gmail.com \
--to=roucaries.bastien@gmail.com \
--cc=digit@google.com \
--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).