From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 7/8] imximage: Add MX53 boot image support
Date: Fri, 31 Dec 2010 11:03:31 +0100 [thread overview]
Message-ID: <4D1DAA73.1030009@denx.de> (raw)
In-Reply-To: <AANLkTimUduwb8ktCPZw1RnJHAzbNiLcdr8-9vheee8DM@mail.gmail.com>
On 12/31/2010 10:25 AM, Jason Liu wrote:
> Hi, Wolfgang,
>
> 2010/12/31 Wolfgang Denk <wd@denx.de>:
>> Dear Jason Liu,
>>
>> In message <AANLkTik1uxZK+7LL6cHtQ465Z4x+pm-kfQeaLi=D7-9S@mail.gmail.com> you wrote:
>>>
>>>> This looks as if you added something to the standard 64 byte image
>>>> header. You must not modify this. It is fixed for all architectures
>>>> and cannot be extended.
>>>
>>> This change is specific for I.MX chip and will not affect other architectur> es.
>>
>> All architectures use exactly the same binary image header. This
>> header has no version field, and such a field cannot be added.
>
> Here, the imx header is the data structure we defined in imximage.c
> and it will be used to generate
> the boot-able image u-boot.imx of i.mx soc together with u-boot.bin by
> .set_header function call of struct
> image_type_params according to FSLi.MX boot ROM requirement.
Yes, the field is inside the imx header and not in the 64 byte structure.
>
> When run the command "mkimage -l u-boot.imx", the imx header will be
> fetched from the u-boot.imx and
> the version information will be decoded according to data structure
> definition, and then it do the verify by
> checking some magic number or tag according to different version, and
> in the end, it will print the header
> information if it pass the verification.
>
> So, I don't think it will affect other architectures.
Yes, but we rely on a single undocumented byte when on the other hand
Freescale has provided at least two well-documented magic numbers for
each version to detect if an image is valid or not. Ans as I stated,
introducing this version field generates an unneeded incompatibility
with atual images.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2010-12-31 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 12:49 [U-Boot] [PATCH v3 7/8] imximage: Add MX53 boot image support Jason Liu
2010-12-30 12:46 ` Stefano Babic
2010-12-31 3:29 ` Jason Liu
2010-12-31 6:06 ` Jason Liu
2010-12-31 8:14 ` Wolfgang Denk
2010-12-31 8:36 ` Jason Liu
2010-12-31 8:50 ` Wolfgang Denk
2010-12-31 9:25 ` Jason Liu
2010-12-31 10:03 ` Stefano Babic [this message]
2010-12-31 11:37 ` Wolfgang Denk
2010-12-31 9:48 ` Stefano Babic
2010-12-31 8:12 ` Wolfgang Denk
2010-12-31 9:55 ` Stefano Babic
2010-12-31 8:10 ` Wolfgang Denk
2010-12-31 9:35 ` Stefano Babic
2010-12-31 11:39 ` Wolfgang Denk
2010-12-31 12:47 ` Stefano Babic
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=4D1DAA73.1030009@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.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 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.