>> Except in the cases where it doesn't do what you want, and possibly in
>> the future where it does less of what you want. You've started on a
>> slippery slope, and I'm stopping you before you make things worse.
>>
>> You are going to have to get SoC kernel drivers to add an ioctl that
>> you ca
On Tue, Apr 30, 2013 at 10:19 PM, Dave Airlie wrote:
>>> Except in the cases where it doesn't do what you want, and possibly in
>>> the future where it does less of what you want. You've started on a
>>> slippery slope, and I'm stopping you before you make things worse.
>>>
>>> You are going to ha
On Mon, Apr 29, 2013 at 12:31 PM, Dave Airlie wrote:
>> The reason we (currently) use the dumb buffer interface is because it
>> does pretty much exactly what we need it to, as we only want linear
>> RGB buffers:
>
> Except in the cases where it doesn't do what you want, and possibly in
> the futu
On Tue, Apr 30, 2013 at 10:19 PM, Dave Airlie wrote:
>>> Except in the cases where it doesn't do what you want, and possibly in
>>> the future where it does less of what you want. You've started on a
>>> slippery slope, and I'm stopping you before you make things worse.
>>>
>>> You are going to ha
>> Except in the cases where it doesn't do what you want, and possibly in
>> the future where it does less of what you want. You've started on a
>> slippery slope, and I'm stopping you before you make things worse.
>>
>> You are going to have to get SoC kernel drivers to add an ioctl that
>> you ca
On Mon, Apr 29, 2013 at 12:31 PM, Dave Airlie wrote:
>> The reason we (currently) use the dumb buffer interface is because it
>> does pretty much exactly what we need it to, as we only want linear
>> RGB buffers:
>
> Except in the cases where it doesn't do what you want, and possibly in
> the futu
> The reason we (currently) use the dumb buffer interface is because it
> does pretty much exactly what we need it to, as we only want linear
> RGB buffers:
Except in the cases where it doesn't do what you want, and possibly in
the future where it does less of what you want. You've started on a
sl
> The reason we (currently) use the dumb buffer interface is because it
> does pretty much exactly what we need it to, as we only want linear
> RGB buffers:
Except in the cases where it doesn't do what you want, and possibly in
the future where it does less of what you want. You've started on a
sl
t; the technical side and those I really want to understand.
>
>
>> -Original Message-
>> From: Dave Airlie [mailto:airlied at gmail.com]
>> Sent: 23 April 2013 21:29
>> To: Tom Cooksey
>> Cc: dri-devel; Inki Dae
>> Subject: Re: abuse of dumb ioctls
t; the technical side and those I really want to understand.
>
>
>> -Original Message-
>> From: Dave Airlie [mailto:airl...@gmail.com]
>> Sent: 23 April 2013 21:29
>> To: Tom Cooksey
>> Cc: dri-devel; Inki Dae
>> Subject: Re: abuse of dumb ioctls
age-
> From: Dave Airlie [mailto:airlied at gmail.com]
> Sent: 23 April 2013 21:29
> To: Tom Cooksey
> Cc: dri-devel; Inki Dae
> Subject: Re: abuse of dumb ioctls in exynos
>
> >
> > Having a flag to indicate a dumb buffer allocation is to be used as a
> > s
age-
> From: Dave Airlie [mailto:airl...@gmail.com]
> Sent: 23 April 2013 21:29
> To: Tom Cooksey
> Cc: dri-devel; Inki Dae
> Subject: Re: abuse of dumb ioctls in exynos
>
> >
> > Having a flag to indicate a dumb buffer allocation is to be used as a
> > s
> It appears exynos is passing the generic flags from the dumb ioctls
> straight into the the GEM creation code.
>
> The dumb flags are NOT driver specific, and are NOT to be used in this
> fashion. Please remove this use of the flags from your driver.
>
> I was going to add one new flag to the i
>
> Having a flag to indicate a dumb buffer allocation is to be used as a
> scan-out buffer would be useful for xf86-video-armsoc. We're trying to
> keep that driver as generic as possible and currently the main device-
> specific bits are what flags to pass to DRM_IOCTL_MODE_CREATE_DUMB for
> scan
>
> Having a flag to indicate a dumb buffer allocation is to be used as a
> scan-out buffer would be useful for xf86-video-armsoc. We're trying to
> keep that driver as generic as possible and currently the main device-
> specific bits are what flags to pass to DRM_IOCTL_MODE_CREATE_DUMB for
> scan
On Tue, Apr 23, 2013 at 12:34 PM, Tom Cooksey wrote:
>> It appears exynos is passing the generic flags from the dumb ioctls
>> straight into the the GEM creation code.
>>
>> The dumb flags are NOT driver specific, and are NOT to be used in this
>> fashion. Please remove this use of the flags from
On Tue, Apr 23, 2013 at 12:34 PM, Tom Cooksey wrote:
>> It appears exynos is passing the generic flags from the dumb ioctls
>> straight into the the GEM creation code.
>>
>> The dumb flags are NOT driver specific, and are NOT to be used in this
>> fashion. Please remove this use of the flags from
> It appears exynos is passing the generic flags from the dumb ioctls
> straight into the the GEM creation code.
>
> The dumb flags are NOT driver specific, and are NOT to be used in this
> fashion. Please remove this use of the flags from your driver.
>
> I was going to add one new flag to the i
Hi, Dave
2013/4/18 Dave Airlie
> It appears exynos is passing the generic flags from the dumb ioctls
> straight into the the GEM creation code.
>
> The dumb flags are NOT driver specific, and are NOT to be used in this
> fashion. Please remove this use of the flags from your driver.
>
>
Got it
It appears exynos is passing the generic flags from the dumb ioctls
straight into the the GEM creation code.
The dumb flags are NOT driver specific, and are NOT to be used in this
fashion. Please remove this use of the flags from your driver.
I was going to add one new flag to the interface for S
Hi, Dave
2013/4/18 Dave Airlie
> It appears exynos is passing the generic flags from the dumb ioctls
> straight into the the GEM creation code.
>
> The dumb flags are NOT driver specific, and are NOT to be used in this
> fashion. Please remove this use of the flags from your driver.
>
>
Got it
It appears exynos is passing the generic flags from the dumb ioctls
straight into the the GEM creation code.
The dumb flags are NOT driver specific, and are NOT to be used in this
fashion. Please remove this use of the flags from your driver.
I was going to add one new flag to the interface for S
22 matches
Mail list logo
