Am 5. April 2023 23:56:59 MESZ schrieb Mark Kettenis :
>> Date: Wed, 5 Apr 2023 10:47:59 -0400
>> From: Tom Rini
>>
>> On Wed, Apr 05, 2023 at 05:28:07PM +1200, Simon Glass wrote:
>> > Hi Tom,
>> >
>> > On Tue, 4 Apr 2023, 02:17 Tom Rini, wrote:
>> >
>> > > On Mon, Apr 03, 2023 at
Hi,
On Fri, Mar 31, 2023 at 12:09 PM Sinthu Raja
wrote:
>
> From: Sinthu Raja
>
> This resyncs the dts file of j721e-sk with the currently in-tree K3
> platforms. Of note are that the main-navss/mcu-navss nodes were renamed
> to main_navss / mcu_navss and so the u-boot.dtsi file needed to be
>
Sometimes when doing tests on real hardware we sometimes run in to the
case where some of these mounts haven't been fully flushed. Using the
--lazy option with umount will allow us to continue while letting the OS
handle flushing the data out still.
Signed-off-by: Tom Rini
---
Hi Tom,
Please pull fsl-qoriq-2023-4-6
---
convert NXP LS1028A RDB and QDS to DM_SERIAL
enable DM_SERIAL for ls1088a
sync serial nodes with linux for lx2160a/ls1088a
---
CI:
> From: Bin Meng
> Sent: Monday, April 03, 2023 11:38 AM
> To: Leo Yu-Chi Liang(梁育齊) ; Rick Jian-Zhi Chen(陳建志)
>
> Cc: u-boot@lists.denx.de
> Subject: [PATCH] riscv: Correct a comment in io.h
>
> Replace NDS32 with RISC-V in the comments.
>
> Signed-off-by: Bin Meng
> ---
>
>
On Wed, Apr 5, 2023 at 10:21 PM Fabio Estevam wrote:
>
> Hi Peng and Ye Li,
>
> The following SDHC error is seen when running top of tree U-Boot on an
> imx7d-sabresd board:
>
> U-Boot 2023.04-00652-g487e42f7bc5e (Apr 05 2023 - 22:14:21 -0300)
>
> CPU: Freescale i.MX7D rev1.0 1000 MHz (running
Hi Peng and Ye Li,
The following SDHC error is seen when running top of tree U-Boot on an
imx7d-sabresd board:
U-Boot 2023.04-00652-g487e42f7bc5e (Apr 05 2023 - 22:14:21 -0300)
CPU: Freescale i.MX7D rev1.0 1000 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 35C
On 4/6/23 01:48, Tom Rini wrote:
When building with clang, it notes that sdinfo may be unused
uninitialized in some cases. This appears to be true from reading the
code, and we can simply set the variable to zero to start with and be as
correct as before.
Signed-off-by: Tom Rini
---
I'm
Hi Vincent,
On Thu, Apr 6, 2023, at 1:04 AM, Vincent Stehlé wrote:
> Hi,
>
> I am hitting an issue with the new bootflow when booting with UEFI from a
> virtio device on Qemu Arm.
>
> It seems the device number computation in efiload_read_file() does not work
> in the general virtio case, where
Synchronize the i.MX8M Mini Toradex Verdin based Menlo board config
with i.MX8M Mini Toradex Verdin carrier board. This enables DM MDIO,
eMMC HS modes, TMU for thermal monitoring, LTO and multiple commands
(hexdump, pmic, read, time).
Signed-off-by: Marek Vasut
---
Cc: Marek Vasut
Cc: Olaf
When building with clang we see this warning:
field guid within 'struct efi_hii_keyboard_layout' is less aligned than
'efi_guid_t' and is usually due to 'struct efi_hii_keyboard_layout' being
packed, which can lead to unaligned accesses [-Wunaligned-access]
Which is correct and true as EFI
At this point, clang can be used on both 32bit and 64bit targets without
issue.
Signed-off-by: Tom Rini
---
doc/build/clang.rst | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/doc/build/clang.rst b/doc/build/clang.rst
index 1d35616eb5ef..222487032ce0 100644
When building with clang, it notes that sdinfo may be unused
uninitialized in some cases. This appears to be true from reading the
code, and we can simply set the variable to zero to start with and be as
correct as before.
Signed-off-by: Tom Rini
---
I'm honestly not sure why gcc isn't
When building with clang we get a warning that rdaddr could be
uninitialized in one case. While this cannot functionally happen, we can
easily silence the warning.
Signed-off-by: Tom Rini
---
boot/image-board.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Toolchains which do not directly support using "isb" and "dsb" directly
are no longer functionally supported in U-Boot. Furthermore, clang has
for a long time warned about using the alternate form that we were.
Update the code.
Signed-off-by: Tom Rini
---
arch/arm/cpu/armv7/start.S | 8
When building for ARM64, we need to pass -ffixed-x18 and otherwise pass
-ffixed-r9. Rather than having this logic in two places, we can do this
once in arch/arm/config.mk. Further, while gcc will ignore being passed
both -ffixed-r9 and -ffixed-x18 and simply use -ffixed-x18, clang will
note that
In the case of using clang to build, and having not already enabled the
private libgcc, do not look for it, as it will not be found nor
required.
Signed-off-by: Tom Rini
---
Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Makefile b/Makefile
index 97a84ae3131e..b5063446ff85
When we invoke $(CPP) to make u-boot.lds we have LDPPFLAGS available to
set other required flags here. As this file is for the target and not
the host, we must ensure that CPP knows what the target architecture is.
For this, pass in $(CLANG_TARGET).
Signed-off-by: Tom Rini
---
Makefile | 1 +
1
Today, only gcc has __builtin_aarch64_crc32b (clang-16 does not, for
example). Make this option depend on CC_IS_GCC.
Signed-off-by: Tom Rini
---
arch/arm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index
Hey all,
I decided to take a look again at what's needed to build and boot ARM
platforms when building with clang. The good news is that this generally
works now. Some size-constrained platforms don't build right now but I
was able to test a reasonable part of my lab. This series also depends
on:
On Thu, 16 Feb 2023 16:33:46 +0100, Tobias Waldekranz wrote:
> Block maps are a way of looking at various sources of data through the
> lens of a regular block device. It lets you treat devices that are not
> block devices, like RAM, as if they were. It also lets you export a
> slice of an
Enable the CONFIG_TI_SECURE_DEVICE by default
Non-HS devices will continue to boot due to runtime device type detection.
TI's security enforcing SoCs will authenticate each binary it loads by
comparing it's signature with keys etched into the SoC during the boot
up process. The am62x family of
> From: Simon Glass
> Date: Thu, 6 Apr 2023 06:38:19 +1200
>
> Hi Neil,
>
> On Mon, 3 Apr 2023 at 19:31, Neil Armstrong wrote:
> >
> > Hi Simon !
> >
> > On 01/04/2023 20:54, Simon Glass wrote:
> > > This shows how binman can be used to replace the long and complicated
> > > instructions with
> Date: Wed, 5 Apr 2023 10:47:59 -0400
> From: Tom Rini
>
> On Wed, Apr 05, 2023 at 05:28:07PM +1200, Simon Glass wrote:
> > Hi Tom,
> >
> > On Tue, 4 Apr 2023, 02:17 Tom Rini, wrote:
> >
> > > On Mon, Apr 03, 2023 at 12:56:49PM +0300, Ilias Apalodimas wrote:
> > > > On Sat, Apr 01, 2023 at
Some SoCs of the H616 family use a die variant, that puts some CPU power
and reset control registers at a different address. There are examples
of two instances of the same board, using different die revisions of the
otherwise same H313 SoC. We need to write to a register in that block
*very*
On 4/5/23 3:09 PM, Christian Gmeiner wrote:
Hi
This matches how it was done for pre-K3 TI platforms and it allows
us to move the forward declaration out of sys_proto.h.
It also removes the need for K3_BOARD_DETECT as one is free to simply
override the weak function in their board files as
Hi
>
> This matches how it was done for pre-K3 TI platforms and it allows
> us to move the forward declaration out of sys_proto.h.
>
> It also removes the need for K3_BOARD_DETECT as one is free to simply
> override the weak function in their board files as needed.
>
> Signed-off-by: Andrew Davis
Hi
On Wed, Apr 5, 2023 at 4:38 PM Bin Meng wrote:
>
> octeontx_bch_devices and octeontx_pci_nand_deferred_devices are only
> referenced in the files where they are defined. Make them static.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/mtd/nand/raw/octeontx_bch.c | 2 +-
>
On Wed, 5 Apr 2023 at 06:45, Andrew Davis wrote:
>
> The header binman_sym.h depends on ulong typedef but does not include
> types.h. This means the header must be included after including types.h
> or a header that includes it.
>
> We could include types.h but instead let's just switch from
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> Compile video driver at SPL using CONFIG_SPL_VIDEO.
>
> Signed-off-by: Nikhil M Jain
> Reviewed-by: Devarsh Thakkar
> ---
> V6:
> - Add Reviewed-by tag
> - Commit message updated.
>
> V5:
> - Add rule to build video at SPL using
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> To enable splash screen at SPL, need to compile cmd/bmp.c which also
> includes bmp commands, since SPL doesn't use commands split bmp.c into
> common/bmp.c which includes all bmp functions and cmd/bmp.c which only
> contains bmp commands.
>
>
Hi Vincent,
On Thu, 6 Apr 2023 at 03:05, Vincent Stehlé wrote:
>
> Hi,
>
> I am hitting an issue with the new bootflow when booting with UEFI from a
> virtio device on Qemu Arm.
>
> It seems the device number computation in efiload_read_file() does not work
> in the general virtio case, where it
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> Add rule to compile bmp.c at SPL and u-boot proper when CONFIG_SPL_BMP
> and CONFIG_BMP are defined.
>
> Signed-off-by: Nikhil M Jain
> Reviewed-by: Devarsh Thakkar
> ---
> V6:
> - Add Reviewed-by tag.
>
> V5:
> - Remove obj-y+= read.o.
>
>
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> To support video driver at SPL use CONFIG_IS_ENABLED and CONFIG_VAL,
> which checks for stage specific configs and thus enables video support
> at respective stage.
>
> Signed-off-by: Nikhil M Jain
> Reviewed-by: Devarsh Thakkar
> ---
> V6:
Hi Christian,
On Mon, 3 Apr 2023 at 20:10, Christian Hewitt
wrote:
>
> > On 2 Apr 2023, at 6:41 am, Simon Glass wrote:
> >
> > Hi Mark,
> >
> > On Sun, 2 Apr 2023 at 09:28, Mark Kettenis wrote:
> > >
> > > > From: Simon Glass
> > > > Date: Sun, 2 Apr 2023 06:54:57 +1200
> > > >
> > > > The
Hi Neil,
On Mon, 3 Apr 2023 at 19:31, Neil Armstrong wrote:
>
> Hi Simon !
>
> On 01/04/2023 20:54, Simon Glass wrote:
> > This shows how binman can be used to replace the long and complicated
> > instructions with an automated build. It is still complicated to read
> > but users don't have to
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> To enable splash screen and loading bmp from boot media, add rules to
> compile splash.c and splash_source.c at SPL stage only when
> CONFIG_SPL_SPLASH_SCREEN and CONFIG_SPL_SPLASH_SOURCE are defined.
>
> Signed-off-by: Nikhil M Jain
>
On Tue, 4 Apr 2023 at 01:50, Stefan Herbrechtsmeier
wrote:
>
> From: Stefan Herbrechtsmeier
>
> Add a test for the hush shell variable assignment and clear.
>
> Signed-off-by: Stefan Herbrechtsmeier
> ---
>
> (no changes since v1)
>
> test/py/tests/test_hush_if_test.py | 13 +
> 1
On Tue, 4 Apr 2023 at 06:47, Heinrich Schuchardt
wrote:
>
> Function fdt_simplefb_enable_existing_node() should be static as it is not
> used outside common/fdt_simplefb.c.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> common/fdt_simplefb.c | 8 +++-
> include/fdt_simplefb.h | 1 -
> 2
Hi Neha,
On Wed, 5 Apr 2023 at 00:13, Neha Malcom Francis wrote:
>
> The ti-board-config entry loads and validates a given YAML config file
> against a given schema, and generates the board config binary. K3
> devices require these generated binaries to be packed into the final
> system firmware
On Tue, 4 Apr 2023 at 06:28, Heinrich Schuchardt
wrote:
>
> The main configuration menu should not contain detail settings.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> test/Kconfig | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
Reviewed-by: Simon Glass
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> To support splash screen at both u-boot proper and SPL use
> CONFIG_IS_ENABLED and CONFIG_VAL to check for video related Kconfigs at
> respective stages.
>
> Replace CONFIG_CMD_BMP with CONFIG_BMP to enable splash_display function
> at u-boot
On Mon, 3 Apr 2023 at 22:04, Heinrich Schuchardt
wrote:
>
> * Fix dependencies
> * Provide labels that are easier to grasp.
> * Fix typo %s/whgch/which/
> * Fix type %s/Is/is/
>
> Fixes: 29784d62eded ("test: Add some tests for kconfig.h")
> Signed-off-by: Heinrich Schuchardt
> ---
>
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> Add Kconfigs which enable the video driver and splash screen at SPL
> stage only and not at u-boot proper. The existing Kconfigs from u-boot
> proper were not used to make SPL splash screen independent to them.
>
> Signed-off-by: Nikhil M Jain
kHi Neha,
On Wed, 5 Apr 2023 at 00:13, Neha Malcom Francis wrote:
>
> The ti-secure entry contains certificate for binaries that will be
> loaded or booted by system firmware whereas the ti-secure-rom entry
> contains certificate for binaries that will be booted by ROM. Support
> for both these
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> To include video related global data variables and splash functions at
> SPL and u-boot proper, use CONFIG_IS_ENABLED.
>
> Replace CONFIG_CMD_BMP with CONFIG_BMP to enable splash_display function
> at u-boot proper and SPL.
>
> Signed-off-by:
On Wed, 5 Apr 2023 at 01:06, Nikhil M Jain wrote:
>
> To enable video driver at SPL, need to compile video-uclass,
> vidconsole-uclass, backlight-uclass, panel-uclass, simple-panel, add
> rules to compile them at SPL and u-boot proper. To support
> splash_display at SPL, need to compile
On Tue, 4 Apr 2023 at 01:50, Stefan Herbrechtsmeier
wrote:
>
> From: Stefan Herbrechtsmeier
>
> The u-boot hush shell doesn’t support the unset command to clear a
> variable and therefore an empty value ("c=") should be a valid value
> for the set_local_var function to clear the variable. This
Hi,
[please try to avoid top posting]
On Wed, 5 Apr 2023 at 19:20, wrote:
>
> Hi Simon,
>
> even with CONFIG_BOOTSTAGE disabled I still get this data abort:
>
> Starting kernel ...
>
> data abort
> pc : [] lr : [<>]
> reloc pc : []lr : []
> sp : fbbefafc ip :
On Wed, 5 Apr 2023 at 21:27, Heinrich Schuchardt
wrote:
>
> os.h is only used by the sandbox.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Simon Glass
On Wed, 5 Apr 2023 at 21:34, Heinrich Schuchardt
wrote:
>
> Given a file ../img of size 4294967296 with GPT partition table and
> partitions:
>
> => host bind 0 ../img
> => part list host 0
> Disk host-0.blk not ready
>
> The cause is os_filesize() returning int. File sizes must use off_t.
>
>
On Thu, 6 Apr 2023 at 02:38, Bin Meng wrote:
>
> aliases_lookup is only referenced in of_access.c
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/core/of_access.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass
Hi Bin,
On Sun, 2 Apr 2023 at 15:33, Bin Meng wrote:
>
> Hi Simon,
>
> On Sat, Apr 1, 2023 at 2:31 PM Simon Glass wrote:
> >
> > Hi Bin,
> >
> > On Fri, 31 Mar 2023 at 19:22, Bin Meng wrote:
> > >
> > > On Fri, Mar 31, 2023 at 5:36 AM Simon Glass wrote:
> > > >
> > > > Hi,
> > > >
> > > > I
This matches AM64 and J721e and removes the need to forward
declare k3_spl_init(), k3_mem_init(), and check_rom_loaded_sysfw()
in sys_proto.h.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/include/mach/sys_proto.h | 3 --
arch/arm/mach-k3/j721s2_init.c| 64
This header file is now empty, remove it.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/am642_init.c | 2 --
arch/arm/mach-k3/am654_init.c | 1 -
arch/arm/mach-k3/common.c | 1 -
arch/arm/mach-k3/include/mach/sys_proto.h | 10 --
This function is the same for each device when it needs to shutdown
the R5 core. Move this to the common section and move the remaining
device specific ID list to the device hardware include.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/am642_init.c | 51 -
This matches how it was done for pre-K3 TI platforms and it allows
us to move the forward declaration out of sys_proto.h.
It also removes the need for K3_BOARD_DETECT as one is free to simply
override the weak function in their board files as needed.
Signed-off-by: Andrew Davis
---
These probably should be in some system wide header given their use.
Until then move them out of K3 sys_proto.h so we can finish cleaning
that header out.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/include/mach/sys_proto.h | 4
drivers/ram/k3-am654-ddrss.c | 4
2
This function is not used currently; remove it.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/common.c | 19 ---
arch/arm/mach-k3/include/mach/sys_proto.h | 1 -
2 files changed, 20 deletions(-)
diff --git a/arch/arm/mach-k3/common.c
The TARGET_x_R5_EVM check is already enough to limit these defines to
only the correct builds. Remove the extra outer check.
Signed-off-by: Andrew Davis
---
board/ti/j721e/j721e.env | 2 --
board/ti/j721s2/j721s2.env | 2 --
2 files changed, 4 deletions(-)
diff --git
The K3 JTAG and SoC ID information is already stored in the K3 arch
hardware file, include that and use its definitions here.
Signed-off-by: Andrew Davis
---
drivers/soc/Kconfig | 2 +-
drivers/soc/soc_ti_k3.c | 30 +-
2 files changed, 10 insertions(+), 22
This belongs in the J721e specific file as it is the only place
this is used. Any board level users should use the SOC driver.
While here, move the J721e and J7200 SoC IDs out of sys_proto.h
and into hardware.h. Add the rest of the SoC IDs for completeness
and later use.
Signed-off-by: Andrew
The J7200 EVM will not include this file, this J7200 checks look
to be a copy/paste errora from j721e_evm.h, which J7200 *can* include.
Signed-off-by: Andrew Davis
---
include/configs/j721s2_evm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/j721s2_evm.h
Hello all,
Some minor cleanups with end patch removing sys_proto.h.
Why? Becouse I don't like headers of "miscellaneous".
Thanks,
Andrew
Changes from v1:
- Added reviewed by tag
- Rebased on latest
Andrew Davis (12):
arm: mach-k3: Move MSMC fixup to SoC level
arm: mach-k3: Move J721e SoC
This header is only used locally by K3 init files, no need to have it
up with the global mach includes. Move into local includes.
Signed-off-by: Andrew Davis
---
arch/arm/mach-k3/am625_init.c | 2 +-
arch/arm/mach-k3/am62a7_init.c | 2 +-
The MSMC fixup is something we do based on SoC, not based on the board.
So this fixup does not belong in the board files. Move this to the
mach-k3 common file so that it does not have to be done in each board
that uses these SoCs.
We use ft_system_setup() here instead of ft_board_setup() since it
Hi,
I am hitting an issue with the new bootflow when booting with UEFI from a
virtio device on Qemu Arm.
It seems the device number computation in efiload_read_file() does not work
in the general virtio case, where it will pick the virtio device number
instead of the block device index. On Qemu
On Wed, Apr 05, 2023 at 09:50:08AM +0200, Christian Gmeiner wrote:
> Hi all
>
> >
> > Preparation for per driver instance allocated data structures.
> >
> > Signed-off-by: Christian Gmeiner
>
> gentle ping - what can I do better to get some feedback, RBs, etc
> faster? This experience is
>
On Wed, Apr 05, 2023 at 05:28:07PM +1200, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 4 Apr 2023, 02:17 Tom Rini, wrote:
>
> > On Mon, Apr 03, 2023 at 12:56:49PM +0300, Ilias Apalodimas wrote:
> > > On Sat, Apr 01, 2023 at 07:31:49PM +1300, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On
yaffsfs_deviceList is only referenced in yaffsfs.c
Signed-off-by: Bin Meng
---
fs/yaffs2/yaffsfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/yaffs2/yaffsfs.c b/fs/yaffs2/yaffsfs.c
index 510faaeed1..d615f02d3f 100644
--- a/fs/yaffs2/yaffsfs.c
+++
octeontx_bch_devices and octeontx_pci_nand_deferred_devices are only
referenced in the files where they are defined. Make them static.
Signed-off-by: Bin Meng
---
drivers/mtd/nand/raw/octeontx_bch.c | 2 +-
drivers/mtd/nand/raw/octeontx_nand.c | 2 +-
2 files changed, 2 insertions(+), 2
aliases_lookup is only referenced in of_access.c
Signed-off-by: Bin Meng
---
drivers/core/of_access.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/core/of_access.c b/drivers/core/of_access.c
index 85f7da5a49..81a307992c 100644
--- a/drivers/core/of_access.c
+++
efi_runtime_mmio is only referenced in efi_boottime.c
Signed-off-by: Bin Meng
---
lib/efi_loader/efi_runtime.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_runtime.c b/lib/efi_loader/efi_runtime.c
index cee96bfc7f..bf54d6ad87 100644
---
efi_mem is only referenced in efi_memory.c
Signed-off-by: Bin Meng
---
lib/efi_loader/efi_memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_memory.c b/lib/efi_loader/efi_memory.c
index b7bee98f79..219b520a0d 100644
--- a/lib/efi_loader/efi_memory.c
efi_event_queue and efi_register_notify_events are only referenced
in efi_boottime.c
Signed-off-by: Bin Meng
---
include/efi_loader.h | 3 ---
lib/efi_loader/efi_boottime.c | 4 ++--
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/include/efi_loader.h
load_file() and load_file2() are only referenced in
efi_selftest_load_file.c
Signed-off-by: Bin Meng
---
lib/efi_selftest/efi_selftest_load_file.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/lib/efi_selftest/efi_selftest_load_file.c
record is only referenced in efi_selftest_exitbootservices.c
Signed-off-by: Bin Meng
---
lib/efi_selftest/efi_selftest_exitbootservices.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_selftest/efi_selftest_exitbootservices.c
On 4/2/23 5:44 AM, Christian Gmeiner wrote:
Hi Andrew
Am Do., 30. März 2023 um 22:30 Uhr schrieb Andrew Davis :
This matches how it was done for pre-K3 TI platforms and it allows
us to move the forward declaration out of sys_proto.h.
It also removes the need to check for TI_I2C_BOARD_DETECT
On Mon, 06 Feb 2023 00:50:02 +0100, Safae Ouajih wrote:
> * This is based on Roman Stratiienko's work to support boot image header
> version 3 and 4.
>
> * This supports the new boot image headers v3, v4 and bootconfig feature.
>
In the early days of the Allwinner A64 U-Boot support, we relied on a
vendor provided "boot0" binary to perform the DRAM initialisation. This
replaced the SPL, and required to equip the U-Boot (proper) binary with
a vendor specific header to be recognised as a valid boot0 payload.
Fortunately
To switch the ARMv8 Allwinner SoCs into the 64-bit AArch64 ISA, we need
to program the 64-bit start code address into an MMIO mapped register
that shadows the architectural RVBAR register.
This address is SoC specific, with just two versions out there so far.
Now a third address emerged, on a
On Wed, Apr 05, 2023 at 08:15:19PM +0800, Bin Meng wrote:
> efi_runtime_mmio is only referenced in efi_boottime.c
>
> Signed-off-by: Bin Meng
> ---
>
> lib/efi_loader/efi_runtime.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/efi_loader/efi_runtime.c
On Wed, Apr 05, 2023 at 08:15:18PM +0800, Bin Meng wrote:
> efi_mem is only referenced in efi_memory.c
>
> Signed-off-by: Bin Meng
> ---
>
> lib/efi_loader/efi_memory.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/efi_loader/efi_memory.c
On Wed, Apr 05, 2023 at 08:15:17PM +0800, Bin Meng wrote:
> efi_event_queue and efi_register_notify_events are only referenced
> in efi_boottime.c
>
> Signed-off-by: Bin Meng
> ---
>
> include/efi_loader.h | 3 ---
> lib/efi_loader/efi_boottime.c | 4 ++--
> 2 files changed, 2
On Wed, Apr 05, 2023 at 08:15:16PM +0800, Bin Meng wrote:
> load_file() and load_file2() are only referenced in
> efi_selftest_load_file.c
>
> Signed-off-by: Bin Meng
> ---
>
> lib/efi_selftest/efi_selftest_load_file.c | 20 ++--
> 1 file changed, 10 insertions(+), 10
On Wed, Apr 05, 2023 at 08:15:15PM +0800, Bin Meng wrote:
> record is only referenced in efi_selftest_exitbootservices.c
>
> Signed-off-by: Bin Meng
> ---
>
> lib/efi_selftest/efi_selftest_exitbootservices.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
From: Ashok Reddy Soma
In current implementation, applications can execute only on R5 core 0.
The boot address for R5 core 1 is not supplied. Pass TCM address for
R5 core 1 based on the argument to fix the issue.
Remove incomplete comment.
Signed-off-by: Ashok Reddy Soma
Signed-off-by: Michal
Fix and document the Secure Channel Protocol03 emulator.
Fixes: 5a8783c80c39 ("drivers: tee: sandbox: SCP03 control emulator")
Signed-off-by: Jorge Ramirez-Ortiz
---
drivers/tee/sandbox.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/drivers/tee/sandbox.c
Implement a ARM SMCCC based driver that allow to use
a secure watchdog on the platform.
Signed-off-by: Lionel Debieve
Reviewed-by: Patrick Delaunay
Tested-by: Patrick Delaunay
---
(no changes since v1)
drivers/watchdog/Kconfig | 8 +++
drivers/watchdog/Makefile | 1 +
ESM MCU masks must be set to 0h so that PMIC can handle errors
that require attention for example SYS_SAFETY_ERRn. The required bits
must be cleared: ESM_MCU_RST_MASK, ESM_MCU_FAIL_MASK, ESM_MCU_PIN_MASK.
If PMIC expected to handle errors, make sure EVM is configured to
connect SOC_SAFETY_ERRz
Given a file ../img of size 4294967296 with GPT partition table and
partitions:
=> host bind 0 ../img
=> part list host 0
Disk host-0.blk not ready
The cause is os_filesize() returning int. File sizes must use off_t.
Correct all uses of os_filesize() too.
Signed-off-by: Heinrich Schuchardt
os.h is only used by the sandbox.
Signed-off-by: Heinrich Schuchardt
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 91d40ea4b6..a0e20ba7c6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1338,6 +1338,7 @@ F:arch/sandbox/
F:
> > Stop polluting the architecture directory with driver specific code,
> > move it into driver where it should be. Split the code slightly so
> > the MX8MM/MX8MN fuse readout and programming and MX8MP fuse readout
> > and programming are in their separate functions, and called in case
> > of
> > Use dev_(dev, ...) for all printing and debug logging, since this
> > already includes the device name. Drop device name where duplicate.
> >
> > Signed-off-by: Marek Vasut
> Reviewed-by: Fabio Estevam
Reviewed-by: Andrejs Cainikovs
Given a file ../img of size 4294967296 with GPT partition table and
partitions:
=> host bind 0 ../img
=> part list host 0
Disk host-0.blk not ready
The cause is os_filesize() returning int. 4294967296 converted to int32_t
gives 0. File sizes must use off_t.
Correct all uses of os_filesize()
Hi,
On Tue, 28 Mar 2023 04:15:15 +0800, Karl Chan wrote:
> Add build instructions for the Beelink GT1 Ultimate board.
>
>
Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-amlogic
(u-boot-amlogic)
[3/3] doc: boards: amlogic: add documentation for Beelink GT1 Ultimate
Hi,
On Tue, 28 Mar 2023 04:13:14 +0800, Karl Chan wrote:
> Add configuration for the Beelink GT1 Ultimate board.
>
>
Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-amlogic
(u-boot-amlogic)
[2/3] boards: amlogic: add Beelink GT1 Ultimate defconfig
Hi,
On Tue, 28 Mar 2023 04:11:52 +0800, Karl Chan wrote:
> Import the device-tree from linux-amlogic/for-next (Linux 6.3-rc1).
>
>
Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-amlogic
(u-boot-amlogic)
[1/3] ARM: dts: add support for Beelink GT1 Ultimate
Hi Andrew,
On 05/04/23 00:27, Andrew Davis wrote:
On 4/4/23 7:13 AM, Neha Malcom Francis wrote:
This series aims to eliminate the use of additional custom repositories
such as k3-image-gen (K3 Image Generation) repo that was plumbed into
the U-Boot build flow to generate boot images for TI K3
Hi all
>
> Preparation for per driver instance allocated data structures.
>
> Signed-off-by: Christian Gmeiner
gentle ping - what can I do better to get some feedback, RBs, etc
faster? This experience is
quite frustrating and it happens for me from time to time for U-Boot patches :(
Patch 1 of
1 - 100 of 101 matches
Mail list logo
