From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57697) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xm2zm-0003K5-CO for qemu-devel@nongnu.org; Wed, 05 Nov 2014 10:59:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xm2ze-0005NC-TC for qemu-devel@nongnu.org; Wed, 05 Nov 2014 10:59:42 -0500 Received: from smtp.codeaurora.org ([198.145.11.231]:50771) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xm2ze-0005Mz-N9 for qemu-devel@nongnu.org; Wed, 05 Nov 2014 10:59:34 -0500 Message-ID: <545A4962.4050902@codeaurora.org> Date: Wed, 05 Nov 2014 10:59:30 -0500 From: Christopher Covington MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] New emulator code base (qemu-android) and "ranchu" virtual board. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Android emulator development , digit@google.com, QEMU Developers 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