linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media <linux-media@vger.kernel.org>, htl10@users.sourceforge.net
Subject: Re: DVB core enhancements - comments please?
Date: Fri, 29 Jun 2012 15:55:04 +0300	[thread overview]
Message-ID: <4FEDA5A8.5030704@iki.fi> (raw)
In-Reply-To: <4FED9972.9090105@redhat.com>

On 06/29/2012 03:02 PM, Mauro Carvalho Chehab wrote:
> Em 29-06-2012 02:03, Antti Palosaari escreveu:
>> On 06/29/2012 07:32 AM, Mauro Carvalho Chehab wrote:
>>> Em 27-06-2012 21:33, Antti Palosaari escreveu:
>>>> SDR - Softaware Defined Radio support DVB API
>>>> --------------------------------------------------
>>>> * http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/44461
>>>> * there is existing devices that are SDR (RTL2832U "rtl-sdr")
>>>> * SDR is quite near what is digital TV streaming
>>>> * study what is needed
>>>> * new delivery system for frontend API called SDR?
>>>> * some core changes needed, like status (is locked etc)
>>>> * how about demuxer?
>>>> * stream conversion, inside Kernel?
>>>> * what are new parameters needed for DVB API?
>>>
>>> Let's not mix APIs: the radio control should use the V4L2 API, as this is not
>>> DVB. The V4L2 API has already everything needed for radio. The only missing
>>> part ther is the audio stream. However, there are a few drivers that provide
>>> audio via the radio device node, using read()/poll() syscalls, like pvrusb.
>>> On this specific driver, audio comes through a MPEG stream. As SDR provides
>>> audio on a different format, it could make sense to use VIDIOC_S_STD/VIDIOC_G_STD
>>> to set/retrieve the type of audio stream, for SDR, but maybe it better to just
>>> add capabilities flag at VIDIOC_QUERYCTL or VIDIOC_G_TUNER to indicate that
>>> the audio will come though the radio node and if the format is MPEG or SDR.
>>
>> SDR is not a radio in mean of V4L2 analog audio radios.
>
> Why not? There's nothing at V4L2 API that limits it to analog, otherwise it couldn't
> be used by digital cameras.
>
>> SDR can receive all kind of signals, analog audio, analog television, digital radio,
>> digital television, cellular phones, etc. You can even receive DVB-T, but hardware I
>> have is not capable to receive such wide stream.
>
> The V4L2 API has everything to control receivers. What it doesn't have (and it doesn't make
> sense to have, as such thing would just duplicate existing features at DVB API)
> are the per delivery-system specific demodulator properties and PID filtering.
>
>> That chip supports natively DVB-T TS but change be switched to SDR mode. Is it even possible
>> to switch from DVB API (DVB-T delivery system) to V4L2 API at runtime?
>
> Yes. There are lots of drivers that do that. There are even a few that allow to control the
> frontend and demod via DVB API and to receive streams via V4L2 mmap or read API.

Could you give closest example?
In that case I have RTL2832 DVB-T frontend which I want to change SDR 
mode. What are the those existing DVB frontend drivers look example.

regards
Antti


-- 
http://palosaari.fi/



  reply	other threads:[~2012-06-29 12:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  0:33 DVB core enhancements - comments please? Antti Palosaari
2012-06-29  4:32 ` Mauro Carvalho Chehab
2012-06-29  5:03   ` Antti Palosaari
2012-06-29 11:24     ` Patrick Boettcher
2012-06-29 13:07       ` Antti Palosaari
2012-06-29 14:21       ` Patrick Boettcher
2012-06-29 14:28       ` Mauro Carvalho Chehab
2012-07-02 21:27         ` Antti Palosaari
2012-07-03 16:25           ` Mauro Carvalho Chehab
2012-07-03 16:50             ` Hin-Tak Leung
2012-07-03 19:54             ` Mauro Carvalho Chehab
2012-06-29 12:02     ` Mauro Carvalho Chehab
2012-06-29 12:55       ` Antti Palosaari [this message]
2012-06-30  9:44 ` Marko Ristola
2012-07-01 11:11   ` Antti Palosaari
2012-07-03 17:21     ` Marko Ristola
2012-07-21 16:36       ` Antti Palosaari
2012-07-25 10:38         ` Antti Palosaari

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=4FEDA5A8.5030704@iki.fi \
    --to=crope@iki.fi \
    --cc=htl10@users.sourceforge.net \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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).