Hi Jaeyong,
This is indeed the proper mailing list for such questions, but you can
also use https://answers.launchpad.net/mir
Good question, and I can kind of see how you might think Android is a
Mir client. But it is not.
The relevant stack is really:
Linux kernel and hardware
^
Android HAL (on phones only, not desktops)
^
libhybris (on phones only, not desktops)
^
Mir server (Unity System Compositor)
^
Mir server (Unity8 shell is a server and a client)
^
Apps (Mir clients)
We do not use Surfaceflinger at all anywhere in Ubuntu Touch. Although
in the early days before Mir, we did.
I don't know enough about LXC to comment further on that part.
- Daniel
On 04/01/16 13:05, 유재용 wrote:
Hello Mir developers
I saw an article of running Android as a LXC guest on top of Ubuntu
touch in the following site.
https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
Here, I have some question with the Mir display server. I hope if you
could help me out understand the
details of display server/client relationship with the above example.
In the diagram (see above link), there is a single Mir display server
placed in Ubuntu touch side.
And, it looks like Android is working as a Mir client to the display server.
As I know, Surface flinger is acting as a compositor (i.e., display
server) in Android side. I'm wondering
how do you manage to work Surface flinger as a Mir client?
And, would it be possible to run 2 display servers (i.e., Surface
flinger and Mir) within LXC but giving
different virtual terminals to each other? (Are there some possibilities
of mess-up in GPU context switches
in between display servers?)
If the question is not proper on this mailing list, could you let me
know the pointers that I can these sort of questions?
Thanks,
Jaeyong
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/mir-devel
