All of lore.kernel.org
 help / color / mirror / Atom feed
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 21:16:25 +0200	[thread overview]
Message-ID: <4EA1C509.40104@vmware.com> (raw)
In-Reply-To: <CAPM=9tym04JW9R_mHQ6m1TR3W3tH7nZt65Eq+G9dpxStSLvS7A@mail.gmail.com>

On 10/21/2011 06:48 PM, Dave Airlie wrote:
>> Why do we have CONTROL_ALLOW on all modesetting ioctls?, also this code in
>> drm_crtc.c  seems odd:
>>      
> The plan was to allow a master daemon to create seats and compute
> nodes, on reflection it probably didn't need *all* the modesetting
> ioctls,
> just the GetResources one.
>
> So gdm or some equivalent would keep control over the control node,
> and could be used to establish seats via render nodes.
> Render nodes could have various crtc/outputs assigned to them.
> A GPGPU render node would have 0 output pieces attached.
>
>    
>> if (file_priv->master->minor->type == DRM_MINOR_CONTROL) {
>> ...
>>
>> Isn't that equivalent to
>>
>> if (file_priv->minor->type == DRM_MINOR_CONTROL) { ?
>>      
> Yeah most likely just over thinking something. should be the same.
>
> I had a tree on k.org with this stuff more fleshed out,
> I've just pushed it out here:
> http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-render-nodes
>
>    

OK. Thanks. Got a better understanding what it's all about now.

/Thomas


> Dave.
>    

      reply	other threads:[~2011-10-21 19:18 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
2011-10-21 16:48       ` Dave Airlie
2011-10-21 19:16         ` Thomas Hellstrom [this message]

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=4EA1C509.40104@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.