On 07/03/2013 09:34 PM, Laurent Pinchart wrote:
On Wednesday 03 July 2013 02:01:59 Sakari Ailus wrote:
On Mon, Jun 24, 2013 at 03:40:14PM +0200, Hans Verkuil wrote:
...
Since the payloads are larger I am less concerned about speed. There is
one problem, though: if you dequeue the event and the
On Wednesday 03 July 2013 02:01:59 Sakari Ailus wrote:
> On Mon, Jun 24, 2013 at 03:40:14PM +0200, Hans Verkuil wrote:
> ...
>
> > Since the payloads are larger I am less concerned about speed. There is
> > one problem, though: if you dequeue the event and the buffer that should
> > receive the pa
On Mon, Jun 24, 2013 at 03:40:14PM +0200, Hans Verkuil wrote:
...
> Since the payloads are larger I am less concerned about speed. There is one
> problem, though: if you dequeue the event and the buffer that should receive
> the payload is too small, then you have lost that payload. You can't alloc
Hi Hans,
On Mon, Jun 24, 2013 at 03:40:14PM +0200, Hans Verkuil wrote:
...
> > Events that fit to regular 64 bytes will be delivered using that, and the
> > user-provided pointer will only be used in the case a large event is
> > delivered to the user. So in order to be able to receive large event
Hi all,
On 06/24/2013 02:57 PM, Hans Verkuil wrote:
On Sun June 23 2013 00:46:57 Sakari Ailus wrote:
On Wed, Jun 19, 2013 at 08:32:35AM +0200, Hans Verkuil wrote:
On Tue June 18 2013 23:22:33 Laurent Pinchart wrote:
On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
On Mon, May 13, 2013 at
On Sat June 22 2013 22:58:01 Sakari Ailus wrote:
> Hi Laurent,
>
> On Tue, Jun 18, 2013 at 11:22:33PM +0200, Laurent Pinchart wrote:
> > On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
> > > On Mon, May 13, 2013 at 02:14:43PM +0200, Hans Verkuil wrote:
> > > > Currently the event API allows fo
On Sun June 23 2013 00:46:57 Sakari Ailus wrote:
> Hi Hans,
>
> On Wed, Jun 19, 2013 at 08:32:35AM +0200, Hans Verkuil wrote:
> > On Tue June 18 2013 23:22:33 Laurent Pinchart wrote:
> > > Hi Hans and Sakari,
> > >
> > > On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
> > > > Hi Hans,
> > > >
Hi Hans,
On Wed, Jun 19, 2013 at 08:32:35AM +0200, Hans Verkuil wrote:
> On Tue June 18 2013 23:22:33 Laurent Pinchart wrote:
> > Hi Hans and Sakari,
> >
> > On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
> > > Hi Hans,
> > >
> > > Thanks for the RFC! :-)
> > >
> > > On Mon, May 13, 2013 a
Hi Laurent,
On Tue, Jun 18, 2013 at 11:22:33PM +0200, Laurent Pinchart wrote:
> On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
> > On Mon, May 13, 2013 at 02:14:43PM +0200, Hans Verkuil wrote:
> > > Currently the event API allows for a payload of up to 64 bytes. Sometimes
> > > we would like
On Tue June 18 2013 23:22:33 Laurent Pinchart wrote:
> Hi Hans and Sakari,
>
> On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
> > Hi Hans,
> >
> > Thanks for the RFC! :-)
> >
> > On Mon, May 13, 2013 at 02:14:43PM +0200, Hans Verkuil wrote:
> > > Currently the event API allows for a payload
Hi Hans and Sakari,
On Friday 07 June 2013 00:38:04 Sakari Ailus wrote:
> Hi Hans,
>
> Thanks for the RFC! :-)
>
> On Mon, May 13, 2013 at 02:14:43PM +0200, Hans Verkuil wrote:
> > Currently the event API allows for a payload of up to 64 bytes. Sometimes
> > we would like to pass larger payloads
Hi Hans,
Thanks for the RFC! :-)
On Mon, May 13, 2013 at 02:14:43PM +0200, Hans Verkuil wrote:
> Currently the event API allows for a payload of up to 64 bytes. Sometimes we
> would like to pass larger payloads to userspace such as metadata associated
> with a particular video stream.
>
> A typi
Currently the event API allows for a payload of up to 64 bytes. Sometimes we
would like to pass larger payloads to userspace such as metadata associated
with a particular video stream.
A typical example of that would be object detection events.
This RFC describes one approach for doing this.
The
13 matches
Mail list logo
