binary-manager 0.1.3__tar.gz → 0.2.1__tar.gz

{binary_manager-0.1.3 → binary_manager-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: binary-manager
-Version: 0.1.3
+Version: 0.2.1
 Summary: Package firmware binaries into images described by a devicetree
 Author-email: Simon Glass <sjg@chromium.org>
 License-Expression: GPL-2.0-or-later
@@ -25,6 +25,7 @@ Requires-Dist: jsonschema
 Requires-Dist: PyYAML
 Requires-Dist: yamllint
 Requires-Dist: u-boot-pylib>=0.1.0
+Requires-Dist: dtoc>=0.1.0
 Provides-Extra: test
 Requires-Dist: concurrencytest; extra == "test"
 Requires-Dist: coverage; extra == "test"
@@ -60,15 +61,20 @@ they require, then use binman to stitch everything together into an image. It:
 - reads an image description from a devicetree and works out what to place
   where, with padding, alignment, compression and hashing;
 - supports hierarchical images and a large set of entry types, including FIT,
-  CBFS, ARM Trusted Firmware FIP and many SoC-specific formats;
+  coreboot's CBFS and flash maps, the ARM Trusted Firmware FIP and many
+  SoC-specific formats;
 - lets firmware find other binaries in the image, using linker symbols or the
   devicetree description of the image;
 - inspects existing images, extracting and replacing their contents and
   repacking where needed;
-- copes with missing binary blobs and fetches the external tools it needs.
+- copes with missing binary blobs and fetches the external tools it needs;
+- fetches firmware blobs such as TF-A, building them from source where it can,
+  and keeps them in a cache.
 
-Binman is designed primarily for use with U-Boot and associated binaries such
-as ARM Trusted Firmware, but is general enough to be used with other projects.
+Binman started as part of U-Boot and still builds U-Boot's images, but it is
+not tied to U-Boot. It can build coreboot images from a coreboot flash-map
+descriptor, and can package the firmware for TF-A, OP-TEE, Zephyr or any other
+project.
 
 Installation
 ------------
@@ -86,10 +92,17 @@ The ``binman`` command is then on your path.
 Quick start
 -----------
 
-Build an image from the description in a devicetree, taking the input files
-from the current directory::
+Build the images described in a devicetree, taking the input files from the
+current directory::
 
-    binman build -d u-boot.dtb
+    binman build -d image.dts -I .
+
+When run in a U-Boot build directory, or with one as an input directory,
+binman treats the devicetree as U-Boot's own, updating it with the image
+layout. To package U-Boot's binaries which have been copied elsewhere, select
+the u-boot project::
+
+    binman --project u-boot build -u -d u-boot.dtb -I .
 
 List the contents of an existing image::
 
@@ -100,6 +113,12 @@ missing::
 
     binman tool -f missing
 
+Fetch a firmware blob, here TF-A's BL31 for an Allwinner A64 board, building
+it from source::
+
+    binman blob -f arm,trusted-firmware-a --version 2.12 --arch aarch64 \
+        --plat sun50i_a64
+
 See ``binman -H`` for the complete manual, or the documentation linked below.
 
 Documentation
@@ -128,6 +147,6 @@ since the expected output tracks its development; pass ``--toolpath`` to point
 binman at a U-Boot ``tools/`` build directory. ``binman test -T`` checks that
 the tests cover all of the code.
 
-The ``dtoc`` library is vendored from the U-Boot tree and ``u_boot_pylib`` is
-installed from PyPI as ``u-boot-pylib``, so no surrounding U-Boot source is
+The ``dtoc`` and ``u_boot_pylib`` libraries are installed from PyPI, as the
+``dtoc`` and ``u-boot-pylib`` packages, so no surrounding U-Boot source is
 required.

{binary_manager-0.1.3 → binary_manager-0.2.1}/README.rst

@@ -28,15 +28,20 @@ they require, then use binman to stitch everything together into an image. It:
 - reads an image description from a devicetree and works out what to place
   where, with padding, alignment, compression and hashing;
 - supports hierarchical images and a large set of entry types, including FIT,
-  CBFS, ARM Trusted Firmware FIP and many SoC-specific formats;
+  coreboot's CBFS and flash maps, the ARM Trusted Firmware FIP and many
+  SoC-specific formats;
 - lets firmware find other binaries in the image, using linker symbols or the
   devicetree description of the image;
 - inspects existing images, extracting and replacing their contents and
   repacking where needed;
-- copes with missing binary blobs and fetches the external tools it needs.
+- copes with missing binary blobs and fetches the external tools it needs;
+- fetches firmware blobs such as TF-A, building them from source where it can,
+  and keeps them in a cache.
 
-Binman is designed primarily for use with U-Boot and associated binaries such
-as ARM Trusted Firmware, but is general enough to be used with other projects.
+Binman started as part of U-Boot and still builds U-Boot's images, but it is
+not tied to U-Boot. It can build coreboot images from a coreboot flash-map
+descriptor, and can package the firmware for TF-A, OP-TEE, Zephyr or any other
+project.
 
 Installation
 ------------
@@ -54,10 +59,17 @@ The ``binman`` command is then on your path.
 Quick start
 -----------
 
-Build an image from the description in a devicetree, taking the input files
-from the current directory::
+Build the images described in a devicetree, taking the input files from the
+current directory::
 
-    binman build -d u-boot.dtb
+    binman build -d image.dts -I .
+
+When run in a U-Boot build directory, or with one as an input directory,
+binman treats the devicetree as U-Boot's own, updating it with the image
+layout. To package U-Boot's binaries which have been copied elsewhere, select
+the u-boot project::
+
+    binman --project u-boot build -u -d u-boot.dtb -I .
 
 List the contents of an existing image::
 
@@ -68,6 +80,12 @@ missing::
 
     binman tool -f missing
 
+Fetch a firmware blob, here TF-A's BL31 for an Allwinner A64 board, building
+it from source::
+
+    binman blob -f arm,trusted-firmware-a --version 2.12 --arch aarch64 \
+        --plat sun50i_a64
+
 See ``binman -H`` for the complete manual, or the documentation linked below.
 
 Documentation
@@ -96,6 +114,6 @@ since the expected output tracks its development; pass ``--toolpath`` to point
 binman at a U-Boot ``tools/`` build directory. ``binman test -T`` checks that
 the tests cover all of the code.
 
-The ``dtoc`` library is vendored from the U-Boot tree and ``u_boot_pylib`` is
-installed from PyPI as ``u-boot-pylib``, so no surrounding U-Boot source is
+The ``dtoc`` and ``u_boot_pylib`` libraries are installed from PyPI, as the
+``dtoc`` and ``u-boot-pylib`` packages, so no surrounding U-Boot source is
 required.

{binary_manager-0.1.3 → binary_manager-0.2.1}/binary_manager.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: binary-manager
-Version: 0.1.3
+Version: 0.2.1
 Summary: Package firmware binaries into images described by a devicetree
 Author-email: Simon Glass <sjg@chromium.org>
 License-Expression: GPL-2.0-or-later
@@ -25,6 +25,7 @@ Requires-Dist: jsonschema
 Requires-Dist: PyYAML
 Requires-Dist: yamllint
 Requires-Dist: u-boot-pylib>=0.1.0
+Requires-Dist: dtoc>=0.1.0
 Provides-Extra: test
 Requires-Dist: concurrencytest; extra == "test"
 Requires-Dist: coverage; extra == "test"
@@ -60,15 +61,20 @@ they require, then use binman to stitch everything together into an image. It:
 - reads an image description from a devicetree and works out what to place
   where, with padding, alignment, compression and hashing;
 - supports hierarchical images and a large set of entry types, including FIT,
-  CBFS, ARM Trusted Firmware FIP and many SoC-specific formats;
+  coreboot's CBFS and flash maps, the ARM Trusted Firmware FIP and many
+  SoC-specific formats;
 - lets firmware find other binaries in the image, using linker symbols or the
   devicetree description of the image;
 - inspects existing images, extracting and replacing their contents and
   repacking where needed;
-- copes with missing binary blobs and fetches the external tools it needs.
+- copes with missing binary blobs and fetches the external tools it needs;
+- fetches firmware blobs such as TF-A, building them from source where it can,
+  and keeps them in a cache.
 
-Binman is designed primarily for use with U-Boot and associated binaries such
-as ARM Trusted Firmware, but is general enough to be used with other projects.
+Binman started as part of U-Boot and still builds U-Boot's images, but it is
+not tied to U-Boot. It can build coreboot images from a coreboot flash-map
+descriptor, and can package the firmware for TF-A, OP-TEE, Zephyr or any other
+project.
 
 Installation
 ------------
@@ -86,10 +92,17 @@ The ``binman`` command is then on your path.
 Quick start
 -----------
 
-Build an image from the description in a devicetree, taking the input files
-from the current directory::
+Build the images described in a devicetree, taking the input files from the
+current directory::
 
-    binman build -d u-boot.dtb
+    binman build -d image.dts -I .
+
+When run in a U-Boot build directory, or with one as an input directory,
+binman treats the devicetree as U-Boot's own, updating it with the image
+layout. To package U-Boot's binaries which have been copied elsewhere, select
+the u-boot project::
+
+    binman --project u-boot build -u -d u-boot.dtb -I .
 
 List the contents of an existing image::
 
@@ -100,6 +113,12 @@ missing::
 
     binman tool -f missing
 
+Fetch a firmware blob, here TF-A's BL31 for an Allwinner A64 board, building
+it from source::
+
+    binman blob -f arm,trusted-firmware-a --version 2.12 --arch aarch64 \
+        --plat sun50i_a64
+
 See ``binman -H`` for the complete manual, or the documentation linked below.
 
 Documentation
@@ -128,6 +147,6 @@ since the expected output tracks its development; pass ``--toolpath`` to point
 binman at a U-Boot ``tools/`` build directory. ``binman test -T`` checks that
 the tests cover all of the code.
 
-The ``dtoc`` library is vendored from the U-Boot tree and ``u_boot_pylib`` is
-installed from PyPI as ``u-boot-pylib``, so no surrounding U-Boot source is
+The ``dtoc`` and ``u_boot_pylib`` libraries are installed from PyPI, as the
+``dtoc`` and ``u-boot-pylib`` packages, so no surrounding U-Boot source is
 required.

{binary_manager-0.1.3 → binary_manager-0.2.1}/binary_manager.egg-info/SOURCES.txt

@@ -23,21 +23,21 @@ binman/control.py
 binman/elf.py
 binman/elf_test.py
 binman/entry.py
+binman/entry_groups.py
 binman/entry_test.py
 binman/fdt_test.py
 binman/fetchbase.py
 binman/fip_util.py
 binman/fip_util_test.py
 binman/fmap_util.py
+binman/fmd_util.py
+binman/fmd_util_test.py
 binman/ftest.py
 binman/image.py
 binman/image_test.py
 binman/main.py
 binman/missing-blob-help
 binman/state.py
-binman/_vendor/dtoc/__init__.py
-binman/_vendor/dtoc/fdt.py
-binman/_vendor/dtoc/fdt_util.py
 binman/blobs/__init__.py
 binman/blobs/_testing.py
 binman/blobs/atf.py
@@ -164,6 +164,7 @@ binman/etype/x86_start16.py
 binman/etype/x86_start16_spl.py
 binman/etype/x86_start16_tpl.py
 binman/etype/xilinx_bootgen.py
+binman/include/binman_sym.h
 binman/test/Makefile
 binman/test/blob_syms.c
 binman/test/blob_syms.lds
@@ -240,6 +241,19 @@ binman/test/cbfs/bad_compress.dts
 binman/test/cbfs/bad_type.dts
 binman/test/cbfs/coreboot_rom.dts
 binman/test/cbfs/coreboot_rom_collection.dts
+binman/test/cbfs/coreboot_rom_create.dts
+binman/test/cbfs/coreboot_rom_create_missing.dts
+binman/test/cbfs/coreboot_rom_files.dts
+binman/test/cbfs/coreboot_rom_files_bad_type.dts
+binman/test/cbfs/coreboot_rom_files_collection.dts
+binman/test/cbfs/coreboot_rom_files_mixed.dts
+binman/test/cbfs/coreboot_rom_files_no_addr.dts
+binman/test/cbfs/coreboot_rom_files_no_content.dts
+binman/test/cbfs/coreboot_rom_files_not_elf.dts
+binman/test/cbfs/coreboot_rom_fmd.dts
+binman/test/cbfs/coreboot_rom_fmd_bad.dts
+binman/test/cbfs/coreboot_rom_fmd_both.dts
+binman/test/cbfs/coreboot_rom_fmd_region_name.dts
 binman/test/cbfs/coreboot_rom_missing.dts
 binman/test/cbfs/coreboot_rom_nested_spl.dts
 binman/test/cbfs/coreboot_rom_no_addr.dts
@@ -286,6 +300,7 @@ binman/test/entry/entry_args_unknown_datatype.dts
 binman/test/entry/env.dts
 binman/test/entry/env_no_size.dts
 binman/test/entry/env_too_small.dts
+binman/test/entry/etype_dir.dts
 binman/test/entry/files.dts
 binman/test/entry/files_align.dts
 binman/test/entry/files_compress.dts
@@ -330,6 +345,8 @@ binman/test/entry/unique_names.dts
 binman/test/entry/unique_names_multi.dts
 binman/test/entry/unknown_contents.dts
 binman/test/entry/unknown_pos_size.dts
+binman/test/etype_dir/dev_etype.py
+binman/test/etype_dir/fill.py
 binman/test/fdt/alternates_fdt.dts
 binman/test/fdt/alternates_fdtgrep.dts
 binman/test/fdt/alternates_inval.dts
@@ -358,6 +375,8 @@ binman/test/fdt/incl.dts
 binman/test/fdt/incl_tpl.dts
 binman/test/fdt/incl_vpl.dts
 binman/test/fdt/list_fdtmap.dts
+binman/test/fdt/plain.dts
+binman/test/fdt/plain_section.dts
 binman/test/fdt/update.dts
 binman/test/fdt/update_all.dts
 binman/test/fdt/update_all_repack.dts
@@ -404,6 +423,7 @@ binman/test/fit/fit.dts
 binman/test/fit/gennode.dts
 binman/test/fit/image_subentry_alignment.dts
 binman/test/fit/key_name_hint_dir_signature.dts
+binman/test/fit/large.dts
 binman/test/fit/missing_blob.dts
 binman/test/fit/openssl.conf
 binman/test/fit/replace_sibling.dts

{binary_manager-0.1.3 → binary_manager-0.2.1}/binary_manager.egg-info/requires.txt

@@ -5,6 +5,7 @@ jsonschema
 PyYAML
 yamllint
 u-boot-pylib>=0.1.0
+dtoc>=0.1.0
 
 [test]
 concurrencytest

binary_manager-0.2.1/binman/__init__.py

@@ -0,0 +1,3 @@
+# SPDX-License-Identifier: GPL-2.0+
+
+"""Binman firmware packager"""