From: Antonino D. <ad...@po...> - 2003-04-01 01:31:41
|
On Tue, 2003-04-01 at 08:27, Kendall Bennett wrote: > Jon Smirl <jon...@ya...> wrote: > > > I didn't read through the code yet, is this being implemented by > > adding some new IOCTLs to the fb interface? For example an IOCTL to > > get the legal modes or to reset the card. > > We definitely want some new IOCTL's to allow the apps to find out what > modes are available, if this has not been added. Actually, the fbdev has its own ioctl, FBIOSETVAR (or something like that). You place the desired mode in struct fb_var_screeninfo (var), then set var->activate = FB_ACTIVATE_TEST. If there's no error, the var should now contain the best mode (not necessarily the same) which was requested. All this is automatically incorporated to vesafb when vm86d is loaded. The new vesafb driver has additional methods for: fb_check_var() fb_set_par() fb_pan_display() fb_setcolreg() fb_blank() -- currently a dummy method Tony |