[Dev] [Emulator] Tizen emulator development plan
sangho1206.park at samsung.com
Tue Oct 28 11:43:51 GMT 2014
> -----Original Message-----
> From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of Patrick Ohly
> Sent: Tuesday, October 28, 2014 6:41 PM
> To: SeokYeon Hwang
> Cc: john.ji at intel.com; ritu.sood at intel.com; Yu, Yu-cheng;
> dev at lists.tizen.org
> Subject: Re: [Dev] [Emulator] Tizen emulator development plan
> On Tue, 2014-10-28 at 18:29 +0900, SeokYeon Hwang wrote:
> > Dear Tizen emulator developers,
> > As you developers knows, we will merge three branches for features and
> > QEMU2.2 into "tizen" branches in the near future.
> Thanks for notifying the list.
> > Not to make the branches unstable, we make a decision to use
> > alternative branch "tizen_next"
> > That is, you developers need to merge the changes into "tizen_next"
> > branches instead of tizen branches.
> > After testing "tizen_next" branch, we will merge it into "tizen"
> > Here is what will be done in "tizen_next" branches.
> > For "tizen_next" branch under sdk/emulator/qemu.git
> > * Merge three features below.
> > - Features/brillcodec_2i
> > - Features/smp
> > - Features/qt_dr
> Is there an overview somewhere what these features are?
> I recently happened to look at sdk/emulator/qemu.git when trying to
> compile it myself for use with hardware accelerated graphics
> I noticed that the current branch seems to be based on 2.0 with a long
> history of Tizen-specific changes. Do you plan to submit any Tizen-
> specific changes back upstream?
Until now, we just focused on developing just tizen emulator.
I hope to submit some changes to upstream-qemu. However, event injecting
related features may be hard to submit upstream and some features may not
need only qemu changes but also kernel changes. We will select features and
> Speaking of qemu in Tizen, which git trees are really used? There's
> sdk/emulator/qemu.git which seems to be the one actively developed. What
> about platform/upstream/qemu platform/upstream/qemu-accel ?
We don't manage the other 2 gits. I have no idea.
> Both have "tizen" branches, implying that they are used in Tizen 3.0,
> Best Regards, Patrick Ohly
> The content of this message is my personal opinion only and although I
> am an employee of Intel, the statements I make here in no way represent
> Intel's position on the issue, nor am I authorized to speak on behalf of
> Intel on this matter.
> Dev mailing list
> Dev at lists.tizen.org
More information about the Dev