Re: [Intel-gfx] [RFC] drm/i915: Framebuffers need not be limited to 256MB on gen8+.

2015-02-26 Thread Damien Lespiau
On Thu, Feb 26, 2015 at 04:01:32PM +, Chris Wilson wrote: On Thu, Feb 26, 2015 at 09:01:52PM +0530, deepa...@linux.intel.com wrote: From: Deepak S deepa...@linux.intel.com The restriction of pinningFramebuffer to first 256MB is removed from gen8+. Removing the restriction so that FB

Re: [Intel-gfx] [RFC] drm/i915: Framebuffers need not be limited to 256MB on gen8+.

2015-02-26 Thread Chris Wilson
On Thu, Feb 26, 2015 at 09:01:52PM +0530, deepa...@linux.intel.com wrote: From: Deepak S deepa...@linux.intel.com The restriction of pinningFramebuffer to first 256MB is removed from gen8+. Removing the restriction so that FB can be pinned in any space within GTT/PPGTT. Also, for gen8+ no

[Intel-gfx] [RFC] drm/i915: Framebuffers need not be limited to 256MB on gen8+.

2015-02-26 Thread deepak . s
From: Deepak S deepa...@linux.intel.com The restriction of pinningFramebuffer to first 256MB is removed from gen8+. Removing the restriction so that FB can be pinned in any space within GTT/PPGTT. Also, for gen8+ no need to use pin_mappable for Framebuffer also we do not take fence as