From: Daniel Exner <dex@dragonslave.de>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: dex@dragonslave.de
Subject: Re: Terratec Cinergy T XS Firmware (Kernel 3.14.1)
Date: Wed, 23 Apr 2014 22:50:36 +0200 [thread overview]
Message-ID: <5358279C.5060108@dragonslave.de> (raw)
In-Reply-To: <CAGoCfizxAopbb4pEtGXVtSSuccqAfu7iqB8Oc2Lb6TOS=6QL8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
Hi,
Am 23.04.2014 22:42, schrieb Devin Heitmueller:
> On Wed, Apr 23, 2014 at 4:34 PM, Daniel Exner <dex@dragonslave.de> wrote:
> You can get the firmware via the following procedure:
>
> http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028#How_to_Obtain_the_Firmware
>
> or if you're on Ubuntu it's already packaged in
> linux-firmware-nonfree. The file itself is 66220 bytes and has an MD5
> checksum of 293dc5e915d9a0f74a368f8a2ce3cc10.
I used that procedure and have exactly that file in my /lib/firmware dir.
> Note that if you have that file in /lib/firmware, it's entirely
> possible that the driver is just broken (this happens quite often).
> The values read back by dmesg are from the device itself, so if the
> chip wasn't properly initialized fields such as the version will
> contain garbage values.
On the page you linked above older firmware versions are mentions that
should be supported by the driver.
My Question is: how to get them?
But you may be right, because "Device is Xceive 34584" seems also wrong
(didn't find any hint such a device exists..)
I'm willing to invest some time to repair the driver.
Anyone interested in helping me in getting this thing back to work?
Greetings
Daniel
--
Daniel Exner
Public-Key: https://www.dragonslave.de/pub_key.asc
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-04-23 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 20:34 Terratec Cinergy T XS Firmware (Kernel 3.14.1) Daniel Exner
2014-04-23 20:42 ` Devin Heitmueller
2014-04-23 20:50 ` Daniel Exner [this message]
2014-04-24 11:29 ` Mauro Carvalho Chehab
2014-04-24 19:09 ` Daniel Exner
2014-04-24 19:24 ` Devin Heitmueller
2014-04-24 21:26 ` Mauro Carvalho Chehab
2014-04-25 19:40 ` Daniel Exner
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=5358279C.5060108@dragonslave.de \
--to=dex@dragonslave.de \
--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 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.