Doesn't the base platform need to be designed to also treat individual heads as resources?
fbdev only sets the mode on a single head. My cards have more that one head. When I tried adding mode setting to DRM so that I could handle my other heads there was a big uproar that fbdev owns mode setting and that code shouldn't be duplicated. Making fbdev support more than one head means that it's API has to be redesigned. DRM doesn't have a mode API so one can be designed from scratch. In a two head system with simultaneous users, one using fbdev console and the other playing a 3D game, how is this locking thing going to work on a process swap basis? Even though we don't have the code for this today the architecture needs to be designed for it. The reason you can't do this today is because the kernel level drivers won't allow it, you can do this currently from the X server. Heads need to stay in an "unassigned state" until someone logs in on them. This allows a head to issue a request for "merged fb" mode and take over the other head. This may require some creativity for drawing the log in prompts. Don't forget about SAK and drawing prompts that can't be spoofed. -- 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. 13. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
