Skip to content
Snippets Groups Projects
  1. Sep 23, 2023
    • Simon Glass's avatar
      kontron_sl28: Use u-boot-update.bin instead of u-boot.update · ae84514f
      Simon Glass authored
      
      A '.update' extension does not get preserved by buildman, so change it.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Acked-by: default avatarMichael Walle <michael@walle.cc>
    • Simon Glass's avatar
      buildman: Start the clock when the build starts · 2ce06f56
      Simon Glass authored
      
      The Kconfig and maintainer processing can take a while, sometimes 5
      seconds or more. This skews the timing printed by buildmand when the build
      completes. Start the clock when the threads start to avoid this problem.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Suggested-by: default avatarTom Rini <trini@konsulko.com>
      2ce06f56
    • Simon Glass's avatar
      buildman: Show progress when regenerating the board.cfg file · 283dcb63
      Simon Glass authored
      
      This can take a while, so show a message when starting.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Reported-by Tom Rini <trini@konsulko.com>
      283dcb63
    • Simon Glass's avatar
      buildman: Keep all common output files · 124a0da5
      Simon Glass authored
      
      Make a list of common output extensions and use it to ensure that the -k
      option preserves all of these.
      
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Suggested-by: default avatarTom Rini <trini@konsulko.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      124a0da5
    • AKASHI Takahiro's avatar
      cmd: dm: allow for selecting uclass and device · 36e45f69
      AKASHI Takahiro authored and Simon Glass's avatar Simon Glass committed
      
      The output from "dm tree" or "dm uclass" is a bit annoying
      if the number of devices available on the system is huge.
      (This is especially true on sandbox when I debug some DM code.)
      
      With this patch, we can specify the uclass name or the device
      name that we are interested in in order to limit the output.
      
      For instance,
      
      => dm uclass usb
      uclass 121: usb
      0     usb@1 @ 0bcff8b0, seq 1
      
      uclass 124: usb
      
      => dm tree usb:usb@1
       Class     Index  Probed  Driver                Name
      -----------------------------------------------------------
       usb           0  [   ]   usb_sandbox           usb@1
       usb_hub       0  [   ]   usb_hub               `-- hub
       usb_emul      0  [   ]   usb_sandbox_hub           `-- hub-emul
       usb_emul      1  [   ]   usb_sandbox_flash             |-- flash-stick@0
       usb_emul      2  [   ]   usb_sandbox_flash             |-- flash-stick@1
       usb_emul      3  [   ]   usb_sandbox_flash             |-- flash-stick@2
       usb_emul      4  [   ]   usb_sandbox_keyb              `-- keyb@3
      
      If you want forward-matching against a uclass or udevice name,
      you can specify "-e" option.
      
      => dm uclass -e usb
      uclass 15: usb_emul
      0     hub-emul @ 0bcffb00, seq 0
      1     flash-stick@0 @ 0bcffc30, seq 1
      2     flash-stick@1 @ 0bcffdc0, seq 2
      3     flash-stick@2 @ 0bcfff50, seq 3
      4     keyb@3 @ 0bd000e0, seq 4
      
      uclass 64: usb_mass_storage
      
      uclass 121: usb
      0     usb@1 @ 0bcff8b0, seq 1
      
      uclass 122: usb_dev_generic
      
      uclass 123: usb_hub
      0     hub @ 0bcff9b0, seq 0
      
      uclass 124: usb
      
      => dm tree -e usb
       Class     Index  Probed  Driver                Name
      -----------------------------------------------------------
       usb           0  [   ]   usb_sandbox           usb@1
       usb_hub       0  [   ]   usb_hub               `-- hub
       usb_emul      0  [   ]   usb_sandbox_hub           `-- hub-emul
       usb_emul      1  [   ]   usb_sandbox_flash             |-- flash-stick@0
       usb_emul      2  [   ]   usb_sandbox_flash             |-- flash-stick@1
       usb_emul      3  [   ]   usb_sandbox_flash             |-- flash-stick@2
       usb_emul      4  [   ]   usb_sandbox_keyb              `-- keyb@3
      
      Signed-off-by: default avatarAKASHI Takahiro <takahiro.akashi@linaro.org>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      36e45f69
    • Jonas Karlman's avatar
      dm: core: Report bootph-pre-ram/sram node as pre-reloc after relocation · 9e644284
      Jonas Karlman authored and Simon Glass's avatar Simon Glass committed
      
      Nodes with bootph-pre-sram/ram props are bound in multiple phases:
      1. At TPL (bootph-pre-sram) or SPL (bootph-pre-ram) phase
      2. At U-Boot proper pre-relocation phase
      3. At U-Boot proper normal phase
      
      However the binding and U-Boot Driver Model documentation indicate that
      only nodes marked with bootph-all or bootph-some-ram should be bound in
      the U-Boot proper pre-relocation phase.
      
      Change ofnode_pre_reloc to report a node with bootph-pre-ram/sram prop
      with a pre-reloc status only after U-Boot proper pre-relocation phase.
      Also update the ofnode_pre_reloc documentation to closer reflect the
      binding and driver model documentation.
      
      This changes behavior of what nodes are bound in the U-Boot proper
      pre-relocation phase. Change to bootph-all or add bootph-some-ram prop
      to restore prior behavior.
      
      Signed-off-by: default avatarJonas Karlman <jonas@kwiboo.se>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      9e644284
  2. Sep 22, 2023
  3. Sep 21, 2023
Loading