Anthony is right, and unfortunately the Android team doesn't have the bandwidth to support sending patches to upstream at the moment.
Note that our version of QEMU is a rather complex mix of 0.8.2 and upstream. I routinely cherry pick upstream improvements and incorporate them to the codebase. However, I'm also pretty conservative and try to avoid stuff we don't depend on and which risk breaking other stuff easily so many parts don't get in, or are implemented differently. Also, many, many things in the Android emulator codebase have very little value for upstream qemu, imho. Bastien, what specific features are you interested in ? I can still have a look at what would be required to generate the corresponding upstream patch. On Sat, Jan 23, 2010 at 2:40 PM, Anthony Liguori <anth...@codemonkey.ws>wrote: > On 01/21/2010 10:27 AM, Bastien ROUCARIES wrote: > >> Hi, >> >> What is the step in order to get qemu android merged mainline ? >> >> http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary >> >> > > Send patches. > > It's very difficult to merge downstream code unless that entire downstream > is committed to working through upstream. I'd suggest encouraging the > Android developers to commit to pushing all of the functionality upstream > before going down this path. > > Regards, > > Anthony Liguori > > Regards >> >> Bastien >> >> >> >> > > > >
