Hans Verkuil | 13 Mar 13:31 2011
Picon
Picon

[ANN] Agenda for the Warsaw meeting.

Agenda for V4L2 brainstorm meeting in Warsaw, March 16-18 2011.

Purpose of the meeting: to brainstorm about current V4L2 API limitations
with regards to required functionality. Ideally the results of the meeting
are actual solutions to these problems, but at the very least we should
have a concensus of what direction to take and who will continue working
on each problem. The hope is that this meeting will save us endless email
and irc discussions.

It is *not* a summit meeting, so any conclusions need to be discussed and
approved on the mailinglist.

The basic outline is the same as during previous meetings: the first day we
go through all the agenda points and make sure everyone understands the
problem. Smaller issues will be discussed and decided, more complex issues
are just discussed.

The second day we go in depth into the complex issues and try to come up with
ideas that might work. The last day we translate the all agenda items into
actions.

This approach worked well in the past and it ensures that we end up with
something concrete.

Those who have a vested interest in an agenda item should be prepared to
explain their take on it and if necessary have a presentation ready.

Besides the main agenda I also added a few items falling under the category
'if time permits'.

(Continue reading)

Jason Hecker | 14 Mar 05:10 2011
Picon

Re: [ANN] Agenda for the Warsaw meeting.

> B) Use of V4L2 as a frontend for SW/DSP codecs
>   (Laurent)

This would be good.   Realtek's RT2832U chip can tune to and possibly
demodulate DAB/DAB+ and FM along with the usual DVB-T.  Realtek does
support DAB and FM in Windows with this part but not in Linux and in
spite of promises from one of their developers I haven't seen anything
from them.  I think it'd be good to get this part talking to the DAB
processing routines in OpenDAB or OpenMoko as I strongly suspect the
part can tune to and provide a digital version of the bandband signal
for demodulation of DAB or FM in user space.

It might be a good opportunity to get a signal processing framework
into the driver but I suspect an API to allow a user space demodulator
to read ADC baseband data from such a device would be best and safest.
Hans Verkuil | 14 Mar 08:36 2011
Picon
Picon

Re: [ANN] Agenda for the Warsaw meeting.

On Monday, March 14, 2011 05:10:53 Jason Hecker wrote:
> > B) Use of V4L2 as a frontend for SW/DSP codecs
> >   (Laurent)
> 
> This would be good.   Realtek's RT2832U chip can tune to and possibly
> demodulate DAB/DAB+ and FM along with the usual DVB-T.  Realtek does
> support DAB and FM in Windows with this part but not in Linux and in
> spite of promises from one of their developers I haven't seen anything
> from them.

When you do, make sure they post it to linux-media! FM support is part of
the V4L API. We had support for a DAB device, but it turned out that:
1) the driver hadn't worked for ages and 2) the DAB API was never reviewed
or documented, 3) the hardware wasn't available anymore, so it was removed
recently.

I'd love to help create a proper DAB API.

Regards,

	Hans

> I think it'd be good to get this part talking to the DAB
> processing routines in OpenDAB or OpenMoko as I strongly suspect the
> part can tune to and provide a digital version of the bandband signal
> for demodulation of DAB or FM in user space.
> 
> It might be a good opportunity to get a signal processing framework
> into the driver but I suspect an API to allow a user space demodulator
> to read ADC baseband data from such a device would be best and safest.
(Continue reading)

Alex Deucher | 14 Mar 06:33 2011
Picon

Re: [ANN] Agenda for the Warsaw meeting.

On Sun, Mar 13, 2011 at 8:31 AM, Hans Verkuil <hverkuil <at> xs4all.nl> wrote:
> Agenda for V4L2 brainstorm meeting in Warsaw, March 16-18 2011.
>
> Purpose of the meeting: to brainstorm about current V4L2 API limitations
> with regards to required functionality. Ideally the results of the meeting
> are actual solutions to these problems, but at the very least we should
> have a concensus of what direction to take and who will continue working
> on each problem. The hope is that this meeting will save us endless email
> and irc discussions.
>
> It is *not* a summit meeting, so any conclusions need to be discussed and
> approved on the mailinglist.
>
> The basic outline is the same as during previous meetings: the first day we
> go through all the agenda points and make sure everyone understands the
> problem. Smaller issues will be discussed and decided, more complex issues
> are just discussed.
>
> The second day we go in depth into the complex issues and try to come up with
> ideas that might work. The last day we translate the all agenda items into
> actions.
>
> This approach worked well in the past and it ensures that we end up with
> something concrete.
>
> Those who have a vested interest in an agenda item should be prepared to
> explain their take on it and if necessary have a presentation ready.
>
> Besides the main agenda I also added a few items falling under the category
> 'if time permits'.
(Continue reading)

Hans Verkuil | 14 Mar 08:24 2011
Picon
Picon

Re: [ANN] Agenda for the Warsaw meeting.

On Monday, March 14, 2011 06:33:46 Alex Deucher wrote:
> On Sun, Mar 13, 2011 at 8:31 AM, Hans Verkuil <hverkuil <at> xs4all.nl> wrote:
> > Agenda for V4L2 brainstorm meeting in Warsaw, March 16-18 2011.
> >
> > Purpose of the meeting: to brainstorm about current V4L2 API limitations
> > with regards to required functionality. Ideally the results of the meeting
> > are actual solutions to these problems, but at the very least we should
> > have a concensus of what direction to take and who will continue working
> > on each problem. The hope is that this meeting will save us endless email
> > and irc discussions.
> >
> > It is *not* a summit meeting, so any conclusions need to be discussed and
> > approved on the mailinglist.
> >
> > The basic outline is the same as during previous meetings: the first day we
> > go through all the agenda points and make sure everyone understands the
> > problem. Smaller issues will be discussed and decided, more complex issues
> > are just discussed.
> >
> > The second day we go in depth into the complex issues and try to come up with
> > ideas that might work. The last day we translate the all agenda items into
> > actions.
> >
> > This approach worked well in the past and it ensures that we end up with
> > something concrete.
> >
> > Those who have a vested interest in an agenda item should be prepared to
> > explain their take on it and if necessary have a presentation ready.
> >
> > Besides the main agenda I also added a few items falling under the category
(Continue reading)


Gmane