From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common, image: introduce new uimage types
Date: Mon, 16 Jan 2012 10:03:29 +0100 [thread overview]
Message-ID: <4F13E7E1.30808@denx.de> (raw)
In-Reply-To: <20120116085101.B216817133E1@gemini.denx.de>
Hello Wolfgang,
Wolfgang Denk wrote:
> Dear Heiko Schocher,
>
> In message <4F13C325.3010200@denx.de> you wrote:
>>>> - ubootimage
>>>> U-Boot image
>>>> - splimage
>>>> SPL image
>>>> - dfenvimage
>>>> Default Environment image
>>>> - ublheader
>>>> TI davinci UBL header image
>>> for ... ?
>> Oh, right, forgotten to add this in the commit message.
>>
>> They are needed for cam_enc_4xx update:
>>
>> http://patchwork.ozlabs.org/patch/136165/
>>
>> There, the UBL-header, SPL-image, U-Boot image and an default image
>> are wrapped in one FIT image.
>
> But this is conceptually broken. The IH_TYPE_* definitions are
> actually only relevant for legacy images.
>
> FIX images use an XML based, extendable data format. The whole idea
> of this is that we do NOT have to change to code when anybody needs a
> new (probably private) entry or type or whatever.
>
> In your case, it should be possible to use an existing image type
> (say, IH_TYPE_FIRMWARE) for your code, and use other distinguishing
> marks to determine which parts you work on. Probably it makes sense
> to define your own entry for each of the parts. Then only your own
> code needs to understand this.
Yep, you are right, rework this.
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2012-01-16 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 7:45 [U-Boot] [PATCH] common, image: introduce new uimage types Heiko Schocher
2012-01-15 17:30 ` Mike Frysinger
2012-01-16 6:26 ` Heiko Schocher
2012-01-16 8:51 ` Wolfgang Denk
2012-01-16 9:03 ` Heiko Schocher [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=4F13E7E1.30808@denx.de \
--to=hs@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.