From: Thomas Hellstrom <thellstrom@vmware.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: The controlD device
Date: Fri, 21 Oct 2011 18:03:27 +0200 [thread overview]
Message-ID: <4EA197CF.4080108@vmware.com> (raw)
In-Reply-To: <CAPM=9txbA1o2aP9u4Mk025-46VhUyp9+e0ceMJcCvnbyuuWOKw@mail.gmail.com>
On 10/21/2011 04:36 PM, Dave Airlie wrote:
> On Fri, Oct 21, 2011 at 3:18 PM, Dave Airlie<airlied@gmail.com> wrote:
>
>> On Fri, Oct 21, 2011 at 3:06 PM, Thomas Hellstrom<thellstrom@vmware.com> wrote:
>>
>>> Dave,
>>>
>>> What is the drm control device nodes really used for?
>>>
>>> On my fc14 system it seems like it has world rw privileges, and full access
>>> to all modesetting ioctls.
>>> Is that the intention?
>>>
>> No, and I just realised we packaged a broken udev rule.
>>
>> It should be root only, oops.
>>
>> Its intention is for setting up multi-seat and gpgpu access to the drm.
>>
>> change /etc/udev/rules.d/91-modeset.rules to be 0600.
>>
> I've filed updates to Fedora to fix this, no other distro should be
> using or caring about these device nodes yet, since we never really
> got GPGPU going yet.
>
> Dave.
>
Sounds good. I was actually mostly curios on the intended usage pattern
of the control node.
I found some things on the DRM wikis, but it doesn't at all seem
consistent with what's in DRM.
Why do we have CONTROL_ALLOW on all modesetting ioctls?, also this code
in drm_crtc.c seems odd:
if (file_priv->master->minor->type == DRM_MINOR_CONTROL) {
...
Isn't that equivalent to
if (file_priv->minor->type == DRM_MINOR_CONTROL) { ?
Any enlightenment would be appreciated.
Thanks,
/Thomas
next prev parent reply other threads:[~2011-10-21 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 14:06 The controlD device Thomas Hellstrom
2011-10-21 14:18 ` Dave Airlie
2011-10-21 14:36 ` Dave Airlie
2011-10-21 16:03 ` Thomas Hellstrom [this message]
2011-10-21 16:48 ` Dave Airlie
2011-10-21 19:16 ` Thomas Hellstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA197CF.4080108@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.