From: Issa Gorissen <flop.m@usa.net>
To: Andreas Oberritter <obi@linuxtv.org>
Cc: Martin Vidovic <xtronom@gmail.com>,
Ralph Metzler <rjkm@metzlerbros.de>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] Ngene cam device name
Date: Sun, 08 May 2011 12:30:06 +0200 [thread overview]
Message-ID: <4DC670AE.2070607@usa.net> (raw)
In-Reply-To: <4DC6682C.4060907@linuxtv.org>
On 08/05/11 11:53, Andreas Oberritter wrote:
> Hello Issa,
>
> On 05/06/2011 08:29 PM, Issa Gorissen wrote:
>> From: Andreas Oberritter <obi@linuxtv.org>
>>> On 05/06/2011 03:47 PM, Issa Gorissen wrote:
>>>> Also, it seems linux en50221 stack provides for the slot selection. So,
>> why
>>>> would you need two ca nodes ?
>>> Because it's the most obvious way to use it. And more importantly
>>> because the API sucks, if you have more than one device per node. You
>>> can have only one reader, one writer, one poll function per node. For
>>> example, you can't use one instance of mplayer to watch one channel with
>>> fe0+dmx0+ca0 and a second instance of mplayer to watch or record another
>>> channel with fe1+dmx1+ca0. You won't know which device has an event if
>>> you use poll. The API even allows mixing multiple CI slots and built-in
>>> descramblers in the same node. But try calling CA_RESET on a specific
>>> slot or on a descrambler. It won't work. It's broken by design.
>>
>> You need to write a userspace soft which will handle the concurrent access of
>> your ca device...
> ... to gain what exactly over using two distinct nodes?
>
> How do you propose solving the problem with CA_RESET with a userspace soft?
Well, solving your problem of having two mplayer instances!
The CA_RESET ioctl will not reset one slot at a time obviously. But you
can do an interface reset via the control register, no ? In cases when
you remove/add a second/third/... module from one of the slot of a CI
device, then I guess the CA_RESET is broken because it will reset
everything... Have you got patches for that ?
>> But for your given example, is there any card allowing you to do that (one ci
>> slot, two tuners) ?
> You don't seem to have understood my example. I was explaining some
> drawbacks of having more than one CI slot, but only one node, answering
> your prior question.
>
> Besides that, it's highly probable that such a card exists. It wouldn't
> make much sense to hardwire CI slots to tuners, if multiple tuners exist
> on a board.
>
> Disregarding the term "cards", there are variants of the Dreambox with
> 1, 2 or 4 CI slots combined with 1 to 4 tuners.
>
> Regards,
> Andreas
I guess your point is valid, maybe the improvement you would like to see
will pop up when the need will be created...
next prev parent reply other threads:[~2011-05-08 10:30 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 18:29 [PATCH] Ngene cam device name Issa Gorissen
2011-05-08 9:53 ` Andreas Oberritter
2011-05-08 10:30 ` Issa Gorissen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-06 13:47 Issa Gorissen
2011-05-06 16:07 ` Andreas Oberritter
2011-05-04 14:51 Issa Gorissen
2011-05-04 14:05 Issa Gorissen
2011-05-04 14:27 ` Andreas Oberritter
2011-05-04 11:09 Issa Gorissen
2011-05-04 11:07 Issa Gorissen
2011-05-04 13:51 ` Andreas Oberritter
2011-05-04 8:27 Issa Gorissen
2011-05-04 9:59 ` Andreas Oberritter
2011-05-04 11:20 ` Ralph Metzler
2011-05-04 12:30 ` Andreas Oberritter
2011-05-04 13:15 ` Ralph Metzler
2011-05-04 13:35 ` Martin Vidovic
2011-05-04 14:46 ` Andreas Oberritter
2011-05-05 14:43 ` Martin Vidovic
2011-05-06 12:17 ` Andreas Oberritter
2011-05-06 13:43 ` Walter Van Eetvelt
2011-05-08 10:05 ` Martin Vidovic
2011-05-08 17:58 ` Andreas Oberritter
2011-05-08 23:55 ` Martin Vidovic
2011-05-09 11:44 ` Andreas Oberritter
2011-04-24 11:38 Issa Gorissen
2011-05-03 23:11 ` Mauro Carvalho Chehab
2011-05-04 7:24 ` Andreas Oberritter
2011-03-12 15:39 Issa Gorissen
2011-03-12 14:34 Issa Gorissen
2011-03-12 14:58 ` Andreas Oberritter
2011-03-28 0:44 ` Ralph Metzler
2011-03-28 21:40 ` Mauro Carvalho Chehab
2011-04-24 9:31 ` Issa Gorissen
2011-03-28 22:57 ` Oliver Endriss
2011-04-05 21:50 ` Issa Gorissen
2011-03-12 14:10 Issa Gorissen
2011-03-12 14:48 ` Andreas Oberritter
2011-03-12 14:57 ` Martin Vidovic
2011-03-12 15:06 ` Andreas Oberritter
2011-03-11 18:33 Issa Gorissen
2011-03-11 20:39 ` Andreas Oberritter
2011-03-11 21:46 ` Ralph Metzler
2011-03-12 13:25 ` Andreas Oberritter
2011-03-12 13:55 ` Ralph Metzler
2011-03-10 15:29 Issa Gorissen
2011-03-11 15:52 ` Andreas Oberritter
2011-03-11 21:44 ` Martin Vidovic
2011-03-12 13:29 ` Andreas Oberritter
2011-03-12 14:05 ` Ralph Metzler
2011-03-12 14:38 ` Andreas Oberritter
2011-03-12 15:06 ` Ralph Metzler
2011-03-12 23:42 ` Oliver Endriss
2011-03-13 10:47 ` Martin Vidovic
2011-03-16 22:07 ` Issa Gorissen
2011-03-18 20:20 ` Martin Vidovic
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=4DC670AE.2070607@usa.net \
--to=flop.m@usa.net \
--cc=linux-media@vger.kernel.org \
--cc=obi@linuxtv.org \
--cc=rjkm@metzlerbros.de \
--cc=xtronom@gmail.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