From: Stefan Ringel <stefan.ringel@arcor.de>
To: Abhijit Bhopatkar <bain@devslashzero.com>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Hauppague WinTV USB2-stick (tm6010)
Date: Tue, 23 Feb 2010 17:53:07 +0100 [thread overview]
Message-ID: <4B8407F3.3050802@arcor.de> (raw)
In-Reply-To: <201002232151.25852.bain@devslashzero.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 23.02.2010 17:21, schrieb Abhijit Bhopatkar:
> On Tuesday 23 Feb 2010 9:45:18 pm Devin Heitmueller wrote:
>> On Tue, Feb 23, 2010 at 11:12 AM, Abhijit Bhopatkar
>>
>> <bain@devslashzero.com> wrote:
>>> Is it worth for me to test this latest tree and driver against my card by
>>> just adding the device ids?
>>> If the devs need some more testing / help i can certainly volunteer my
>>> time/efforts.
>>> I do have fare familiarity with linux driver development and would be
>>> happy to help in debugging/developing support for this tuner. The only
>>> thing i don't have is knowledge for making this chipset work.
>>
>> Don't bother. The driver is known to be broken - badly. It needs
>> alot of work, although someone has finally started hacking at the
>> tm6000 driver recently (see the mailing list archives for more info).
>>
>
> Devin, thanks for the input
>
> I see that Stefan is doing some patching/cleanup.
>
> Stefan, is there anything i can do to help?
>
> Abhijit
I think, you can help to analyse the usb data communication -> what
for tuner, demodulator, gpio's etc.? And you can also ask Mauro
Carvalho Chehab.
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLhAfzAAoJEDX/lZlmjdJlUPYH/RnDzHGSWwC78Nc2FgKDPkYw
RFnDOImVo4G+i/Mr0UtZB9JIx75lkntwPeeJVp+aal3tLBECil0eYLco6jTuxcYt
V5iBuSZClycyvaWBc+VFi40rJcX3cqG6210GwIzNZMJH41/wPhAj15D4BVauiNsc
8ZhupI0HhM66w5LiO22fYq80WkgTb7dx5UMBVDzhkKNaS4f5mmcvyxWMJZrVzesN
Fv36lsp/RnqdmT5GgOR6Bgc/zExyiHIiLmEVclmfKv1ExeuqrwscN8F6eASlqXlK
iXQgMYmqEb3jTtKJRzLi4R/Yl0s16iOhvK0AA7AAybBj3liQOZKeh/k5HG3Hf6g=
=g/SL
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-02-23 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 16:12 Hauppague WinTV USB2-stick (tm6010) Abhijit Bhopatkar
2010-02-23 16:15 ` Devin Heitmueller
2010-02-23 16:21 ` Abhijit Bhopatkar
2010-02-23 16:53 ` Stefan Ringel [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=4B8407F3.3050802@arcor.de \
--to=stefan.ringel@arcor.de \
--cc=bain@devslashzero.com \
--cc=dheitmueller@kernellabs.com \
--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