Skip to content
Snippets Groups Projects
  1. Feb 03, 2022
    • Simon Glass's avatar
      scripts/checkpatch.pl: Resync with v5.16 · 587254eb
      Simon Glass authored and Tom Rini's avatar Tom Rini committed
      
      This resyncs us with the version found in v5.16 of the Linux kernel with
      the following exceptions:
      - Keep our u-boot specific tests / code area.
      - Change the location of checkpatch.rst
      - Drop the "use strscpy" test as we don't have that, but do have strlcpy
        and want that used now.
      - Keep debug/printf in the list for $logFunctions
      
      This also syncs the spdxcheck.py tool and all the associated
      documentation.
      S
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      587254eb
  2. Jan 29, 2022
  3. Jan 28, 2022
  4. Jan 25, 2022
    • Simon Glass's avatar
      binman: Add documentation for bintools · 3e7749ea
      Simon Glass authored
      
      Add this documention to explain how bintools are used and which ones are
      available.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      3e7749ea
    • Rasmus Villemoes's avatar
      introduce CONFIG_DEVICE_TREE_INCLUDES · a77f4680
      Rasmus Villemoes authored and Simon Glass's avatar Simon Glass committed
      
      The build system already automatically looks for and includes an
      in-tree *-u-boot.dtsi when building the control .dtb. However, there
      are some things that are awkward to maintain in such an in-tree file,
      most notably the metadata associated to public keys used for verified
      boot.
      
      The only "official" API to get that metadata into the .dtb is via
      mkimage, as a side effect of building an actual signed image. But
      there are multiple problems with that. First of all, the final U-Boot
      (be it U-Boot proper or an SPL) image is built based on a binary
      image, the .dtb, and possibly some other binary artifacts. So
      modifying the .dtb after the build requires the meta-buildsystem
      (Yocto, buildroot, whatnot) to know about and repeat some of the steps
      that are already known to and handled by U-Boot's build system,
      resulting in needless duplication of code. It's also somewhat annoying
      and inconsistent to have a .dtb file in the build folder which is not
      generated by the command listed in the corresponding .cmd file (that
      of course applies to any generated file).
      
      So the contents of the /signature node really needs to be baked into
      the .dtb file when it is first created, which means providing the
      relevant data in the form of a .dtsi file. One could in theory put
      that data into the *-u-boot.dtsi file, but it's more convenient to be
      able to provide it externally: For example, when developing for a
      customer, it's common to use a set of dummy keys for development,
      while the consultants do not (and should not) have access to the
      actual keys used in production. For such a setup, it's easier if the
      keys used are chosen via the meta-buildsystem and the path(s) patched
      in during the configure step. And of course, nothing prevents anybody
      from having DEVICE_TREE_INCLUDES point at files maintained in git, or
      for that matter from including the public key metadata in the
      *-u-boot.dtsi directly and ignore this feature.
      
      There are other uses for this, e.g. in combination with ENV_IMPORT_FDT
      it can be used for providing the contents of the /config/environment
      node, so I don't want to tie this exclusively to use for verified
      boot.
      
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarRasmus Villemoes <rasmus.villemoes@prevas.dk>
      Fix doc formatting error (make htmldocs)
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      a77f4680
    • Simon Glass's avatar
      doc: Add usage information for the acpi command · 02155e05
      Simon Glass authored
      
      Add some documentation for this command.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      02155e05
  5. Jan 24, 2022
    • Simon Glass's avatar
      moveconfig: Allow querying board configuration · 65d7fcec
      Simon Glass authored and Tom Rini's avatar Tom Rini committed
      
      It is useful to be able to find out which boards define a particular
      option, or combination of options. This is not as easy as grepping the
      defconfig files since many options are implied by others.
      
      Add a -f option to the moveconfig tool to permit this. Update the
      documentation to cover this, including a better title for the doc page.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      65d7fcec
    • Simon Glass's avatar
      Makefile: Add a pylint checker to the build · feafc61e
      Simon Glass authored and Tom Rini's avatar Tom Rini committed
      
      At present the Python code in U-Boot is somewhat inconsistent, with some
      files passing pylint quite cleanly and others not.
      
      Add a way to track progress on this clean-up, by checking that no module
      has got any worse as a result of changes.
      
      This can be used with 'make pylint'.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      [trini: Re-generate pylint.base]
      feafc61e
    • Jan Kiszka's avatar
      mkimage: Allow to specify the signature algorithm on the command line · 5902a397
      Jan Kiszka authored and Tom Rini's avatar Tom Rini committed
      
      This permits to prepare FIT image description that do not hard-code the
      final choice of the signature algorithm, possibly requiring the user to
      patch the sources.
      
      When -o <algo> is specified, this information is used in favor of the
      'algo' property in the signature node. Furthermore, that property is set
      accordingly when writing the image.
      
      Signed-off-by: default avatarJan Kiszka <jan.kiszka@siemens.com>
      5902a397
  6. Jan 19, 2022
  7. Jan 18, 2022
  8. Jan 15, 2022
  9. Jan 13, 2022
  10. Jan 08, 2022
    • Patrick Wildt's avatar
      imx8mq: Generate a single bootable flash.bin again · b05cebb5
      Patrick Wildt authored and Tom Rini's avatar Tom Rini committed
      
      All i.MX8MQ boards have been converted to binman, which makes it
      necessary to flash both flash.bin and u-boot.itb to get a bootable
      system. Prior to the conversion, only flash.bin was needed.
      
      Such new requirement breaks existing distro mechanisms to generate the
      final binary because the extra u-boot.itb is now required.
      
      Generate a final flash.bin that can be used again as a single bootable
      binary to keep the original behavior.
      
      After this change the SPL binary is called spl.bin, which is a more
      descriptive name for its purpose, and can still be used standalone (for
      example, for secure boot purposes).
      
      Also update imx8mq_evk.rst to remove the u-boot.itb copy step.
      
      This is a cherry-pick of 028abfd9 ("imx8mm-evk: Generate a single
      bootable flash.bin again") adjusted to apply to i.MX8MQ.
      
      Signed-off-by: default avatarPatrick Wildt <patrick@blueri.se>
      Reviewed-by: default avatarFabio Estevam <festevam@denx.de>
      b05cebb5
  11. Jan 07, 2022
  12. Jan 05, 2022
  13. Dec 31, 2021
  14. Dec 27, 2021
    • Tom Rini's avatar
      Finish converting CONFIG_SYS_FSL_CLK to Kconfig · ada261f1
      Tom Rini authored
      
      This converts the following to Kconfig:
         CONFIG_SYS_FSL_CLK
      
      We move the exiting option to common/Kconfig near the other options to
      control the contents of board_init_f() and note that this is a legacy
      option.  We further restrict this to where the call is going to be
      non-empty, for the SoCs that had only been using this for some
      MMC-related clocks.
      
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      ada261f1
Loading