From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: "Jan-Simon Möller" <dl9pf@gmx.de>
Cc: "Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Dênis Goes" <denishark@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: TM6010 driver and firmware
Date: Thu, 8 Oct 2009 10:39:27 -0400 [thread overview]
Message-ID: <829197380910080739h75ddba76pe7d28c60f47dd235@mail.gmail.com> (raw)
In-Reply-To: <200910081050.02215.dl9pf@gmx.de>
On Thu, Oct 8, 2009 at 4:50 AM, Jan-Simon Möller <dl9pf@gmx.de> wrote:
> Hi !
>
> Using the 3.7 firmware on HVR900H, I get up to this point:
>
> http://pastebin.ca/1603643
>
> [...]
> Error during zl10353_attach!
> tm6000: couldn't attach the frontend!
> xc2028 4-0061: destroying instance
> tm6000: Error -1 while registering
> tm6000: probe of 1-5.1:1.0 failed with error -1
> usbcore: registered new interface driver tm6000
> Original value=255
>
>
> Best,
> Jan-Simon
I keep seeing people trying out that driver, apparently thinking that
they just need to compile the correct tree in order for their product
to work. For the record, this driver is currently *TOTALLY BROKEN*.
Unless you are a developer who is prepared to reverse engineer the
wire protocol and debug the driver, then you should not be wasting
your time compiling the tree in the hope that it will work for you.
Cheers,
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
prev parent reply other threads:[~2009-10-08 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f326ee1a0910030539pd5e00e2xb9f6de9975b64b9b@mail.gmail.com>
[not found] ` <f326ee1a0910030602w2518f66q2d6e185c473d5ad@mail.gmail.com>
2009-10-05 12:53 ` Mauro Carvalho Chehab
2009-10-08 8:50 ` Jan-Simon Möller
2009-10-08 14:39 ` Devin Heitmueller [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=829197380910080739h75ddba76pe7d28c60f47dd235@mail.gmail.com \
--to=dheitmueller@kernellabs.com \
--cc=denishark@gmail.com \
--cc=dl9pf@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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
all inboxes | Powered by JetHome®