On Sat, 11 Sep 2004 14:05:54 -0400 (EDT), Vladimir Dergachev <[EMAIL PROTECTED]> wrote: > > All register writes would occur in the driver. There is nothing > > stopping the code that computes those register values from running in > > user space. > > > > A example mode setting IO would take: > > display buffer offset > > width, height, stride, etc - for fbcon to use > > register values to set the mode > > > > Mode setting needs to be serialized. It may be better to do the > > serialization before the hotplug event, in that case the mode setting > > IOCTL would be implicitly serialized and not need a separate lock. > > Just to clear up things - do you plan to retain the knowledge of last mode > set in the DRM driver ?
Yes, you have to do that for fbcon and suspend/restore to work. -- 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
