On Saturday 14 February 2009 01:42:31 Trent Piepho wrote:
On Fri, 13 Feb 2009, Hans Verkuil wrote:
On Friday 13 February 2009 22:15:45 Mauro Carvalho Chehab wrote:
On Fri, 13 Feb 2009 09:55:19 +0100
The V4L API defines its RDS API as follows.
From radio devices supporting it,
RFC: Completing the V4L2 RDS API
Introduction
There are several drivers that implement RDS support: bttv (through
saa6588), radio-si470x and radio-cadet. radio-tea5764 wants to support this
in the future as well.
The saa6588 is used in different
On Fri, 13 Feb 2009 09:55:19 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
RFC: Completing the V4L2 RDS API
Introduction
There are several drivers that implement RDS support: bttv (through
saa6588), radio-si470x and radio-cadet.
On Friday 13 February 2009 22:15:45 Mauro Carvalho Chehab wrote:
On Fri, 13 Feb 2009 09:55:19 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
RFC: Completing the V4L2 RDS API
Introduction
There are several drivers that implement RDS
On Fri, 13 Feb 2009 22:59:07 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
Or perhaps we should add a field that reports the maximum number of
buffered packets? E.g. __u16 rds_buf_size. This might be more generic
and you can even allow this to be set with VIDIOC_S_TUNER (although
On Fri, 13 Feb 2009, Hans Verkuil wrote:
On Friday 13 February 2009 22:15:45 Mauro Carvalho Chehab wrote:
On Fri, 13 Feb 2009 09:55:19 +0100
The V4L API defines its RDS API as follows.
From radio devices supporting it, RDS data can be read with the read()
function. The data is