[U-Boot] [PATCH v4 6/7] arm: add Faraday firmware image utility
Kuo-Jung Su
dantesu at gmail.com
Tue Jun 11 05:00:29 CEST 2013
2013/6/11 Albert ARIBAUD <albert.u.boot at aribaud.net>:
> Hi Kuo-Jung,
>
> On Tue, 7 May 2013 14:25:12 +0800, Kuo-Jung Su <dantesu at gmail.com>
> wrote:
>
>> From: Kuo-Jung Su <dantesu at faraday-tech.com>
>>
>> Signed-off-by: Kuo-Jung Su <dantesu at faraday-tech.com>
>> CC: Albert Aribaud <albert.u.boot at aribaud.net>
>> ---
>> Changes for v4:
>> - Coding Style cleanup.
>> - Break up from [arm: add Faraday A36x SoC platform support]
>>
>> Changes for v3:
>> - Coding Style cleanup.
>> - Always insert a blank line between declarations and code.
>>
>> Changes for v2:
>> - Coding Style cleanup.
>>
>> arch/arm/cpu/faraday/Makefile | 2 +-
>> arch/arm/cpu/faraday/cmd_bootfa.c | 132 +++++++++++++++++++++++++++++++++++++
>> arch/arm/cpu/faraday/fwimage.h | 38 +++++++++++
>> arch/arm/cpu/faraday/fwimage2.h | 70 ++++++++++++++++++++
>> arch/arm/cpu/u-boot.lds | 11 ++++
>> 5 files changed, 252 insertions(+), 1 deletion(-)
>> create mode 100644 arch/arm/cpu/faraday/cmd_bootfa.c
>> create mode 100644 arch/arm/cpu/faraday/fwimage.h
>> create mode 100644 arch/arm/cpu/faraday/fwimage2.h
>
> What is the rationale behind a specific boot command?
Got it, thanks.
I'll add the rationale at next patch.
> What prevents
> using the existing tools and formats?
>
The private firmware image format is designed for better backward compatibility
to the hard-wired ROM code for Faraday A36x SoC.
I'll try to revise the design and see if it's possible to adapt it to
existing u-boot tools and formats.
> Amicalement,
> --
> Albert.
--
Best wishes,
Kuo-Jung Su
More information about the U-Boot
mailing list