On Sun, 2004-09-19 at 04:43, Jon Smirl wrote: > Original proposal..... > At OLS we talked about a system like this for setting video modes: > > 1) user owns graphics devices > 2) user sets mode with string (or similar) format using ioctl common to > all drivers. > 3) driver is locked to prevent multiple mode sets > 4) common code takes this string and does a hotplug event with it. > 5) hotplug event runs root context in user space > 6) mode is decoded and verified, this may involve a little process that > maintains the DDC database and reads a file of legal modes. Other > schemes are possible. > 7a) mode is set using VBIOS and vm86, signal driver mode is set > 7b) the register values needed to set the mode are passed into a root > priv ioctl. > 8) driver is unlocked.
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. 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 also involves dealing with all pending DRI clients too, that is they have to be notified that the fb/vmem layout is changing, the pending commands have to be completed, no more accepted, etc... until every DRI "client" acked the change... That sort of thing. Ben. ------------------------------------------------------- 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
