Robert Schwebel wrote:
A second step could be:
- Have this initial framebuffer as /dev/fb0 (mem at the end of RAM)
- In order to avoid flicker, the driver sets up a 2nd framebuffer,
in dynamically allocated memory -> /dev/fb1. This framebuffer
continues to display the splash image (or an animation). Switching
from fb0 -> fb1 is done during VSync.
What about double-buffering fb0 instead? That's how Android works.
Drivers which see the framebuffer= parameter would have to skip their
hardware initialisation step.
Actually, I'd rather that drivers look at the hardware itself, and
verify that the configuration matches what the parameter specifies
before making changes. That way you could use framebuffer= to
communicate the desired setup to the driver in cases where the hardware
wasn't already initialized.
--
Bill Gatliff
b...@billgatliff.com
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
