Multiple Display Support

[Pekka Paalanen]

On Mon, 25 Aug 2014 18:36:07 +0530
Abhijit Potnis <abhijitpotnis at gmail.com> wrote:

> Hello Pekka,
> 
> Weston does detect the two connectors, log below show that :

Please paste the whole log.

> [22:29:40.882] Output None1, (connector 4, crtc 10)
>                mode 1280x800 at 57.4, preferred, current

Looks like your kernel driver is saying the connector type is "None",
which is strange (drmModeConnector::connector_type == 0).

> [22:29:40.919] Failed to initialize backlight
> [22:29:40.919] EDID data 'DEL', 'DELL 2007WFP', 'NF409794051L'
> [22:29:40.919] Output HDMI1, (connector 12, crtc 14)
>                mode 1680x1050 at 59.9, preferred, current
>                mode 1280x1024 at 75.0
>                mode 1280x1024 at 60.0
>                mode 1152x864 at 75.0
>                mode 1024x768 at 75.1
>                mode 1024x768 at 60.0
>                mode 800x600 at 75.0
>                mode 800x600 at 60.3
>                mode 640x480 at 7[80981.215270] HDCP: hdcp_3des_cb:
> hdcp_keys not loaded = 0
> 
> I also noticed that when launched without the --connector argument, weston
> shell launches on one display ( Say HDMI ), the other display (LCD) goes
> BLACK and even the fbcon is not visible. This does mean someone is
> rendering on that screen. But I wasn't able to move any Weston windows to
> the LCD display.

Seems like you get to inspect what Weston does with KMS, and then debug
your DRM driver on where it goes wrong, or is Weston perhaps using a
KMS configuration that is not supposed to work on your driver.

Have you tried the DRM backend with --use-pixman? That should rule out
any rendering problems, as it will render with CPU and use dumb buffers
to set up the outputs.

Also, even if you are not able to see anything on the 2nd output, are
you able to move the pointer and windows there?


Thanks,
pq

> On Mon, Aug 25, 2014 at 6:10 PM, Abhijit Potnis <abhijitpotnis at gmail.com>
> wrote:
> 
> >
> >
> >
> > On Mon, Aug 25, 2014 at 4:59 PM, Pekka Paalanen <ppaalanen at gmail.com>
> > wrote:
> >
> >> On Mon, 25 Aug 2014 15:04:08 +0530
> >> Abhijit Potnis <abhijitpotnis at gmail.com> wrote:
> >>
> >> > Hello ,
> >> >
> >> > I have a doubt regarding Wayland/Weston's support for multiple
> >> displays. I
> >> > am of the assumption that "multiple display" means support of two or
> >> more
> >> > monitors(or displays) simultaneously like a extended desktop mode and
> >> the
> >> > ability to drag-and-drop windows from one display to the other.
> >> >
> >> > Am I right regarding my understanding of "multiple display" support in
> >> > Wayland ?
> >>
> >> Yes.
> >>
> >
> > Thanks. Now that we know multiple display is supported, We will have to
> > see as to why it doesn't work on the OMAP board.
> >
> >>
> >> > I am are running Wayland/Weston 1.5 on the TI Jacinto J6 board with two
> >> > displays connected ( via HDMI and LCD connectors ). I am unable to get
> >> the
> >> > extended display started. Do I have to change/add any thing in the
> >> > weston.ini file to get the extended display started ?
> >>
> >> AFAIK, Weston-DRM automatically takes all connected outputs into use,
> >> unless specifically told not to in weston.ini, or the kernel reports
> >> them as disconnected.
> >>
> >
> >> I assume fbcon runs fine cloned to both displays, right?
> >>
> >
> > Console runs fine on both the displays.
> >
> >
> >>
> >> You are using Weston with the DRM backend, right?
> >>
> >
> > Yes, we are using DRM backend. We are also able to run Weston on HDMI and
> > LCD individually by supplying --connector=<connectorID> argument.
> > When run without the connector arg it picks up the LCD screen and HDMI
> > remains bank ( no windows can be moved across to the HDMI screen )
> >
> >
> >>
> >> Fbdev-backend cannot deal with more than one output.
> >>
> >>
> >
> > Thanks,
> >> pq
> >>
> >
> >