From: Albert H. <alb...@ya...> - 2008-01-02 23:22:14
|
Daniel Thompson writes: > I've been fiddling again looking at porting a few more frame buffer code > to operate with the 'cube not-RGB frame buffer. It struck me that > instead of lying about the visual reporting it with a fourcc code would > be quite useful for detecting and adapting to strange pixel formats (and > the resulting code could be ported to other weird hardware without > conditional compilation). > > The attached patch shows what I have in mind. > Hi Daniel, I can't see any advantage over the current solution in using a fourcc for the visual. It would help if applications were written to expect a fourcc code, but they aren't so you end up even in a worst situation. Maybe if the standard Linux kernel starts using a fourcc to specify a visual then we could use it in a useful way. On the other hand, one thing that I have in mind and could make linux applications directly useable using the cube's framebuffer is building a virtual rgb framebuffer at the kernel level using the "recently" merged deferred io framework. Cheers, Albert |