Hi, I am encountering a problem during the initialization of DirectFB. I am writing a driver for a device that uses more than one pixel formats, and the problem is that DirectFB won't issue a set_par on the kernel driver unless it detects different current and target resolutions. I have temporarily resolved the problem by redirecting control to the 'else' block in systems/fbdev/fbdev.c:1367. Am I missing the right way to trigger a mode change, or is this DirectFB's unintended behavior?
With regards, nccc -- View this message in context: http://old.nabble.com/No-proper-mode-change-during-initialization-tp27174430p27174430.html Sent from the DirectFB Dev mailing list archive at Nabble.com. _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
