From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Gibson Date: Thu, 20 Dec 2007 11:50:10 +1100 Subject: [U-Boot-Users] RFC: New U-boot image format In-Reply-To: <47692A03.6030700@semihalf.com> References: <475EB857.4080104@semihalf.com> <475EE3AE.6060102@ge.com> <4761B528.3080601@semihalf.com> <47692A03.6030700@semihalf.com> Message-ID: <20071220005010.GA23395@localhost.localdomain> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Dec 19, 2007 at 03:26:11PM +0100, Marian Balakowicz wrote: > 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. I don't believe anyone's looked at it so far. It really shouldn't take more than a couple of days once Jon or I gets to thinking about it. The trickiest bit is just thinking of a good syntax for it. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson