On Fri, Jan 11, 2019 at 9:19 AM Ivan Mironov wrote:
>
> On Wed, 2019-01-09 at 15:52 +, Sasha Levin wrote:
> > Hi,
> >
> > [This is an automated email]
> >
> > This commit has been processed because it contains a "Fixes:" tag,
> > fixing commit: 79e539453b34 DRM: i915: add mode setting
On Wed, 2019-01-09 at 15:52 +, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 79e539453b34 DRM: i915: add mode setting support.
>
> The bot has tested the following trees: v4.20.0, v4.19.13,
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 79e539453b34 DRM: i915: add mode setting support.
The bot has tested the following trees: v4.20.0, v4.19.13, v4.14.91, v4.9.148,
v4.4.169, v3.18.131.
v4.20.0: Failed to apply!
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 79e539453b34 DRM: i915: add mode setting support.
The bot has tested the following trees: v4.20.0, v4.19.13, v4.14.91, v4.9.148,
v4.4.169, v3.18.131.
v4.20.0: Failed to apply!
Strict requirement of pixclock to be zero breaks support of SDL 1.2
which contains hardcoded table of supported video modes with non-zero
pixclock values[1].
To better understand which pixclock values are considered valid and how
driver should handle these values, I briefly examined few existing
