The udlfb (DisplayLink virtual USB) framebuffer driver currently supports 16bpp (RGB565) only. Looking at adding 24/32bpp support. Because it's a virtual device where the pixels get processed before sending over USB, any pixel encoding on the host side could work. Just have to choose the best one. Anyone know of any surprising pros/cons which would lead one of ARGB8888 or RGB888 being an obvious choice, all other things equal? Is either mode known to work better for xf86-video-fbdev or other client app compatibility? RBG888 has several advantages, of course. One interesting advantage of ARG8888 is udlfb has a mode where it's a defio client -- and larger bpp means page faults are actually somewhat more precise in identifying the damaged areas of the screen, in addition to natural alignment advantages. As background -- udlfb is in the kernel staging tree. And there is some future work at git.plugable.com. Thanks, Bernie http://plugable.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
