<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:????
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Pekka<br><br>Thank you very much for your reply.<br><br>I got your meaning,but i have another question.<br><br>Is there any necessary for modify weston/compositor?<br><br>Because i investigate source code[compositor-fbdev.c],and find that compositor open device [/dev/fb0].<br><br>It seems that the compositor is constant with /dev/fb0,how does compositor direct surfaces to specific outputs(fb0/fb1...)<br><br>Could you give me some advice?<br><br>[source code]<br>backend_init(struct wl_display *display, int *argc, char *argv[],<br> struct weston_config *config)<br>{<br> /* TODO: Ideally, available frame buffers should be enumerated using<br> * udev, rather than passing a device node in as a parameter. */<br> struct fbdev_parameters param = {<br> .tty = 0, /* default to current tty */<br> .device = "/dev/fb0", /* default frame buffer */<br> .use_gl = 0,<br> };<br><br> parse_options(fbdev_options, ARRAY_LENGTH(fbdev_options), argc, argv);<br><br> return fbdev_compositor_create(display, argc, argv, config, ¶m);<br>}<br><br>Best regards<br><br>Andy<br><div>> Date: Thu, 9 Oct 2014 14:10:02 +0300<br>> From: ppaalanen@gmail.com<br>> To: williamyang13@hotmail.com<br>> CC: wayland-devel@lists.freedesktop.org<br>> Subject: Re: Question about multi-displays control on wayland protocolþ<br>> <br>> On Thu, 9 Oct 2014 06:34:21 +0000<br>> Yang Andy <williamyang13@hotmail.com> wrote:<br>> <br>> > Hello everyone<br>> > <br>> > I have one question about multi-displays control on wayland protocol.<br>> > <br>> > I want to control dual displays on wayland protocol.<br>> > <br>> > For example,Display1 which is used to render map,while display2 which is used to render mp3-palyer.<br>> > <br>> > Could anyone give me some advice about how to design the software architecture based on wayland protocol?<br>> > <br>> > [wayland/weston version]<br>> > 1.5<br>> > <br>> > [TizenIVI version]<br>> > TizenCommon<br>> <br>> I think that will be specific to the shell protocol you will be using.<br>> <br>> All outputs are advertized as globals, but you need a shell to able to<br>> direct surfaces to specific outputs, and perhaps to identify which<br>> output you want to pick. That is when you want the application to<br>> choose which output it occupies.<br>> <br>> In your example use case, it might be more appropriate to leave the<br>> output assignment for the window manager, and just communicate the<br>> purpose of the surface to the window manager. That too will happen<br>> through a shell.<br>> <br>> <br>> Thanks,<br>> pq<br></div> </div></body>
</html>