RE: Question about multi-displays control on wayland protocol‏

[Yang Andy]

Hi Pekka

Thank you very much for your reply.

I got your meaning,but i have another question.

Is there any necessary for modify weston/compositor?

Because i investigate source code[compositor-fbdev.c],and find that compositor open device [/dev/fb0].

It seems that the compositor is constant with /dev/fb0,how does compositor direct surfaces to specific outputs(fb0/fb1...)

Could you give me some advice?

[source code]
backend_init(struct wl_display *display, int *argc, char *argv[],
         struct weston_config *config)
{
    /* TODO: Ideally, available frame buffers should be enumerated using
     * udev, rather than passing a device node in as a parameter. */
    struct fbdev_parameters param = {
        .tty = 0, /* default to current tty */
        .device = "/dev/fb0", /* default frame buffer */
        .use_gl = 0,
    };

    parse_options(fbdev_options, ARRAY_LENGTH(fbdev_options), argc, argv);

    return fbdev_compositor_create(display, argc, argv, config, &param);
}

Best regards

Andy
> Date: Thu, 9 Oct 2014 14:10:02 +0300
> From: ppaalanen at gmail.com
> To: williamyang13 at hotmail.com
> CC: wayland-devel at lists.freedesktop.org
> Subject: Re: Question about multi-displays control on wayland protocol‏
> 
> On Thu, 9 Oct 2014 06:34:21 +0000
> Yang Andy <williamyang13 at hotmail.com> wrote:
> 
> > Hello everyone
> > 
> > I have one question about multi-displays control on wayland protocol.
> > 
> > I want to control dual displays on wayland protocol.
> > 
> > For example,Display1 which is used to render map,while display2 which is used to render mp3-palyer.
> > 
> > Could anyone give me some advice about how to design the software architecture based on wayland protocol?
> > 
> > [wayland/weston version]
> > 1.5
> > 
> > [TizenIVI version]
> > TizenCommon
> 
> I think that will be specific to the shell protocol you will be using.
> 
> All outputs are advertized as globals, but you need a shell to able to
> direct surfaces to specific outputs, and perhaps to identify which
> output you want to pick. That is when you want the application to
> choose which output it occupies.
> 
> In your example use case, it might be more appropriate to leave the
> output assignment for the window manager, and just communicate the
> purpose of the surface to the window manager. That too will happen
> through a shell.
> 
> 
> Thanks,
> pq
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20141010/9f58a18c/attachment.html>