From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Alexjan Carraturo <axjslack@gmail.com>
Cc: CityK <cityk@rogers.com>,
video4linux-list@redhat.com,
Linux-media <linux-media@vger.kernel.org>
Subject: Re: Pinnacle PCTV DVB-T 70e
Date: Tue, 18 May 2010 15:10:35 -0300 [thread overview]
Message-ID: <4BF2D81B.5050804@redhat.com> (raw)
In-Reply-To: <AANLkTilJ24ok_LzX_m3QvXz8tio0DIfarYp5Dj0hUc5o@mail.gmail.com>
Alexjan Carraturo wrote:
> Why not? Because nobody can cure this entry? Or why the driver is not
> compatible with the version in the kernel now?
For someone to add support to a device, it needs to have that device (or
a similar one), and to be able to get access to the datasheets or to use
some reverse engineering technique. One important information is what
are the chips inside the device.
>> You can, however, look to see if you can add support for your device to
>> the existing v4l-dvb kernel driver. There are several developers that
>> are knowledgeable of the em28xx driver, and whom may be able to help you
>> in that regard, but you will have to gain there attention first.
>>
>>
>
> I'm sorry, but even knowing a bit 'of the C programming language, I
> have never written a driver, I'm not able, and I honestly do not even
> capable.
>
> You tell me to add support to the current driver, but I have no idea
> how to do. It is also good to clarify that the driver on the kernel
> vanulla charge in the presence of this card, but simply does not work,
> and does not create deivce (/dev/dvb/).
Take a look at linuxtv WIKI pages. It explains several useful things
on how to add support to a new device.
> So knowing that I'm not able to write the driver, I would say that
> this device is definitely dead and buried ... in this case would be at
> least that was not loaded em28xx module (the one in the kernel),
> avoiding giving the illusion that the driver functions.
>
> I do not know if you can, but should be added, if any, in a sort of blacklist.
The USB ID used by your device is generic: all devices with em2870 without
eeprom will inform the same code (and even some with eeprom, but where
the vendor didn't care to write their own ID there).
What are the components used on your device?
--
Cheers,
Mauro
prev parent reply other threads:[~2010-05-18 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 22:51 Pinnacle PCTV DVB-T 70e Alexjan Carraturo
2010-05-15 16:03 ` CityK
2010-05-18 17:12 ` Alexjan Carraturo
2010-05-18 18:10 ` Mauro Carvalho Chehab [this message]
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=4BF2D81B.5050804@redhat.com \
--to=mchehab@redhat.com \
--cc=axjslack@gmail.com \
--cc=cityk@rogers.com \
--cc=linux-media@vger.kernel.org \
--cc=video4linux-list@redhat.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