[PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge

2016-09-08 Thread Martin van Es
On dinsdag 6 september 2016 21:40:48 CEST Ville Syrjälä wrote: > On Tue, Sep 06, 2016 at 01:56:20PM +0300, Ville Syrjälä wrote: > > Actually I just cooked up another branch [2]. It just throws in some > > memory barriers to the opregion code, and adds a a new debug print so > > to show the resp

[PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge

2016-09-08 Thread Martin van Es
On donderdag 8 september 2016 13:18:41 CEST Ville Syrjälä wrote: > On Thu, Sep 08, 2016 at 12:04:39PM +0200, Martin van Es wrote: > > On dinsdag 6 september 2016 21:40:48 CEST Ville Syrjälä wrote: > > > On Tue, Sep 06, 2016 at 01:56:20PM +0300, Ville Syrjälä wrote: >

[PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge

2016-08-30 Thread Martin van Es
Hi Andrea, I'd be happy to test, but what am I testing when applying these boot parameters? In other words: what should I report? And just to be sure, I THINK I own an IVB but intel is not very vocal about it when searching for familyname. I have a vendor_id : GenuineIntel cpu family

[PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge

2016-08-30 Thread Martin van Es
On dinsdag 30 augustus 2016 11:13:40 CEST Jani Nikula wrote: > On Tue, 30 Aug 2016, Martin van Es wrote: > > Hi Andrea, > > > > I'd be happy to test, but what am I testing when applying these boot > > parameters? In other words: what should I report? > >