On 10 June 2016 at 21:08, Eric Anholt wrote:
> Emil Velikov writes:
>
>> On 10 June 2016 at 00:42, Eric Anholt wrote:
>>> Rob Herring writes:
>>>
Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
to authorized clients and render nodes. Without this, access from
Emil Velikov writes:
> On 10 June 2016 at 21:08, Eric Anholt wrote:
>> Emil Velikov writes:
>>
>>> On 10 June 2016 at 00:42, Eric Anholt wrote:
Rob Herring writes:
> Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
> to authorized clients and render n
Emil Velikov writes:
> On 10 June 2016 at 00:42, Eric Anholt wrote:
>> Rob Herring writes:
>>
>>> Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
>>> to authorized clients and render nodes. Without this, access from render
>>> nodes fails.
>>
>> We've already got a fix
On 10 June 2016 at 00:42, Eric Anholt wrote:
> Rob Herring writes:
>
>> Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
>> to authorized clients and render nodes. Without this, access from render
>> nodes fails.
>
> We've already got a fix to add RENDER_ALLOW submitted in
Hi Rob,
On 9 June 2016 at 22:19, Rob Herring wrote:
> Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
> to authorized clients and render nodes. Without this, access from render
> nodes fails.
>
> Signed-off-by: Rob Herring
> ---
> drivers/gpu/drm/vc4/vc4_drv.c | 18
Rob Herring writes:
> Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
> to authorized clients and render nodes. Without this, access from render
> nodes fails.
We've already got a fix to add RENDER_ALLOW submitted in the latest
drm-vc4-fixes. There's no reason to requir
Ioctls generally have DRM_AUTH and DRM_RENDER_ALLOW set to restrict them
to authorized clients and render nodes. Without this, access from render
nodes fails.
Signed-off-by: Rob Herring
---
drivers/gpu/drm/vc4/vc4_drv.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
d
