Hi Thomas, On Friday 02 September 2011 11:18:53 Thomas Petazzoni wrote: > Le Fri, 2 Sep 2011 17:08:32 +0800, "Wu, Josh" a écrit : > > My understanding is that you want to use Atmel ISI to output RGB data > > then work with framebuffer. So yes, it is possible. > > Good. > > > Since current atmel_isi.c only uses its codec path to output YUV > > data. So first need add RGB format support in > > isi_camera_get_formats(). Then you have two choices to enable RGB > > output of ISI: 1. Enable isi's preview path(DMA, interrupts) to > > convert YUV to RGB. 2. Or still use codec path but don't need add > > much ISI code, just set camera sensor(if it support RGB565 output) to > > output RGB565 data for ISI, then what the data ISI output now should > > be RGB565 format. But in this way you cannot do any scale. > > Doing the YUV -> RGB within the V4L2 driver is something I understand > quite well. The part I miss is how the V4L2 driver interacts with the > framebuffer driver to output the camera image into the framebuffer. > > > For V4L2_CAP_VIDEO_OVERLAY type driver, I don't know much about that. > > Hum, ok, found http://v4l2spec.bytesex.org/spec/x6570.htm which seems > to explain a bit the userspace interface for this. I'm not sure if V4L2_CAP_VIDEO_OVERLAY is a good solution for this. This driver type (or rather buffer type) was used on old systems to capture directly to the PCI graphics card memory. Nowadays I would advice using USERPTR with framebuffer memory. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
