From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Matteo Sisti Sette <matteosistisette@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?
Date: Tue, 29 Jun 2010 07:54:53 +0200 [thread overview]
Message-ID: <4C298AAD.2090701@hoogenraad.net> (raw)
In-Reply-To: <4C290096.5080209@gmail.com>
I see: apparently the versions earlier than V3.0 of CTVDIGRCU used
Realtek RTL2831U. I'll make a note of that on the wiki page.
Matteo Sisti Sette wrote:
> On 06/28/2010 09:48 PM, Jan Hoogenraad wrote:
>> Matteo:
>>
>> If I read this well, CTVDIGUSB2 1b80:d393 (Afatech) is not at all
>> similar to the CTVDIGRCU.
>> The CTVDIGRCU has a Realtek RTL2831U decoder, and is NOT included in the
>> standard dvb list.
>
> So is the table at http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices
> incorrect?
>
> It says:
>
> Conceptronic USB2.0 DVB-T CTVDIGRCU V3.0
> ✔ Yes, in kernel since 2.6.31
> 1b80:e397 USB2.0
> Afatech AF9015
>
>
> Anyway, I see there are other sticks with chipsets by Afatech. Is there
> any chance that some of the currently implemented driver would work fine
> with my chipset if only I forced the driver to recognize the chipset as
> another one by touching the source code?
> How could I try that? (if it deserves a try)
>
> Thanks
> m.
>
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
next prev parent reply other threads:[~2010-06-29 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 20:07 v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0? matteo sisti sette
2010-06-28 19:48 ` Jan Hoogenraad
2010-06-28 20:05 ` Matteo Sisti Sette
2010-06-29 5:54 ` Jan Hoogenraad [this message]
2010-06-29 6:28 ` Matteo Sisti Sette
[not found] ` <AANLkTik6dQw_yw28L3CajIZYdLLGHkfddrDQq4BuSDAI@mail.gmail.com>
2010-06-29 10:06 ` Fwd: " Pedro Côrte-Real
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=4C298AAD.2090701@hoogenraad.net \
--to=jan-conceptronic@hoogenraad.net \
--cc=linux-media@vger.kernel.org \
--cc=matteosistisette@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