On 10.07.23 04:40, Simon Glass wrote:
> This series converts the mkimage entry type to be a section, i.e. based on
> the entry_Section class. This makes it more consistent in its behaviour,
> e.g. allowing symbol writing and expanded entries.
>
> A simple templating feature is also introduced, to
Add support for writing symbols and determining the assumed position of
binaries inside a mkimage image. This is useful as an example for other
entry types which might want to do the same thing.
Signed-off-by: Simon Glass
---
Changes in v3:
- Add new patch to support writing symbols inside a
Allow templates to be used inside a section, not just in the top-level
/binman node.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/control.py| 5 ++-
tools/binman/ftest.py | 8
tools/binman/test/289_template_section.dts | 52
Add this as a separate test case.
Signed-off-by: Simon Glass
---
Changes in v3:
- Add new test case for templating in a FIT
tools/binman/ftest.py | 7 +
tools/binman/test/288_template_fit.dts | 37 ++
2 files changed, 44 insertions(+)
create mode
Allow a template to appear in the top level description when using
multiple images.
Signed-off-by: Simon Glass
---
Changes in v3:
- Drop duplicate dts-v1 header
tools/binman/control.py | 5 +++--
tools/binman/ftest.py| 12 +++
Collections can used to collect the contents of other entries into a
single entry, but they result in a single entry, with the original entries
'left behind' in their old place.
It is useful to be able to specific a set of entries ones and have it used
in multiple images, or parts of an image.
Provide a way to specify a phandle list of nodes which are to be inserted
into an existing node.
Signed-off-by: Simon Glass
---
Changes in v3:
- Adjust to use the new example file
tools/dtoc/fdt.py | 19 +++
tools/dtoc/test/dtoc_test_copy.dts | 13
This permits implementation of a simple templating system, where a node
can be reused as a base for others.
For now this adds new subnodes after any existing ones.
Signed-off-by: Simon Glass
---
Changes in v3:
- Add a new devicetree file especially for node copying
- Correct logic for merging
Fix the check for the __bss_size symbol, since it may be 0. Unfortunately
there was no test coverage for this.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/elf_test.py | 5 +
tools/binman/etype/u_boot_spl_bss_pad.py | 2 +-
This is not needed since the linker script sets it up. Drop the variable
to avoid confusion.
Fix the prototype for main() while we are here.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/test/bss_data.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
From: Marek Vasut
This is needed to handle mkimage with inner section located itself in a
section.
Signed-off-by: Marek Vasut
Use BuildSectionData() instead of ObtainContents(), add tests and a few
other minor fixes:
Signed-off-by: Simon Glass
---
Changes in v3:
- Fix up some tests which now
Sometimes multiple boards are built with binman and it is useful to
specify a different FDT list for each. At present this is not possible
without providing multiple values of the of-list entryarg (which is not
supported in the U-Boot build system).
Allow a fit,fdt-list-val string-list property
Update the LookupAndWriteSymbols() function to return the number of
symbols written. Also add some logging for when debugging is not
enabled.
Signed-off-by: Simon Glass
---
Changes in v3:
- Add new patch for elf to return number of written symbols
tools/binman/elf.py | 13 +++--
This area of binman can be a bit confusing. Add some more comments to
help.
Signed-off-by: Simon Glass
---
Changes in v3:
- Add new patch with more detail on how ObtainContents() works
tools/binman/entry.py | 3 +++
tools/binman/etype/section.py | 32 +++-
These boards use SPL in a mkimage entry and apparently access the symbol
containing the image position of U-Boot, but put U-Boot in another
image. This means that binman is unable to fill in the symbol correctly
in the SPL binary.
This doesn't matter at present since mkimage doesn't support
Some boards don't use symbol writing but do access the symbols in SPL.
Provide an option to work around this.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/binman.rst | 7 ++
tools/binman/entry.py | 4 +++-
Some section types don't have a simple _entries list. Use the GetEntries()
method in GetEntryContents() and other places to handle this.
This makes the behaviour more consistent.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/etype/section.py | 18 +-
1
Move this to the ReadEntries() function where it belongs.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/etype/mkimage.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/binman/etype/mkimage.py b/tools/binman/etype/mkimage.py
index
Add a pragma to deal with the code-coverage gap which drops binman down to
90% coverage.
Fixes: de65b122a25 (tools: Fall back to importlib_resources on Python 3.6)
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/control.py | 2 +-
1 file changed, 1 insertion(+), 1
This should be set up in the init function, to avoid a warning about a
property not set up there. Fix it.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/etype/section.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/binman/etype/section.py
This series converts the mkimage entry type to be a section, i.e. based on
the entry_Section class. This makes it more consistent in its behaviour,
e.g. allowing symbol writing and expanded entries.
A simple templating feature is also introduced, to reduce duplication
when a set of entries must
On Mon, Jul 10, 2023 at 11:13:12AM +0900, Masahisa Kojima wrote:
> On Fri, 7 Jul 2023 at 18:12, AKASHI Takahiro
> wrote:
> >
> > On Fri, Jul 07, 2023 at 05:19:33PM +0900, Masahisa Kojima wrote:
> > > Hi Akashi-san,
> > >
> > > On Fri, 7 Jul 2023 at 16:16, AKASHI Takahiro
> > > wrote:
> > > >
>
On Fri, 7 Jul 2023 at 18:12, AKASHI Takahiro wrote:
>
> On Fri, Jul 07, 2023 at 05:19:33PM +0900, Masahisa Kojima wrote:
> > Hi Akashi-san,
> >
> > On Fri, 7 Jul 2023 at 16:16, AKASHI Takahiro
> > wrote:
> > >
> > > On Fri, Jul 07, 2023 at 08:29:12AM +0200, Heinrich Schuchardt wrote:
> > > > On
On Fri, Jul 07, 2023 at 11:35:49AM -0600, Simon Glass wrote:
> Hi,
>
> On Tue, 4 Jul 2023 at 03:35, AKASHI Takahiro
> wrote:
> >
> > Hi Simon,
> >
> > On Mon, Jul 03, 2023 at 02:30:57PM +0100, Simon Glass wrote:
> > > Hi,
> > >
> > > On Mon, 3 Jul 2023 at 01:57, AKASHI Takahiro
> > > wrote:
>
Hi Tom,
Please pull fsl-qoriq-2023-7-6 for next
-
Enable DM Serial for ls1043ardb and ls1046ardb/afrwy
Fixed secure boot on LS-CH2 platforms
-
On Fri, Jul 07, 2023 at 11:35:52AM -0600, Simon Glass wrote:
> Hi,
>
> On Tue, 4 Jul 2023 at 02:26, AKASHI Takahiro
> wrote:
> >
> > On Mon, Jul 03, 2023 at 02:30:54PM +0100, Simon Glass wrote:
> > > Hi,
> > >
> > > On Mon, 3 Jul 2023 at 01:55, AKASHI Takahiro
> > > wrote:
> > > >
> > > > On
Hi,
I'm trying to port U-Boot to a new board (Samsung JACKPOTLTE, ARMv8,
Exynos7885) but when CONFIG_ARCH_FIXUP_FDT_MEMORY is enabled, the bootm
command leads to an unaligned memory access, which results in a
synchronous abort.
After a long debugging session, I concluded that fdt_pack_reg in
Using `default y` will not select BMP when CMD_BMP has been enabled, if
it was already configured.
By using `select`, if `CMD_BMP` is turned on, it will force the presence
of `BMP`.
Fixes: 072b0e16c482114d242580dd7a3197db5966705f
Signed-off-by: Samuel Dionne-Riel
---
cmd/Kconfig| 1 +
The sar-reg0 alias was left over from an earlier iteration of the
patches adding support for this board. Remove the unused alias.
Fixes: 6cc8b5db40 ("arm: mvebu: Add RD-AC5X board")
Signed-off-by: Chris Packham
---
arch/arm/dts/ac5-98dx35xx-rd.dts | 1 -
1 file changed, 1 deletion(-)
diff
The x240 and SE240 are a series of L2+ switches from Allied Telesis.
There are a number of them in the range but as far as U-Boot is
concerned all the CPU block components are the same so there's only one
board defined.
Signed-off-by: Chris Packham
---
Notes:
Changes in v2:
- drop
The CN9130 SoC (an ARMADA 8K type) has both a NAND Flash Controller and
a generic local bus controller (Device Bus Controller) that share common
pins.
With a board design that incorporates both a NAND flash and uses
the Device Bus (in our case for an SRAM) accessing the Device Bus device
fails
The NAND flash controller (NFC) on the AC5/AC5X SoC is the same as
the NFC used on other Marvell SoCs. It does have the additional
restriction of only supporting SDR timing modes up to 3.
Signed-off-by: Chris Packham
---
drivers/mtd/nand/raw/pxa3xx_nand.c | 17 ++---
1 file changed,
The NF_CLK for the AC5 SoC runs at 400MHz. There's no strapping
or gating require so just add a mvebu_get_nand_clock() that
returns this value.
Signed-off-by: Chris Packham
---
arch/arm/mach-mvebu/alleycat5/soc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
The AC5/AC5X SoC has a NAND flash controller. Add this to the
SoC device tree.
Signed-off-by: Chris Packham
---
arch/arm/dts/ac5-98dx25xx.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/dts/ac5-98dx25xx.dtsi b/arch/arm/dts/ac5-98dx25xx.dtsi
index
This series adds support for the NAND flash controller on the AC5X SoC
and adds support for the Allied Telesis x240 board.
I've also included 2 unrelated changes. "arm: mvebu: Remove unused alias
from RC AC5X dts" removes an unused alias from the dts. This was in the
neighborhood of the x240 so I
On Sun, Jul 09, 2023 at 04:32:22PM +, Anne Macedo wrote:
> On Tue, Jul 04, 2023 at 11:22:29PM +, Anne Macedo wrote:
> > Hey!
> >
> > I'm trying to bake Linux images for the Orange Pi One Plus using Yocto.
> > Everything works fine, except for Ethernet.
> >
> > On the u-boot prompt:
> >
On Tue, Jul 04, 2023 at 11:22:29PM +, Anne Macedo wrote:
> Hey!
>
> I'm trying to bake Linux images for the Orange Pi One Plus using Yocto.
> Everything works fine, except for Ethernet.
>
> On the u-boot prompt:
>
> => dhcp
> No ethernet found.
>
> After adding:
>
> CONFIG_SPL_SPI_SUNXI=y
On Sun, Jul 09, 2023 at 12:38:46PM +0200, Heinrich Schuchardt wrote:
> Dear Tom,
>
> The following changes since commit 0beb649053b86b2cfd5cf55a0fc68bc2fe91a430:
>
> MAINTAINERS: correct at91 tree link (2023-07-07 11:37:09 -0400)
>
> are available in the Git repository at:
>
>
Hi Heinrich,
> -Original Message-
> From: Heinrich Schuchardt
> Sent: Sunday, July 9, 2023 7:09 PM
> To: Soma, Ashok Reddy ; u-
> b...@lists.denx.de
> Cc: s...@chromium.org; ilias.apalodi...@linaro.org; rfried@gmail.com;
> seanedm...@microsoft.com; tob...@waldekranz.com;
Am 9. Juli 2023 15:33:17 MESZ schrieb Sughosh Ganu :
>The EFI capsule authentication logic in u-boot expects the public key
>in the form of an EFI Signature List(ESL) to be provided as part of
>the platform's dtb. Currently, the embedding of the ESL file into the
>dtb needs to be done manually.
Am 9. Juli 2023 15:09:57 MESZ schrieb Ashok Reddy Soma
:
>When CONFIG_CMD_USB and CONFIG_USB are disabled some compilation errors
>are seen as below.
Thanks for your patch.
Currently we have no documentation for the thordown command. We should create
a man page in /docs/usage/cmd/.
Do you
The EFI capsule files can now be generated as part of u-boot
build. This is done through binman. Add capsule entry nodes in the
u-boot.dtsi for the sandbox architecture for generating the
capsules. Remove the corresponding generation of capsules from the
capsule update conftest file.
The capsules
Support has been added to the mkeficapsule tool to generate capsules
by parsing the capsule parameters through a config file. Add a config
file for generating capsules. These capsules will be used for testing
the capsule update feature on sandbox platform.
Enable generation of capsules through
The embedding of the public key EFI Signature List(ESL) file into the
platform's DTB is now done at the time of u-boot build. Remove this
logic from the capsule update test' configuration.
Include the public key for the sandbox and sandbox_flattree variant
as part of the build.
Signed-off-by:
Support has being added through earlier commits to build capsules and
embed the public key needed for capsule authentication as part of
u-boot build.
>From the testing point-of-view, this means the input files needed for
the above have to be setup before invoking the build. Set this up in
the
Support has being added through earlier commits to build capsules
and embed the public key needed for capsule authentication as part of
u-boot build.
>From the testing point-of-view, this means the input files needed for
generating the above have to be setup before invoking the build. Set
this up
Add support in binman for generating capsules. The capsule parameters
can be specified either through a config file or through the capsule
binman entry.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* New patch which generates capsules through binman replacing the
earlier make target.
The UEFI capsule can be generated either through command-line
parameters, or, by specifying those in a config file. Add
documentation to describe the format of the config file.
Signed-off-by: Sughosh Ganu
---
Changes since V2: None
doc/develop/uefi/uefi.rst | 64
Add support for specifying the parameters needed for capsule
generation through a config file, instead of passing them through
command-line. Parameters for more than a single capsule file can be
specified, resulting in generation of multiple capsules through a
single invocation of the command.
The EFI capsule authentication logic in u-boot expects the public key
in the form of an EFI Signature List(ESL) to be provided as part of
the platform's dtb. Currently, the embedding of the ESL file into the
dtb needs to be done manually.
Add a signature node in the u-boot dtsi file and include
Update the document to specify how the EFI Signature List(ESL) file
can be embedded into the platform's dtb as part of the u-boot build.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* Highlight the need to use the u-boot.dtsi file for embedding the
public key ESL into the DTB.
Add a newline at the end of the dts, without which the build fails
when including the u-boot.dtsi file.
Signed-off-by: Sughosh Ganu
---
Changes since V2:
* New patch
arch/arm/dts/nuvoton-npcm845-evb.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patchset aims to bring two capsule related tasks under the u-boot
build flow.
One is the embedding of the public key into the platform's dtb. The
public key is in the form of an EFI Signature List(ESL) file and is
used for capsule authentication. This is being achieved by adding the
When CONFIG_CMD_USB and CONFIG_USB are disabled some compilation errors
are seen as below.
cmd/thordown.o: in function `usb_gadget_initialize':
include/linux/usb/gadget.h:981: undefined reference to `board_usb_init'
cmd/thordown.o: in function `do_thor_down':
cmd/thordown.c:68: undefined
When CONFIG_CMD_USB and CONFIG_USB are disabled, still some compilation
errors are seen as below.
In file included from include/configs/xilinx_zynqmp.h:173,
from include/config.h:3,
from include/common.h:16,
from env/common.c:10:
When USB device driver CONFIG_USB and CONFIG_CMD_USB are disabled, some
compilation issues are seen. Also CMD_THOR_DOWNLOAD should depend on
CONFIG_CMD_USB. Add dependencies to resolve those issues and compile
properly. Also remove unused config CONFIG_ZYNQMP_USB.
Ashok Reddy Soma (2):
cmd:
On Saturday 08 July 2023 11:28:34 Tom Rini wrote:
> On Sat, Jul 08, 2023 at 10:30:47AM +0200, Pali Rohár wrote:
> > On Friday 07 July 2023 19:43:34 Tom Rini wrote:
> > > On Sat, Jul 08, 2023 at 12:54:38AM +0200, Pali Rohár wrote:
> > >
> > > > To make eMMC partition choosing in
On Fri, Jul 7, 2023 at 8:48 PM Sahaj Sarup wrote:
> For now the fix seems to be `clocks = <_blk_ctrl 0>;`
Please submit the fix to Linux.
> this gets pcie working under linux but not under u-boot, i'm guessing pcie
> for imx8 is not yet implemented?
That's correct.
After Linux commit ff61f0791ce9, x86 documentation was moved to
arch/x86 and the link in bootparam.h was broken.
Signed-off-by: Paul Barker
---
arch/x86/include/asm/bootparam.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/bootparam.h
On 09/07/2023 02:47, Heinrich Schuchardt wrote:
On 7/7/23 17:41, Tom Rini wrote:
On Fri, Jul 07, 2023 at 07:51:42AM +0100, Paul Barker wrote:
After Linux commit ff61f0791ce9, x86 documentation was moved to
arch/x86 and the link in bootparam.h was broken.
Signed-off-by: Paul Barker
---
Dear Tom,
The following changes since commit 0beb649053b86b2cfd5cf55a0fc68bc2fe91a430:
MAINTAINERS: correct at91 tree link (2023-07-07 11:37:09 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-efi.git
tags/efi-2023-07-rc7
for you to fetch
On 7/9/23 11:44, Paul Barker wrote:
After Linux commit ff61f0791ce9, x86 documentation was moved to
arch/x86 and the link in bootparam.h was broken.
Signed-off-by: Paul Barker
Reviewed-by: Heinrich Schuchardt
---
arch/x86/include/asm/bootparam.h | 2 +-
1 file changed, 1 insertion(+),
On 6/26/23 12:04, Ilias Apalodimas wrote:
The EFI doesn't allow removal of handles, unless all hosted protocols
are cleanly removed. Our efi_delete_handle() is a bit intrusive.
Although it does try to delete protocols before removing a handle,
it doesn't care if that fails. Instead it only
On 6/20/23 08:19, Ilias Apalodimas wrote:
efi_uninstall_protocol() calls efi_disconnect_all_drivers() but never
checks the return value. Instead it tries to identify protocols that
are still open after closing the ones that were opened with
EFI_OPEN_PROTOCOL_BY_HANDLE_PROTOCOL,
On 6/20/23 08:19, Ilias Apalodimas wrote:
efi_disconnect_controller() doesn't reconnect drivers in case of
failure. Reconnect the disconnected drivers properly
Signed-off-by: Ilias Apalodimas
Reviewed-by: Heinrich Schuchardt
On 6/19/23 23:23, Raymond Mao wrote:
Changes for complying to EFI spec §3.5.1.1
'Removable Media Boot Behavior'.
Boot variables can be automatically generated during a removable
media is probed. At the same time, unused boot variables will be
detected and removed.
Please note that currently the
On 6/16/23 10:28, Stefan Herbrechtsmeier wrote:
From: Malte Schmidt
The data type of item_offset_list shall be UINT64 according to the UEFI [1]
specifications.
In include/efi_api.h the correct data type is used. The bug was probably
never noticed because of little endianness.
[1]
67 matches
Mail list logo
