On Fri, Apr 15, 2016 at 06:23:33PM +0200, Nicolas Ferre wrote:
> From: Boris Brezillon
>
> All modes exposed by simple panels should be tagged as driver defined
> modes.
> Moreover, if a panel supports only one mode, this mode is obviously the
> preferred one.
>
> Doing this also fix a problem
From: Boris Brezillon
All modes exposed by simple panels should be tagged as driver defined
modes.
Moreover, if a panel supports only one mode, this mode is obviously the
preferred one.
Doing this also fix a problem occurring when a 'video=' parameter is
Le 28/05/2015 16:25, Boris Brezillon a écrit :
> Hi Thierry,
>
> Could you have a look at this patch (a.k.a. ping) ?
It's been a long time and... It seems that this patch doesn't apply
anymore but:
Reviewed-by: Nicolas Ferre
So, I'm updating it and resending right now.
Bye,
> On Thu, 30
Hi Thierry,
Could you have a look at this patch (a.k.a. ping) ?
Best Regards,
Boris
On Thu, 30 Apr 2015 16:39:30 +0200
Boris Brezillon wrote:
> All modes exposed by simple panels should be tagged as driver defined
> modes.
> Moreover, if a panel supports only one mode, this mode is obviously
Le 30/04/2015 16:39, Boris Brezillon a écrit :
> All modes exposed by simple panels should be tagged as driver defined
> modes.
> Moreover, if a panel supports only one mode, this mode is obviously the
> preferred one.
>
> Doing this also fix a problem occurring when a 'video=' parameter is
All modes exposed by simple panels should be tagged as driver defined
modes.
Moreover, if a panel supports only one mode, this mode is obviously the
preferred one.
Doing this also fix a problem occurring when a 'video=' parameter is passed
on the kernel cmdline. In some cases the user provided