linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: V4L2 'brainstorming' meeting in Warsaw, March 2011
Date: Tue, 01 Mar 2011 10:10:08 +0200	[thread overview]
Message-ID: <4D6CA9E0.5020508@maxwell.research.nokia.com> (raw)
In-Reply-To: <201102281912.01542.laurent.pinchart@ideasonboard.com>

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@vger.kernel.org/msg27956.html
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg26630.html
>>
>> 2) HDMI API support
>>
>> Some hotplug/CEC code can be found here:
>>
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg28549.html
>>
>> but Cisco will soon post RFCs on this topic as well.
>>
>> 3) Snapshot functionality.
>>
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg28192.html
>> http://www.mail-archive.com/linux-media@vger.kernel.org/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,

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

  reply	other threads:[~2011-03-01  8:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 17:11 V4L2 'brainstorming' meeting in Warsaw, March 2011 Marek Szyprowski
2011-02-28 18:03 ` Hans Verkuil
2011-02-28 18:12   ` Laurent Pinchart
2011-03-01  8:10     ` Sakari Ailus [this message]
2011-03-01  8:46       ` Tomasz Stanislawski
2011-03-05 16:02     ` Hans Verkuil
2011-03-05 21:02       ` Laurent Pinchart
2011-03-01 10:25 ` Hans Verkuil
     [not found] <AANLkTi=tOEikHi-c_0KYN8Sp9sguGB5Wd4dagvs72QFc@mail.gmail.com>
2011-03-10 11:38 ` Marek Szyprowski
  -- strict thread matches above, loose matches on Subject: below --
2011-02-28 16:54 Marek Szyprowski
2011-03-01 10:40 ` Marek Szyprowski
2011-03-01 15:26   ` Marek Szyprowski
     [not found]     ` <AANLkTim3=qq_NHzxOKEQzi21MPmhDdYvHNxpHDHr4O96@mail.gmail.com>
2011-03-04  9:18       ` Robert Fekete
2011-03-04  9:31     ` Jaeryul Oh
2011-03-08 11:00     ` Marek Szyprowski
2011-03-08 11:02     ` Marek Szyprowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D6CA9E0.5020508@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).