From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stefan Ringel <stefan.ringel@arcor.de>
Cc: linux-media@vger.kernel.org
Subject: Re: tm6000: firmware
Date: Wed, 14 Apr 2010 14:06:49 -0700 [thread overview]
Message-ID: <4BC62E69.60600@redhat.com> (raw)
In-Reply-To: <4BC60C72.6020901@arcor.de>
Em 14-04-2010 11:41, Stefan Ringel escreveu:
> Am 14.04.2010 19:44, schrieb Mauro Carvalho Chehab:
>> Hi Stefan,
>>
>> Em 14-04-2010 09:26, Stefan Ringel escreveu:
>>
>>> Hi Mauro,
>>>
>>> Can you added these three firmwares? The third is into archive file,
>>> because I'm extracted for an user (Bee Hock Goh).
>>>
>> Sorry, but for us to put the firmwares at the server and/or add them at linux-firmware
>> git tree, we need to get the distribution rights from the manufacturer,
>> as described on:
>> http://linuxtv.org/wiki/index.php/Development:_How_to_submit_patches#Firmware_submission
>>
>> So, we need Xceive's ack, in order to add the firmware files somewhere. That's why
>> currently we're using the procedure described on the comments at the extraction
>> tool:
>> Documentation/video4linux/extract_xc3028.pl
>>
>> Cheers,
>> Mauro
>>
> OK. In the archive is the modified extract_xc3028 tool for
> tm6000-xc3028.fw . Is that useful?
Yes, but:
1) Please, send it as a patch, with the proper SOB;
2) From a diff I did here:
- my $sourcefile = "UDXTTM6000.sys";
- my $hash = "cb9deb5508a5e150af2880f5b0066d78";
- my $outfile = "tm6000-xc3028.fw";
+ my $sourcefile = "hcw85bda.sys";
+ my $hash = "0e44dbf63bb0169d57446aec21881ff2";
+ my $outfile = "xc3028-v27.fw";
This version works with another *.sys file. The proper way is to
check for the hash, and use the proper logic, based on the provided
sys file;
3) Please document where to get the UDXTTTM6000.sys file at the
comments;
4) tm6000-xc3028.fw is a really bad name. It made sense only during
the development of tuner-xc2028.c, since, on that time, it seemed that
tm6000 had a different firmware version. In fact, the first devices
appeared with v 1.e firmware. So, a proper name for that version
would be xc3028-v1e.fw. We should rename it to be consistent.
It is not clear what version is provided with this version. Is it
v3.6? On a few cases, we've seen some modified versions of XC3028 firmwares
shipped with some specific board. Is it the case?
Cheers,
Mauro
next prev parent reply other threads:[~2010-04-14 21:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BC5ECB8.2060208@arcor.de>
2010-04-14 17:44 ` tm6000: firmware Mauro Carvalho Chehab
2010-04-14 18:41 ` Stefan Ringel
2010-04-14 21:06 ` Mauro Carvalho Chehab [this message]
2010-04-15 14:37 ` Stefan Ringel
2010-04-15 17:14 ` Mauro Carvalho Chehab
2010-04-15 19:28 ` Stefan Ringel
2010-04-21 4:45 ` Mauro Carvalho Chehab
2010-04-21 15:15 ` Stefan Ringel
[not found] ` <20100421130422.7b66bdff@pedra>
2010-04-21 16:08 ` Stefan Ringel
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=4BC62E69.60600@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=stefan.ringel@arcor.de \
/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