From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?J=F6rg?= Krause Date: Mon, 16 Jan 2017 21:25:16 +0100 Subject: [U-Boot] [PATCH v6 01/13] binman: Introduce binman, a tool for building binary images In-Reply-To: <1480130164-15709-2-git-send-email-sjg@chromium.org> References: <1480130164-15709-1-git-send-email-sjg@chromium.org> <1480130164-15709-2-git-send-email-sjg@chromium.org> Message-ID: <1484598316.8221.3.camel@embedded.rocks> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, On Fri, 2016-11-25 at 20:15 -0700, Simon Glass wrote: > This adds the basic code for binman, including command parsing, > processing > of entries and generation of images. > > So far no entry types are supported. These will be added in future > commits > as examples of how to add new types. > > See the README for documentation. > > Signed-off-by: Simon Glass > --- > [snip] > + > +To do > +----- > + > +Some ideas: > +- Fill out the device tree to include the final position and size of > each > +??entry (since the input file may not always specify these) > +- Use of-platdata to make the information available to code that is > unable > +??to use device tree (such as a very small SPL image) > +- Write an image map to a text file > +- Allow easy building of images by specifying just the board name > +- Produce a full Python binding for libfdt (for upstream) > +- Add an option to decode an image into the constituent binaries > +- Suppoort hierarchical images (packing of binaries into another > binary > +??which is then placed in the image) > +- Support building an image for a board (-b) more completely, with a > +??configurable build directory > +- Consider making binman work with buildman, although if it is used > in the > +??Makefile, this will be automatic > +- Implement align-end Any plans to add support for Python 3 as it is done for patman? Best regards, J?rg Krause