On Mon, 2019-06-10 at 12:32 +0300, Jani Nikula wrote:
> Right, I've added a call to drm_connector_update_edid_property() in v2
> to address this issue.
Confirmed this fixed the EDID override data.
> Can't think of why this would happen; the backtrace might offer clues.
Unfortunately I wasn't ab
On Sat, 08 Jun 2019, Paul Wise wrote:
> On Sat, 2019-06-08 at 13:10 +0800, Paul Wise wrote:
>
>> I've tested these two patches on top of Linux v5.2-rc3 and the EDID
>> override works correctly on an Intel Ironlake GPU with a monitor that
>> lost its EDID a while ago.
>
> While testing I noticed a
On Fri, 2019-06-07 at 17:10 +0200, Daniel Vetter wrote:
> As discussed on irc, we need tested-by here from the reporters since
> there's way too many losing and frustrangingly few winning moves here.
Tested-by: Paul Wise
I've tested these two patches on top of Linux v5.2-rc3 and the EDID
overri
On Sat, 2019-06-08 at 13:10 +0800, Paul Wise wrote:
> I'll test that it also works with an nVidia GPU & noveau drivers
> later today once that system is available.
Same results as with the Intel GPU:
Correct screen resolution but missing EDID override data.
--
bye,
pabs
https://bonedaddy.net/
On Fri, 2019-06-07 at 17:10 +0200, Daniel Vetter wrote:
> As discussed on irc, we need tested-by here from the reporters since
> there's way too many losing and frustrangingly few winning moves here.
I'm building it now, hopefully will be done today.
--
bye,
pabs
https://bonedaddy.net/pabs3/
On Sat, 2019-06-08 at 13:10 +0800, Paul Wise wrote:
> I've tested these two patches on top of Linux v5.2-rc3 and the EDID
> override works correctly on an Intel Ironlake GPU with a monitor that
> lost its EDID a while ago.
While testing I noticed a couple of things:
While everything the GUI is t
On Fri, Jun 07, 2019 at 02:05:13PM +0300, Jani Nikula wrote:
> We've moved the override and firmware EDID (simply "override EDID" from
> now on) handling to the low level drm_do_get_edid() function in order to
> transparently use the override throughout the stack. The idea is that
> you get the ove
We've moved the override and firmware EDID (simply "override EDID" from
now on) handling to the low level drm_do_get_edid() function in order to
transparently use the override throughout the stack. The idea is that
you get the override EDID via the ->get_modes() hook.
Unfortunately, there are scen
