Hi,
On 16 January 2017 at 13:25, Jörg Krause joerg.krause@embedded.rocks wrote:
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 sjg@chromium.org
[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?
Yes that would be good...
Regards, Simon