From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans-Frieder Vogt <hfvogt@gmx.net>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 3/3] Firmware for AF9035/AF9033 driver
Date: Mon, 19 Mar 2012 21:32:58 -0300 [thread overview]
Message-ID: <4F67D03A.1080606@redhat.com> (raw)
In-Reply-To: <201202222322.02424.hfvogt@gmx.net>
Em 22-02-2012 20:22, Hans-Frieder Vogt escreveu:
> Firmware for the AF9035/AF9033 driver.
>
> irmware format for af903x driver:
> copied from it9135-driver by Jason Dong (C) 2011 ITE Technologies, INC.
>
> 00000000: 8 chars "AF9035BX" Identifier of firmware
> 00000008: 4 bytes LE length of firmware following this:
> 32 + 4 + 4 + 4 + 4 + 4 + Firmware_CODELENGTH +
> Firmware_SEGMENTLENGTH * Firmware_PARTITIONLENGTH * 5 +
> 5 + 2 + Firmware_scriptSets[0] * 5;
> 0000000C: 32 chars firmware release version
> 0000002C: 4 bytes BE link version
> 00000030: 4 bytes BE ofdm version
> 00000034: 4 bytes LE firmware code length (Firmware_CODELENGTH)
> 00000038: 1 bytes number of firmware segments (Firmware_SEGMENTLENGTH)
> 00000039: 3 bytes filler (0)
> 0000003C: 1 bytes number of firmware partitions (Firmware_PARTITIONLENGTH)
> 0000003D: 3 bytes filler (0)
> 00000040: Firmware_CODELENGTH bytes
> 0000abcd: description of firmware segments, for each segment in every
> partition:
> 1 byte segment type (0: download firmware, 1: copy firmware, else:
> direct write firmware)
> 4 bytes LE segment length
> 0000bcde: 1 byte Firmware_SEGMENTLENGTH check
> 0000bcdf: 1 byte Firmware_PARTITIONLENGTH check
> 0000bce0: 3 bytes filler (0)
> 0000bce3: 2 bytes LE number of firmware (demodulator) scripts
> 0000bce5: list of firmware scripts, for each entry:
> 4 bytes LE address
> 1 byte value
>
> Signed-off-by: Hans-Frieder Vogt <hfvogt@gmx.net>
>
> http://home.arcor.de/hfvogt/af903x/dvb-usb-af9035-03.fw => for Terratec T5
> Ver. 2 / T6
> http://home.arcor.de/hfvogt/af903x/dvb-usb-af9035-04.fw => for Avermedia A867
Firmware patches should be against the linux-firmware tree [1].
[1] http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=summary
We need a licensing text signed by the board or chipset manufacturer, in order
to be able to add it there. If you can't get it, then the alternative is to change
the Documentation/dvb/get_dvb_firmware script to get it from somewhere (although
this is a bad option, as the firmware won't be distributed together with the Linux
distributions).
Regards,
Mauro
>
> Hans-Frieder Vogt e-mail: hfvogt <at> gmx .dot. net
> --
> 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
prev parent reply other threads:[~2012-03-20 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 22:22 [PATCH 3/3] Firmware for AF9035/AF9033 driver Hans-Frieder Vogt
2012-02-23 9:20 ` Oliver Schinagl
2012-02-27 0:33 ` Daniel Glöckner
2012-02-27 22:35 ` Hans-Frieder Vogt
2012-03-20 0:32 ` Mauro Carvalho Chehab [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=4F67D03A.1080606@redhat.com \
--to=mchehab@redhat.com \
--cc=hfvogt@gmx.net \
--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;
as well as URLs for NNTP newsgroup(s).