Hi, On Mon, 2010-12-13 at 15:26 -0500, ext Chethan Pandarinath wrote: > Hi Tomi, > > > I sent the below email to the angstrom linux development listserv. > Based on the Maintainers list from git.kernel.org, you seem like the > right person to contact about this. Would you be able to discuss this > with me? > > > Thanks. > Chethan > > ---------- Forwarded message ---------- > From: Chethan Pandarinath <[email protected]> > Date: Mon, Dec 13, 2010 at 2:34 PM > Subject: possible errors in linux omap display headers - who would be > a good person to contact? > To: angstrom-distro-devel <[email protected]> > > > Hi everybody, this may not be the right place to ask this question, > but I don't really know who to address it to, so maybe someone here > can point me in the right direction. > > > I have been working on setting up a video framebuffer and writing to > it on an OMAP 3530 device (TI beagleboard). It appears that the > definitions in drivers/video/omap/omapfb.h are incorrect (possibly out > of date?), which caused a lot of confusion while trying to set up my > framebuffer. > > > Specifically, I'm trying to set the properties of my framebuffer, > using the ioctl command, FBIOPUT_VSCREENINFO, and a fb_var_screeninfo > struct. > > > The fb_var_screeninfo struct has a parameter nonstd that sets the > color properties of the buffer (e.g. RGB 565, RGB 24U, YUV 422, etc). > > > The acceptable values for nonstd are defined in the omapfb.h file, but > they appear to be incorrect - at least they don't seem to set the > parameters of the buffer the way one would expect. For example, > using OMAPFB_COLOR_RGB565 appears to give me a buffer with parameters > that look like OMAPFB_COLOR_RGB24U.
nonstd field is only used for OMAPFB_COLOR_YUV422 and OMAPFB_COLOR_YUY422. For other modes leave it to zero. If you want to use YUV modes, set the nonstd to the yuv mode, and bits_per_pixel to 16. For other modes, set bits_per_pixel and red/green/blue/transp fields. You can look at drivers/video/omap2/omapfb/omapfb-main.c omapfb_colormodes[] array for examples how the driver parses the modes. Tomi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
