On Mon, Jan 4, 2016 at 6:50 AM, 유재용 <jaeyong....@samsung.com> wrote:
> Oh, I see. That is more interesting. > > > > Just for the curiosity, could you tell me more about the early days before > Mir? > > I'm wondering why you choose to remove surface flinger. > > Is there some constraint if you keep using Surface flinger and another > graphics server? > > > > Thanks, > > Jaeyong > > > Hi Jaeyong, Replacng surfaceflinger with a mir based system compositor - next to the obvious idea of making the android driver based stack similar to the mesa/kms based stack - allows us to separate the user session from the output and input devices allocation. With that it will be easy to have a seamless switch between user sessions or have them running in parallel and move devices between sessions .. and more. regards Andreas
-- Mir-devel mailing list Mir-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/mir-devel
