Is VT sharing possbile with weston 1.8.0 with fbdev backend?

[Daniel Stone]

Hi Vikas,

On 27 October 2015 at 15:22, Vikas Patil Gmail <vikasmpatil at gmail.com> wrote:
> Thanks for your comment and suggestions. I will surely ask to freesacle
> regarding it.
>
> I was thinking VTs sharing don't have dependencies on GAL2D. Is possible
> could you point me the hack you mentioned so I can give try?
>
> Is VT sharing possible if I use GLES renderer with fbdev backend?
>
> I am trying splash screen and want to avoid flicker/screen clear. Using fb0
> for splash and fb1 for Weston.

Currently the VT code assumes that fbdev is being used for display;
both GAL2D and the changes Freescale have made to the fbdev backend
(the hacks I mentioned above), mean that we can't guarantee they won't
break the core VT code.

Cheers,
Daniel

> Thanks & Regards,
> Vikash
> ________________________________
> From: Daniel Stone
> Sent: ‎10/‎27/‎2015 7:43 PM
> To: Vikas Patil
> Cc: wayland mailing list
> Subject: Re: Is VT sharing possbile with weston 1.8.0 with fbdev backend?
>
> Hi,
>
> On 27 October 2015 at 13:12, Vikas Patil <vikasmpatil at gmail.com> wrote:
>> Does anyone know here if weston switches between VTs (Virtual Terminal)
>> while starting weston using "fbdev" backend and GLA2D (Freescale specific
>> renderer)? If yes then is there any way
>> to stop switching between VTs and still star it successfully?
>>
>> I am using weston 1.8.0 on iMX platform with linux 3.14.28 (framebuffer
>> console with logo, Virtual Terminal enabled).
>>
>> I used to do this with X11 using option called "sharedvt" (-sharevts:
>> share
>> VTs with another X server) to avoid the flicker/screen clear displayed due
>> to without using this option.
>
> The GAL2D backend is maintained completely separately by Freescale,
> and has never been sent upstream. Unfortunately due to this (the hacks
> in the code make it impossible to merge in its current form), we
> cannot support the patches you have. Please get in touch with
> Freescale and request support from them.
>
> Alternately, there is support developing in Mesa for using the etnaviv
> (Vivante 3D GPU) and imx-drm (Freescale 2D-ACE engine) open-source
> drivers on i.MX6. If you are not able to get help from Vivante, this
> could be a good option to pursue, as it has far better support.
>
> Cheers,
> Daniel