On Sun, 19 Sep 2004 14:45:37 +1000, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: > One issue here... When we discussed all of this with Keith, we wanted > a mecanism where the user can set the mode without "owning" the device.
The owning part is for multiuser systems. If I have four users logged into the same system I have to assign them ownership of their video devices so that they can't mess with each other. I want to avoid needing root priv to change the monitor mode. > Typically, with X: We don't want X itself to have to be the one setting > the mode, but rather set the mode and have X be notified properly before > and after it happens so it can "catch up". This is going to require some more thought. Mode setting needs two things, a description of the mode timings and a location of the scan out buffer. With multiple heads you can't just assume that the buffer starts at zero. There also the problem of the buffer increasing in size and needing to be moved since it won't fit where it is. Keith, how should this work for X? We have to make sure all DRI users of the buffer are halted, get a new location for the buffer, set the mode, free the old buffer, notify all of the DRI clients that their target has been wiped and has a new size. I was wanting to switch mode setting into an atomic operation where you passed in both the mode timings and buffer location. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
