Re: [Qemu-devel] New emulator code base (qemu-android) and "ranchu" virtual board.

[Christopher Covington <cov@codeaurora.org>]

Hi,

[snip--for full message see
https://groups.google.com/d/msg/android-emulator-dev/dltBnUW_HzU/2tSZNLaVzmQJ]

> 5) Relationship with upstream
> 
> In an ideal world, we would not need a fork, and all code would live on
> the upstream QEMU git.
> 
> In reality, things are different: there is little chance that the upstream 
> team would want to maintain 100K+ lines of code that are completely 
> specific to Android, and for good reason. That's why the refactoring effort
> is so important, we need to find a way to maintain the Android-specific
> QEMU patches as small as possible, and push as much stuff into the
> android-emulation library.

I'm curious, have there been previous discussions with the QEMU maintainers
that you can summarize or point me to?

> Even with smaller changes, it's crucial to have a good set of tests, that 
> exercise these Android-specific features, added to the QEMU test suite, and
> clear documentation about the implementation being added. This may require
> a stub or minimal mock version of android-emulation.
> 
> Finally, we may want to dedicate serious engineering resources to better 
> continuous integration of upstream QEMU that would also exercise the 
> Android bits.
> 
> Until we reach such a situation, we will have to maintain a separate fork 
> and continue to rebase it on top of recent QEMU changes.

Thanks,
Cov

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project