From: Steve Kerrison <steve@stevekerrison.com>
To: "Rémi Denis-Courmont" <remi@remlab.net>
Cc: linux-media@vger.kernel.org, vlc-devel@videolan.org
Subject: Re: dvb: one demux per tuner or one demux per demod?
Date: Tue, 24 May 2011 13:05:34 +0100 [thread overview]
Message-ID: <1306238734.7397.102.camel@ares> (raw)
In-Reply-To: <719f9c4d1bd57d5b2711bc24a9d5c3b1@chewa.net>
Hi Rémi,
The cxd2820r supports DVB-T/T2 and also DVB-C. As such antti coded up a
multiple front end (MFE) implementation for em28xx then attaches the
cxd2820r in both modes.
I believe you can only use one frontend at once per adapter (this is
certainly enforced in the cxd2820r module), so I don't see how it would
cause a problem for mappings. I think a dual tuner device would register
itself as two adapters, wouldn't it?
But I'm new at this, so forgive me if I've overlooked something or
misunderstood the issue you've raised.
Regards,
--
Steve Kerrison MEng Hons.
http://www.stevekerrison.com/
On Tue, 2011-05-24 at 12:55 +0200, Rémi Denis-Courmont wrote:
> Hello,
>
> Been testing the bleeding-edge Hauppauge 290E (em28174 + Sony cxd2820r)
> from Antti Palosaari and Steve Kerrison, now in linux-media GIT tree.
>
> It seems the device creates two frontends and only one demux/dvr nodes.
> Are they not supposed to be one demux per frontend? Or how is user-space
> supposed to map the demux/dvr and the frontend, on a multi-proto card? on a
> multi-tuner card?
>
> Best regards,
>
next prev parent reply other threads:[~2011-05-24 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 10:55 dvb: one demux per tuner or one demux per demod? Rémi Denis-Courmont
2011-05-24 12:05 ` Steve Kerrison [this message]
2011-05-24 12:28 ` Devin Heitmueller
2011-05-24 12:45 ` Steve Kerrison
2011-05-24 13:00 ` Antti Palosaari
2011-05-25 14:51 ` Rémi Denis-Courmont
2011-05-24 15:59 ` Rémi Denis-Courmont
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=1306238734.7397.102.camel@ares \
--to=steve@stevekerrison.com \
--cc=linux-media@vger.kernel.org \
--cc=remi@remlab.net \
--cc=vlc-devel@videolan.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.