Sakari Ailus wrote:
Laurent Pinchart wrote:
On Monday 28 February 2011 19:03:39 Hans Verkuil wrote:
On Monday, February 28, 2011 18:11:47 Marek Szyprowski wrote:
[snip]
4. Agenda
TBD, everyone is welcomed to put his items here :)
In no particular order:
1) pipeline configuration, cropping and scaling:
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg27956.html
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg26630.html
2) HDMI API support
Some hotplug/CEC code can be found here:
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg28549.html
but Cisco will soon post RFCs on this topic as well.
3) Snapshot functionality.
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg28192.html
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg28490.html
If we finish quicker than expected, then we can also look at this:
- use of V4L2 as a frontend for SW/DSP codecs
In still no particular order:
- Muxed formats (H.264 inside MJPEG)
- H.264
- Buffers pool
- Entity information ioctl
- Userspace drivers (OMX)
- Sensor blanking/pixel-clock/frame-rate settings (including
enumeration/discovery)
- GL/ES in V4L2 devices
Unordered, again:
- Multiple video buffer queues per device (currently implemented in the
OMAP 3 ISP driver in non-standard way).
- Synchronising parameters (e.g. exposure time and gain) on given
frames. Some sensors support this on hardware. There are many use cases
which benefit from this, for example this one:
<URL:http://fcam.garage.maemo.org/>
- Flash synchronisation (might fall under the above topic).
- Frame metadata. It is important for the control algorithms (exposure,
white balance, for example), to know which sensor settings have been
used to expose a given frame. Many sensors do support this. Do we want
to parse this in the kernel or does it belong to user space? The
metadata formats are mostly sensor dependent.
The dates are okay for me but I'm not yet certain of my participation
for other reasons.
Best regards,
I propose few topic:
1. Acquiring subdevs from other devices using subdev pool
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg21831.html
2. Buffer cropping.
http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg27956.html
3. Introducing subdev hierarchy. Below there is a link to driver using it:
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/28885/focus=28890
Best regards
Tomasz Stanislawski
--
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
