On Tue, 2005-06-28 at 20:13 -0400, Jon Smirl wrote: > On 6/28/05, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: > > > > > The callgate for getting to mode setting has to be in the kernel. That > > > provides a standard API and a secure user-root transition. After the > > > call is in the kernel each driver can choose to satisfy the call > > > in-kernel or use something like call_userhelper() to do the work in > > > user space. > > > > As I explained already, I think it should be a userland daemon, that's > > really the best way to deal with access control and would fix all of the > > issues. > > How do I communicate my desired mode to the daemon?
We have to define an interface of course. The protocol there could go over a unix socket I suppose. Ben. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
