From: Marian Balakowicz <m8@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: New U-boot image format
Date: Wed, 19 Dec 2007 15:26:11 +0100 [thread overview]
Message-ID: <47692A03.6030700@semihalf.com> (raw)
In-Reply-To: <4761B528.3080601@semihalf.com>
Marian Balakowicz wrote:
[...]
>>> 3. 'New image' format must support the following features:
>> [snip]
>>
>>> - 'container' image blob shall include 'component' images'
>>> data, which means direct data embedding - as opposed to
>>> having only references
>> Q for Jon L: This would require an extension to the dtc to "include" a
>> raw file into the blob? I'm presuming that we don't want to take a
>> binary (ELF) file, turn it into ASCII bytes, include it into a dts, and
>> then use dtc to compile it back into binary.
>>
>> Am I missing something that is already available? Do you see any
>> problems with extending dtc to support this?
>
> AFAIK dtc currently has no support for data includes. I've seen such
> feature on a dtc wish list though, so adding it should not be troublesome.
Jon, David,
Are you aware if anyone is working on a binary includes for dtc?
This feature will be needed for U-boot New uImage format implementation,
so I wonder what is the actual status of this dtc wish list item.
Thanks,
Marian
next prev parent reply other threads:[~2007-12-19 14:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 16:18 [U-Boot-Users] RFC: New U-boot image format Marian Balakowicz
2007-12-11 16:32 ` [U-Boot-Users] RFC: New U-boot image format - open issues Marian Balakowicz
2007-12-11 19:23 ` [U-Boot-Users] RFC: New U-boot image format Jerry Van Baren
2007-12-11 22:23 ` Wolfgang Denk
2007-12-12 12:38 ` Jerry Van Baren
2007-12-13 22:59 ` Marian Balakowicz
2007-12-13 22:41 ` Marian Balakowicz
2007-12-14 6:17 ` Wolfgang Denk
2007-12-14 21:44 ` T Ziomek
2007-12-19 14:26 ` Marian Balakowicz [this message]
2007-12-20 0:50 ` David Gibson
2007-12-20 16:41 ` Scott Wood
2007-12-20 22:25 ` Marian Balakowicz
2007-12-20 22:39 ` Scott Wood
2007-12-21 0:17 ` David Gibson
2007-12-18 15:17 ` Timur Tabi
2007-12-18 15:33 ` Jerry Van Baren
2007-12-18 15:36 ` Timur Tabi
2007-12-18 16:12 ` Wolfgang Denk
2007-12-18 16:17 ` Timur Tabi
2007-12-18 19:42 ` Wolfgang Denk
2007-12-18 19:47 ` Timur Tabi
2007-12-18 20:11 ` Wolfgang Denk
2007-12-18 20:18 ` Timur Tabi
2007-12-19 14:07 ` Marian Balakowicz
2007-12-20 19:42 ` Wolfgang Denk
2007-12-21 15:04 ` Marian Balakowicz
2007-12-21 15:17 ` Wolfgang Denk
2007-12-21 15:39 ` Marian Balakowicz
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=47692A03.6030700@semihalf.com \
--to=m8@semihalf.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox