All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 28 Jun 2010 21:48:56 +0200	[thread overview]
Message-ID: <4C28FCA8.5090005@hoogenraad.net> (raw)
In-Reply-To: <AANLkTikojhopHeY2WuHxK_tbCs99_SV7ksWnYv4UXM4W@mail.gmail.com>

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.
Conceptronic just packages sticks from other vendors.
The fact that the device ID is recognized point towards the afatech
driver, and not the Realtek RTL2831U driver.

Fot background on the Realtek RTL2831U driver, see:

http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U

matteo sisti sette wrote:
> Hi,
> 
> I hope this is the right place for reporting this; if not, please
> forgive and redirect me.
> 
> My DVB-T USB stick, a "Conceptronic USB 2.0 Digital TV Receiver"
> CTVDIGUSB2 doesn't work after succesfully compiling and installing
> v4l-dvb, and it seems it is not supported according to the device
> list.
> 
> The ID is 1b80:d393
> 
> The name "Conceptronic USB 2.0" is very similar to that of CTVDIGRCU,
> which _is_ supported and the chipset seems to be indeed an Afatech as
> the output of lsusb reports:
> Bus 002 Device 007: ID 1b80:d393 Afatech
> (or isn't that reliable?)
> 
> So I wonder whether this is one of the cases where the following applies:
> "The driver has to be aware that it's related to some hardware
> (typically through the subsystem ID from the USB ID or PCI ID). If the
> driver doesn't recognize/bind to your particular hardware, then the
> module will probably load but then proceed to not do anything. In
> other words, support for your device would have to be added to the
> driver."
> 
> If I understand correctly (pleas correct me if I am wrong), IF that is
> the case (which may be not), then making it work should be just a
> matter of adding the id of the device to the source code of the driver
> somewhere and recompiling it and it would work??
> 
> If so, is it something I may try following some step-by-step guide?
> 
> Thanks
> m.
> 


-- 
Jan Hoogenraad



  reply	other threads:[~2010-06-28 19:50 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 [this message]
2010-06-28 20:05   ` Matteo Sisti Sette
2010-06-29  5:54     ` Jan Hoogenraad
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=4C28FCA8.5090005@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 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.