On Thu, 05 Nov 2015, Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> wrote: > On 11/03/2015 04:44 AM, Maarten Lankhorst wrote: >> Hey, >> >> Op 03-11-15 om 12:32 schreef Jani Nikula: >>> On Tue, 03 Nov 2015, Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> wrote: >>>> On Tue, Nov 03, 2015 at 08:31:41AM +0100, Maarten Lankhorst wrote: >>>>> Those platforms have the same bug as haswell, and the same fix applies to them. >>> How about Broxton? IS_DDI matches that. >>> >>> Jani. >>> >> Judging from irc it's very likely it suffers from the same problem, but it would be nice if we had someone who could confirm. :) > > It won't hurt (much) if we apply this workaround and it doesn't affect > BXT, so I think we may as well apply given what we know of BXT's lineage. Pushed this one patch to drm-intel-next-fixes, with cc: stable v4.3. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
