On 04/07/2014 02:18 PM, Siluvery, Arun wrote:
On 27/03/2014 22:23, Chris Wilson wrote:
On Thu, Mar 27, 2014 at 03:28:26PM +,
arun.siluv...@linux.intel.com wrote:
From: "Siluvery, Arun"
This patch series adds a new ioctl to resize a gem object.
I'm tired, but off the top of my head, I t
On 27/03/2014 22:23, Chris Wilson wrote:
On Thu, Mar 27, 2014 at 03:28:26PM +, arun.siluv...@linux.intel.com wrote:
From: "Siluvery, Arun"
This patch series adds a new ioctl to resize a gem object.
I'm tired, but off the top of my head, I think you can do away with the
magic extension to
On 27/03/2014 22:23, Chris Wilson wrote:
On Thu, Mar 27, 2014 at 03:28:26PM +, arun.siluv...@linux.intel.com wrote:
From: "Siluvery, Arun"
This patch series adds a new ioctl to resize a gem object.
I'm tired, but off the top of my head, I think you can do away with the
magic extension to
On Thu, Mar 27, 2014 at 03:28:26PM +, arun.siluv...@linux.intel.com wrote:
> From: "Siluvery, Arun"
>
> This patch series adds a new ioctl to resize a gem object.
I'm tired, but off the top of my head, I think you can do away with the
magic extension to create_ioctl. If we allow any one to f
From: "Siluvery, Arun"
This patch series adds a new ioctl to resize a gem object.
This is required in cases where the actual size of the object is not known
at the time of creation and there is chance that we may need more space later.
A typical use case is memory allocation for mipmaps where y