From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NamZr-0005ah-9w for qemu-devel@nongnu.org; Fri, 29 Jan 2010 03:51:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NamZl-0005Xm-C1 for qemu-devel@nongnu.org; Fri, 29 Jan 2010 03:51:42 -0500 Received: from [199.232.76.173] (port=47449 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NamZk-0005XP-Ud for qemu-devel@nongnu.org; Fri, 29 Jan 2010 03:51:37 -0500 Received: from fmmailgate01.web.de ([217.72.192.221]:59108) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NamZk-0004o4-5e for qemu-devel@nongnu.org; Fri, 29 Jan 2010 03:51:36 -0500 Message-ID: <4B62A18C.5040908@web.de> Date: Fri, 29 Jan 2010 09:51:24 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <195c7a901001210827i29b91f30p3a80c2a8a0c2b4bb@mail.gmail.com> <4B5B7AFB.9040506@codemonkey.ws> <195c7a901001280244i36d09907gb1e9ea387c526255@mail.gmail.com> <195c7a901001280244n13f3afeen45a7c65922b9f0b7@mail.gmail.com> <60cad3f1001281841m24cd0cd0t485cf97b1da60585@mail.gmail.com> In-Reply-To: <60cad3f1001281841m24cd0cd0t485cf97b1da60585@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig75BC5F746E74881B151798B1" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: Merge qemu android List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Turner Cc: Bastien ROUCARIES , qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig75BC5F746E74881B151798B1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable David Turner wrote: > On Thu, Jan 28, 2010 at 2:44 AM, Bastien ROUCARIES < > roucaries.bastien@gmail.com> wrote: >=20 >> They use also craps like sdl :S >> >> > That's totally orthogonal to upstream QEMU. The code for our SDL-suppor= ted > interface is totally separate from the rest > of QEMU changes (or so I hope), and also different from mainline's sdl.= c >=20 >=20 >> I think a total rewritte will be better . >> >> >=20 >> 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 And= roid > system images in an upstream qemu executable, > you will need essentially the following: >=20 > - the content of hw/goldfish_.c in the Android codebase, correspo= nding > to the emulated hardware > - hw/android_arm.c to be ported to upstream too Pushing that bits upstream, converting them to qdev etc. should be a good plan for whoever wants to make a start - even at the risk of "forking" from Google's code base. I guess at some point you will be allowed to adjust your strategy and join that effort simply because maintaining your own tree became too expensive. > - a few changes to the slirp code to setup the default network redirect= ions That sounds strange given that slirp is fairly configurable during runtime these days. Can you elaborate? > - a few changes to vl.c for setup. >=20 > that should be it, though I cannot guarantee success at this point. Als= o you > will miss many features of the emulator, but > as I already said, this should not be a concern for upstream maintainer= s at > all. I think upstream would already benefit from having support for booting images, being able to stimulate most inputs, enabling users to play with virtual phones and allowing developers to debug (upstream) kernels. Jan --------------enig75BC5F746E74881B151798B1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAktioZMACgkQitSsb3rl5xS9VACgtrZZCaVpVlKE3v+XyswlF0e/ 4n0An3CuffDnqTyhnCnE6uFUs35U53VF =AexU -----END PGP SIGNATURE----- --------------enig75BC5F746E74881B151798B1--