On Sun, Dec 01, 2024 at 07:42:33AM -0700, Simon Glass wrote:
> Standard passage provides for a bloblist to be passed from one firmware
> phase to the next. That can be used to pass the devicetree along as well.
> Add an option to support this.
> 
> Tests for this will be added as part of the Universal Payload work.
> 
> Note: This is the correct way to deal with bloblist, since it allows
> boards to choose whether they want to use the devicetree from there, or
> not.
> 
> Link: 
> https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
> Link: 
> https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
> Link: 
> https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
> Link: 
> https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
> Link: 
> https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
> Link: 
> https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/

You should
%s#https://patchwork.ozlabs.org/project/uboot/patch#https://lore.kernel.org/u-boot
all of these Links, aside from shorter, it's on much more broadly
distributed infrastructure. And this is a general comment as well.

> Signed-off-by: Simon Glass <[email protected]>
> ---
> 
>  common/bloblist.c                  |  1 +
>  doc/develop/devicetree/control.rst |  3 ++
>  dts/Kconfig                        |  8 ++++++
>  include/fdtdec.h                   |  3 +-
>  lib/fdtdec.c                       | 44 ++++++++++++++++++++++--------
>  5 files changed, 46 insertions(+), 13 deletions(-)

The rest of this, I need to think on.

-- 
Tom

Attachment: signature.asc
Description: PGP signature

Reply via email to