Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/stolen: Deduce base of reserved portion as top-size on vlv

2018-03-16 Thread Chris Wilson
Quoting Ville Syrjälä (2018-03-16 12:00:45) > On Mon, Mar 12, 2018 at 04:52:06PM +, Chris Wilson wrote: > > On Valleyview, the HW deduces the base of the reserved portion of stolen > > memory as being (top - size) and the address field within > > GEN6_STOLEN_RESERVED is set to 0. Add yet

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/stolen: Deduce base of reserved portion as top-size on vlv

2018-03-16 Thread Ville Syrjälä
On Mon, Mar 12, 2018 at 04:52:06PM +, Chris Wilson wrote: > On Valleyview, the HW deduces the base of the reserved portion of stolen > memory as being (top - size) and the address field within > GEN6_STOLEN_RESERVED is set to 0. Add yet another GEN6_STOLEN_RESERVED > reader to cope with the

[Intel-gfx] [PATCH v2 3/3] drm/i915/stolen: Deduce base of reserved portion as top-size on vlv

2018-03-12 Thread Chris Wilson
On Valleyview, the HW deduces the base of the reserved portion of stolen memory as being (top - size) and the address field within GEN6_STOLEN_RESERVED is set to 0. Add yet another GEN6_STOLEN_RESERVED reader to cope with the subtly different path required for vlv. v2: Avoid using reserved_base =