From: Kevin Wells <wells_kevin@yahoo.co.nz>
To: linux-media@vger.kernel.org
Subject: Re: tm6010 status
Date: Mon, 05 Oct 2009 09:53:16 +1300 [thread overview]
Message-ID: <4AC90B3C.7060407@yahoo.co.nz> (raw)
In-Reply-To: <4AC8C44E.4050103@free.fr>
matthieu castet wrote:
> Hi,
>
> what's the status of tm6010 support ?
>
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04048.html
> announced some patches,
> but nothing seems to have happened ?
>
>
> Matthieu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Mauro has it on his TODO list:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg08770.html
I'm not spending any time on this at the moment, and probably won't in
the future. I spent some time reading the code for the existing driver
and submitted a few trivial patches, and quite a bit of time with a USB
sniffer to try and determine where the Linux and Windows XP driver
behaved differently. But I have subsequently purchased an Asus My-Cinema
U3100 Mini (DVB-T only) that is cheap and worked out of the box on
Ubuntu. So I no longer have much motivation to work on this.
I was surprised to find that data sheets are difficult to obtain for the
tm6010, and for a lot of other chips used in TV devices as well. Why? I
thought these companies made money by selling chips in significant
volume rather than by selling development kits. So surely they would
sell more chips by making documentation available to anyone who wants to
support their products. If there are trade secrets they are trying to
protect surely these are in the hardware and firmware rather than the
driver and the protocols used to communicate with the hardware. Perhaps
someone on this list can explain how this makes business sense.
So it seems it is common practice to use reverse engineering to get
drivers working. This is a lot of work and makes me really appreciate
the work that has been put in by v4l developers.
Kevin Wells
next prev parent reply other threads:[~2009-10-04 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 15:50 tm6010 status matthieu castet
2009-10-04 20:53 ` Kevin Wells [this message]
[not found] ` <f326ee1a0910040910p3400a8a7idd91a280e638bec5@mail.gmail.com>
2009-10-05 21:54 ` matthieu castet
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=4AC90B3C.7060407@yahoo.co.nz \
--to=wells_kevin@yahoo.co.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox