To work properly, the DRM needs an area of memory per open of the device
which stores information on whether that fd is authenticated and also to
have a unique identifier for use in the lock. Currently we use
drm_find_file_by_proc to get the private data and use the pid as the
unique identifier, b
On Fri, 2003-03-14 at 13:59, Eric Anholt wrote:
> To work properly, the DRM needs an area of memory per open of the device
> which stores information on whether that fd is authenticated and also to
> have a unique identifier for use in the lock. Currently we use
> drm_find_file_by_proc to get the
Eric Anholt writes:
> shouldn't be too big of an issue. The unique identifier is the big
> problem and the fileops trick should work for that.
>
> However, is this going to get easier some day? Are there any plans to
> pass the struct file down to the drivers and have a void * in there for
In message <[EMAIL PROTECTED]>, Eric Anholt writes:
>To work properly, the DRM needs an area of memory per open of the device
>which stores information on whether that fd is authenticated and also to
>have a unique identifier for use in the lock.
I have some plans for this for 6.x but we would hav
4 matches
Mail list logo
