From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marian Balakowicz <m8@semihalf.com>
Date: Wed, 19 Dec 2007 15:26:11 +0100
Subject: [U-Boot-Users] RFC: New U-boot image format
In-Reply-To: <4761B528.3080601@semihalf.com>
References: <475EB857.4080104@semihalf.com> <475EE3AE.6060102@ge.com>
	<4761B528.3080601@semihalf.com>
Message-ID: <47692A03.6030700@semihalf.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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