From: Antti Palosaari <crope@iki.fi>
To: Bert Haverkamp <bert@bertenselena.net>
Cc: linux-media@vger.kernel.org
Subject: Re: usb dvb-c tuner status
Date: Sat, 19 Sep 2009 13:51:08 +0300 [thread overview]
Message-ID: <4AB4B79C.7000802@iki.fi> (raw)
In-Reply-To: <1e68a10b0909182348v2026a57dsc877a8c5c1e9289f@mail.gmail.com>
On 09/19/2009 09:48 AM, Bert Haverkamp wrote:
> Hello all,
>
> A while back I asked about supported USB dvb-c devices.
> Meanwhile my search continued and I have extended my list of available devices.
> Unfortunately, none of them currently are supported by linux.
>
> Does anyone have viable solution for me?
>
> - Technotrend CT 1200 which is an old device, hard to get.
> - Technotrend CT-3650 for which there is one report that dvb-c works
> with a patch,(is this already in-tree?), but dvb-t and CI not
> - Sundtek MediaTV Pro for which a closed source driver exists. I
> don't want to go that way.
> Terratec Cinergy Hybrid H5 which seems to be troubled with a driver
> for a drx-k or drx-j chip.
> - Pinnacle 340e, depends on the xc4000 chip, under development by Devin.
> - Hauppauge WinTV HVR-930C, also drx-j based as far as I can see
Anysee E30C Plus
Anysee E30 Combo (DVB-T/DVB-C)
Reddo DVB-C USB BOx (I just added, goes to 2.6.32)
All those are using Philips TDA10023 demod, which seems to be almost
only solution currently for open Linux DVB-C. Anysee contains also
smartcard reader which is not supported (it is not CAM, just reader).
Unfortunately market situation for those devices is currently few EU
countries or Finland only.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2009-09-19 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 12:15 usb dvb-c tuner status Bert Haverkamp
2009-08-15 19:54 ` Chris Thornley
2009-08-17 13:00 ` Bert Haverkamp
2009-09-19 6:48 ` Bert Haverkamp
2009-09-19 10:51 ` Antti Palosaari [this message]
2009-09-20 12:55 ` Bert Haverkamp
2009-09-20 13:30 ` 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=4AB4B79C.7000802@iki.fi \
--to=crope@iki.fi \
--cc=bert@bertenselena.net \
--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.