All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel <eallaud@gmail.com>
To: unlisted-recipients:; (no To-header on input)@bombadil.infradead.org
Cc: linux-media@vger.kernel.org
Subject: Re: How to handle independent CA devices
Date: Tue, 14 Sep 2010 23:13:43 -0400	[thread overview]
Message-ID: <4C9039E7.3040809@gmail.com> (raw)
In-Reply-To: <19600.3015.410234.367070@valen.metzler>

rjkm a écrit :
> Hi Johannes,
>
>
> Johannes Stezenbach writes:
>  > > So, I would like to hear your opinions about how to handle such CA devices 
>  > > regarding device names/types, the DVB API and user libraries.
>  > 
>  > it looks like there isn't much interest from DVB developers
>  > in that topic...  I'll try...
>  > 
>  > 
>  > IMHO there are three sub topics:
>  > 
>  > 1. be compatible with existing applications
>  >    (I guess this means: feed stream from frontend through CI transparently)
>  > 2. create an API which would also work for CI-only
>  >    devices like this Hauppauge WinTV-CI USB thingy
>  > 3. how to switch between these modes?
>  > 
>  > This sec0 device is history (unused and deprecated for years), right?
>
> Yes, the former DiSEqC, etc. device. I only use it because it is is
> unused and I do not have to change anything in dvb-core this way.
> But trivial to change it or add ci0.
>
>
>  > How about the following:
>  > Rename it to ci0.  When ci0 is closed the stream is routed
>  > transparently from frontend through CI, if it's opened one needs to
>  > read/write the stream from userspace.
>
>
> You still need a mechanism to decide which tuner gets it. First one
> which opens its own ca device?
> Sharing the CI (multi-stream decoding) in such an automatic way 
> would also be complicated.
> I think I will only add such a feature if there is very high demand
> and rather look into the separate API solution.
>
>
>  > If you can't get responses here I guess you could talk to
>  > vdr or other application developers.  After all they'll have
>  > to use the API.
>
> I am in contact with some.
> Just wanted to check what people think about it on this list.
>
> Thanks for your comments.
>
>   
You might also want to check on mythtv-dev list, there was a guy (James 
Courtier-Dutton) who wanted to hack exactly this in mythtv. I guess he 
would have the user space point-of-view.
Hope you succeed, because having an independant CI would be perfect to 
enable real multirec for DVB cards by decoding after the fact.
Bye
Manu

  reply	other threads:[~2010-09-15  3:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 21:52 How to handle independent CA devices rjkm
2010-09-14 14:43 ` Johannes Stezenbach
2010-09-14 23:56   ` rjkm
2010-09-15  3:13     ` Emmanuel [this message]
2010-09-15  4:05     ` Manu Abraham
2010-09-18  0:47       ` rjkm
2010-09-18 11:27         ` James Courtier-Dutton
2010-09-18 12:23         ` Manu Abraham
2010-09-19  1:20           ` Oliver Endriss
2010-09-16 20:43 ` [linux-media] " Klaus Schmidinger
2010-09-18  1:02   ` rjkm
2017-06-29 20:10   ` Jasmin J.

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=4C9039E7.3040809@gmail.com \
    --to=eallaud@gmail.com \
    --cc=linux-media@vger.kernel.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.