On Wed, 13 Nov 2024 at 04:30, Sam Protsenko wrote:
>
> On Mon, Nov 11, 2024 at 8:48 AM Ilias Apalodimas
> wrote:
> >
> > On Thu, 7 Nov 2024 at 04:58, Sam Protsenko
> > wrote:
> > >
> > > SCTLR_EL2 is a 64-bit register [1]. Return its value as long (64 bit)
> > > instead of int (32 bit) in get_s
On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
>
> Add efi_dp_from_http to form a device path from HTTP. The
> device path is the concatenation of the device path returned
> by efi_dp_from_ipv4 together with an URI node and an END node.
>
> Signed-off-by: Adriano Cordova
> ---
>
> Changes i
Add support for spi-nor flash reset via GPIO controller
by reading the reset-gpios property.
[Ported from Linux kernel commit
8f1ee9ef71d0 ("mtd: spi-nor: Add support for flash reset") ]
Signed-off-by: Venkatesh Yadav Abbarapu
---
Changes in v2:
- Removed the code from spi_nor_remove() as gpio d
Some dt-binding headers mask the upstream ones which can lead to build
failures, or worse: super weird bugs, if they get out of sync.
Remove these headers so our devicetree and binding headers will both be
in sync with upstream.
Signed-off-by: Caleb Connolly
---
Build tested with qcom_defconfig,
Make use of OF_UPSTREAM which uses Linux dts.
Signed-off-by: david regan
Reviewed-by: Linus Walleij
Reviewed-by: Sumit Garg
Reviewed-by: William Zhang
Reviewed-by: Anand Gore
---
arch/arm/dts/bcm47622.dtsi| 126
arch/arm/dts/bcm4912.dtsi | 128 ---
These device specific nand driver files can be removed because
they are now replaced by a common driver bcmbca_nand.c
Signed-off-by: david regan
Reviewed-by: Linus Walleij
Reviewed-by: William Zhang
Reviewed-by: Anand Gore
---
drivers/mtd/nand/raw/Kconfig | 24
drivers/
Set parameter_page_big_endian to zero for bcmbca
Signed-off-by: david regan
Reviewed-by: William Zhang
Reviewed-by: Anand Gore
---
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
b/drivers/mtd/nand/r
These are ports of upstream Linux patches to U-Boot.
Remove device specific nand driver files as they are now replaced
by a common driver bcmbca_nand.c
Make use of OF_UPSTREAM which uses Linux dts.
Implement a minimal set of defconfig options to enable basic NAND
functionality. Tested on:
47622
This patch adds support for determining whether a gpio pin is mapped as
peripheral function.
Signed-off-by: Zixun LI
---
Changes in v2:
- Rename function
---
drivers/gpio/at91_gpio.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/gpio/at91_gpio.c b/driv
Update log level messages so that more critical messages can be logged
to console and help the troubleshooting with field devices.
This is a port of the upstream Linux patch to U-Boot.
https://lore.kernel.org/linux-mtd/20240223034758.13753-4-william.zh...@broadcom.com/
Signed-off-by: david regan
Support GPIO configuration with following flags:
- in, out, out_active
- open_drain, pull_up
Signed-off-by: Zixun LI
---
Changes in v2:
- Return ENOTSUPP if flag is unsupported.
- Inline port output variable.
---
drivers/gpio/at91_gpio.c | 39 +++
1 file chang
Add ops get_dir_flags() to read status from GPIO registers.
Signed-off-by: Zixun LI
---
Changes in v2:
- Fix pullup read polarity
Changes in v3:
- Use clamp (!!) to turn return value into a bool
---
drivers/gpio/at91_gpio.c | 45
1 file changed, 45 inser
On Wed, 13 Nov 2024 at 18:03, Heinrich Schuchardt wrote:
>
> On 11/13/24 12:28, Ilias Apalodimas wrote:
> > Hi Sughosh
> >
> > On Tue, 12 Nov 2024 at 20:46, Sughosh Ganu wrote:
> >>
> >> On Tue, 12 Nov 2024 at 18:48, Simon Glass wrote:
> >>>
> >>> A bisect of Ubuntu 2022.04 boot-failure on qemu-
On 11/1/24 21:29, Mark Kettenis wrote:
From: Janne Grunau
Date: Thu, 31 Oct 2024 23:48:02 +0100
DM_FLAG_VITAL marks devices which are essential for the operation of
other devices. Removing these devices before their users can result in
hangs or crashes.
This potentially fixes EFI boot of Renesa
On 11/13/24 12:28, Ilias Apalodimas wrote:
Hi Sughosh
On Tue, 12 Nov 2024 at 20:46, Sughosh Ganu wrote:
On Tue, 12 Nov 2024 at 18:48, Simon Glass wrote:
A bisect of Ubuntu 2022.04 boot-failure on qemu-x86_64 resulted in this
patch. I am not sure how to investigate it.
The boot hangs at so
El mié, 13 nov 2024 a las 5:16, Ilias Apalodimas (<
ilias.apalodi...@linaro.org>) escribió:
> On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
> >
> > Add efi_dp_from_http to form a device path from HTTP. The
> > device path is the concatenation of the device path returned
> > by efi_dp_from_
On 13/11/2024 10:48, Dragan Simic wrote:
> Hello Caleb,
>
> Thanks for the patch. Please, see a comment below.
>
> On 2024-11-13 06:30, Caleb Connolly wrote:
>> It may be the case that MMC support is enabled even though the board
>> we're booting on doesn't have any MMC devices. Move the prin
Hello Caleb,
On 2024-11-13 14:08, Caleb Connolly wrote:
On 13/11/2024 10:48, Dragan Simic wrote:
Thanks for the patch. Please, see a comment below.
On 2024-11-13 06:30, Caleb Connolly wrote:
It may be the case that MMC support is enabled even though the board
we're booting on doesn't have an
Hi Adriano,
You forgot to add reviewed tags on this one.
I am reviewing the rest of the patches, so please go through the tags
and add them when you send a v4.
Thanks
/Ilias
On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
>
> From: Heinrich Schuchardt
>
> Add long texts for
>
> * EFI HTTP
Reviewed-by tags missing for me * Heinrich
On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
>
> The function string_to_ip is already in net_utils, which is
> compiled unconditionally, but ip_to_string is currently only
> accessible if the legacy network stack is selected. This
> commit puts i
On Tue, 12 Nov 2024 at 16:11, Simon Glass wrote:
>
> Add a list of possible platforms that can be used by gitlab runners.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
> Changes in v3:
> - Drop patches which remove grub and tracing for arm64
>
> .gitlab-ci.yml | 1 +
> 1 file c
On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
>
> Add definition for DEVICE_PATH_SUB_TYPE_MSG_IPV4 device path
> subtype.
>
> Signed-off-by: Adriano Cordova
> ---
>
> Changes in v3:
> - Removed alignment in struct efi_ipv4_address
>
> include/efi_api.h | 17 +
> 1 file cha
On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
>
> Add efi_dp_from_ipv4 to form a device path from an ipv4 address.
>
> Signed-off-by: Adriano Cordova
> ---
>
> Changes in v3:
> - Removed some unnecessary void* casts.
> - Changed sizeof(struct efi_device_path_ipv4) to sizeof(*ipv4dp)
> in
On Wed, Nov 13, 2024 at 02:58:42PM +0900, Dominique Martinet wrote:
> Dominique Martinet wrote on Wed, Nov 06, 2024 at 09:56:42AM +0900:
> > Running commands such as 'load mmc 2:1 $addr $path' when path does not
> > exists historically do not print any error on filesystems such as ext4
> > or fat.
On Tue, 05 Nov 2024 12:08:49 +0100, Jerome Forissier wrote:
> We don't do anything with Content-Length except a debug print, and the
> strict_strtoul() call is incorrect (it always returns -EINVAL and leaves
> content_length to zero due to the presence of trailing characters after
> the decimal va
On 13/11/2024 05:22, Caleb Connolly wrote:
Add a small utility for displaying some information about U-Boot and the
hardware it's running on in a similar fashion to the popular neofetch
tool for Linux [1].
While the output is meant to be useful, it should also be pleasing to
look at and perhaps
On Wed, Nov 13, 2024 at 06:30:08AM +0100, Caleb Connolly wrote:
> It may be the case that MMC support is enabled even though the board
> we're booting on doesn't have any MMC devices. Move the print over to
> the print_mmc_devices() function where we can only print it if we
> actually have MMC dev
On Wed, Nov 13, 2024 at 03:40:01PM +0100, Heinrich Schuchardt wrote:
> Am 13. November 2024 14:32:57 MEZ schrieb Neil Armstrong
> :
> >On 13/11/2024 05:22, Caleb Connolly wrote:
> >> Add a small utility for displaying some information about U-Boot and the
> >> hardware it's running on in a similar
This causes problems with the boot order, so drop it until we can figure
out a better way to know when bootmgr should be used.
Link:
https://lore.kernel.org/u-boot/20241112171205.4e805...@donnerap.manchester.arm.com/
Signed-off-by: Simon Glass
---
Changes in v5:
- Add new patch to drop bootmgr
On Wed, 13 Nov 2024 at 18:04, Simon Glass wrote:
>
> Hi Ilias,
>
> On Wed, 13 Nov 2024 at 08:11, Ilias Apalodimas
> wrote:
> >
> > On Wed, 13 Nov 2024 at 17:09, Simon Glass wrote:
> > >
> > > Hi Ilias,
> > >
> > > On Wed, 13 Nov 2024 at 07:46, Ilias Apalodimas
> > > wrote:
> > > >
> > > > On W
On Wed, Nov 13, 2024 at 09:03:22AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 13 Nov 2024 at 08:24, Tom Rini wrote:
[snip]
> > We're not going to get the sunxi series in for v2025.01, so we have time
> > to think about this still and try and get the code to match up with the
> > use cases.
>
From: Neil Armstrong
Hi,
On Tue, 12 Nov 2024 15:58:32 +0300, Alexey Romanov wrote:
> We should remove bindings and dtsi from include/ folder for A1
> and AXG Amlogic devices. We have exactly the same, or with minor
> differences in dts/upstream folder.
>
> I tested this changes on devices close
Hi Heinrich,
On Wed, 13 Nov 2024 at 08:17, Heinrich Schuchardt
wrote:
>
> Am 13. November 2024 15:39:22 MEZ schrieb Simon Glass :
> >Hi,
> >
> >On Wed, 13 Nov 2024 at 05:52, Heinrich Schuchardt
wrote:
> >>
> >> On 11/1/24 21:29, Mark Kettenis wrote:
> >> >> From: Janne Grunau
> >> >> Date: Thu,
The phyCORE-i.MX 93 is available in various variants. Relevant variant
options for the spl/u-boot are:
- with or without HS400 support for the eMMC
- with 1GB ram chip, or 2GB ram chip
The phyCORE's eeprom contains all information about the existing variant
options. Add evaluation of the eeprom da
The phyCORE-i.MX 93 is available in various variants (e.g. different ram
sizes, eMMC HS400 yes/no). It's eeprom contains information which features
the existing module supports.
Extend the existing board-code to support all the SOM variants. The spl/u-boot
evaluates the eeprom information and enab
The phyCORE-i.MX 93 is available in various variants (e.g. different ram
sizes, eMMC HS400 yes/no). Enable hardware introspection for the
imx93-phyboard-segin_defconfig, so that during startup the SOM module
variant can be detected, and the hardware can be configured accordingly.
The resulting SPL
On Sun, 03 Nov 2024 04:50:15 +0100, Heinrich Schuchardt wrote:
> Avoid a build failure when building with CONFIG_API=y, CONFIG_EXAMPLES=y:
>
> lib/vsprintf.c:312:14: warning:
> ‘device_path_string’ defined but not used [-Wunused-function]
> 312 | static char *device_path_string(char
On Sun, 03 Nov 2024 18:54:00 +0100, Heinrich Schuchardt wrote:
> We have only implemented longjmp() on the EFI architectures.
>
> Define a symbol CONFIG_HAVE_SETJMP and have it selected by the relevant
> architectures.
>
> Use CONFIG_HAVE_SETJMP to decide if the longjmp test shall be built.
>
>
The phyCORE-i.MX 93 is available with a 1GB ram chip or a 2GB ram chip.
Add the ram timings for the 2GB chip, in form of a diff compared
to the existing LPDDR4X 1GB timings. With that, the SPL can select the
appropriate timings at startup.
Update also the 1GB ram timings with new version of the DDR
On Wed, 06 Nov 2024 08:35:43 -0700, Simon Glass wrote:
> This flag was lost by a previous change and has never been restored.
> Without it, binman cannot fully handle missing blobs which are
> themselves inputs to mkimage.
>
> Discussion on this at [1] indicated that this was necessary but the
>
On Thu, 07 Nov 2024 10:38:53 +0100, Heinrich Schuchardt wrote:
> After calling strdup() check the returned pointer.
>
> Avoid a memory leak if the directory is not found.
>
>
Applied to u-boot/master, thanks!
--
Tom
write}_config_* function calls
(2024-11-04 18:01:58 -0600)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-amlogic.git
tags/u-boot-amlogic-next-20241113
for you to fetch changes up to 1cdb4e03e684d94456dee0cc30c935d7e25b263d:
dt-bindings: interrupt-contr
On Wed, Nov 13, 2024 at 08:09:31AM -0700, Simon Glass wrote:
> In principle bootstd can work without block devices, even if it does
> require driver model to be enabled in that case.
>
> The use of a 'depends on BLK' for BOOTSTD conflicts with the way 'BLK'
> is now defined, producing recursive e
On Tue, 05 Nov 2024 20:31:29 +0100, Heinrich Schuchardt wrote:
> qemu_arm64_defconfig with CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=n leads to a
> build error:
>
> arch/arm/lib/crt0_64.S:85:
> Error: constant expression expected at operand 2 --
> `ldr x0,=((CFG_SYS_INIT_RAM_ADDR+CFG_SYS_INI
On Sun, 03 Nov 2024 23:42:19 +0100, Heinrich Schuchardt wrote:
> The lib_test_uuid_to_le and lib lib_test_dynamic_uuid tests fail on
> 32-bit systems. But we never caught this in our CI because we never
> ran any of our C unit tests on 32-bit.
>
> Enable CONFIG_UNIT_TEST on qemu_arm_defconfig.
>
On Wed, Nov 13, 2024 at 08:09:33AM -0700, Simon Glass wrote:
> This causes problems with the boot order, so drop it until we can figure
> out a better way to know when bootmgr should be used.
>
> Link:
> https://lore.kernel.org/u-boot/20241112171205.4e805...@donnerap.manchester.arm.com/
>
> Sig
On Wed, Nov 13, 2024 at 08:09:34AM -0700, Simon Glass wrote:
> This is another option to fix sunxi booting with bootstd, which may be
> better since it will work for all boards. We can then figure out how to
> automatically and deterministicaly decide when bootmgr should be used.
>
> This reverts
"Error reading cluster" is the new error.
U-Boot SPL 2025.01-rc2 (Nov 08 2024 - 07:13:26 +)
DDR version: dc2e84f0.
Trying to boot from MMC2
U-Boot 2025.01-rc2 (Nov 08 2024 - 07:13:26 +)
CPU: sifive,u74-mc
Model: StarFive VisionFive 2 v1.2A
DRAM: 4 GiB
Core: 136 devices, 26 uclasses,
Hi Heinrich,
On Mon, 11 Nov 2024 at 23:10, Adriano Cordova wrote:
>
> From: Heinrich Schuchardt
>
> Implement Ipv4() node support in the device path to text protocol.
>
> Signed-off-by: Heinrich Schuchardt
> Signed-off-by: Adriano Cordova
> ---
>
> (no changes since v2)
>
> lib/efi_loader/efi
Hello Peng,
On Wed, Nov 13, 2024 at 05:27:23AM +, Peng Fan wrote:
> > Subject: [PATCH v1] imx: Fix critical thermal threshold
> >
> > From: Francesco Dolcini
> >
> > Fix the critical thermal threshold for i.MX processors, this was changed
> > while moving the code from imx8m/imx9 directorie
Hello Caleb,
Thanks for the patch. Please, see a comment below.
On 2024-11-13 06:30, Caleb Connolly wrote:
It may be the case that MMC support is enabled even though the board
we're booting on doesn't have any MMC devices. Move the print over to
the print_mmc_devices() function where we can on
On Mon, 2024-11-11 at 04:49 -0600, Adam Ford wrote:
> On Mon, Nov 11, 2024 at 1:48 AM Yannic Moog wrote:
> >
> > Hi,
> >
> > On Fri, 2024-11-08 at 10:05 -0800, Tim Harvey wrote:
> > > On Fri, Nov 8, 2024 at 5:49 AM Adam Ford wrote:
> > > >
> > > > On Thu, Nov 7, 2024 at 2:42 AM Yannic Moog wr
HI
On Wed, Nov 13, 2024 at 7:27 AM david regan wrote:
>
> These are ports of upstream Linux patches to U-Boot.
>
> Remove device specific nand driver files as they are now replaced
> by a common driver bcmbca_nand.c
>
> Make use of OF_UPSTREAM which uses Linux dts.
>
> Implement a minimal set of
> Subject: Re: [PATCH v1] imx: Fix critical thermal threshold
>
> Hello Peng,
>
> On Wed, Nov 13, 2024 at 05:27:23AM +, Peng Fan wrote:
> > > Subject: [PATCH v1] imx: Fix critical thermal threshold
> > >
> > > From: Francesco Dolcini
> > >
> > > Fix the critical thermal threshold for i.MX pr
Hi Sughosh
On Tue, 12 Nov 2024 at 20:46, Sughosh Ganu wrote:
>
> On Tue, 12 Nov 2024 at 18:48, Simon Glass wrote:
> >
> > A bisect of Ubuntu 2022.04 boot-failure on qemu-x86_64 resulted in this
> > patch. I am not sure how to investigate it.
> >
> > The boot hangs at some point during booting of
On Sun, Nov 10, 2024 at 12:50:19PM +0100, Christian Marangi wrote:
> This series is split in 2 part.
>
> While adapting the LED boot and activity code to the new property
> accepted by Rob in dt-schema repository, a big BUG was discovered.
>
> The reason wasn't clear at start and took me some da
Add a list of possible platforms that can be used by gitlab runners.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
Reviewed-by: Ilias Apalodimas
---
(no changes since v3)
Changes in v3:
- Drop patches which remove grub and tracing for arm64
.gitlab-ci.yml | 1 +
1 file changed, 1 inserti
Refactor the code to support downloading toolchains for arm64 as well as
x86_64
There doesn't seem to be an xtensa toolchain for arm64 at the same
location, so download that only on x86
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
---
(no changes since v3)
Changes in v3:
- Add patch to in
The package names are slightly different for arm64 and we don't seem to
have a linux-image-kvm package. Provide some extra ones for x86
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
---
(no changes since v3)
Changes in v3:
- Use grub-efi and linux-image-generic for both archs
Changes in v2
This isn't needed for sandbox builds and coreboot isn't much used on
arm64, nor does U-Boot have a build that supports running from coreboot
on any ARM target.
So drop it.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
---
(no changes since v1)
tools/docker/Dockerfile | 6 --
1 file ch
Fix a warning due to the syntax used for PYTHONPATH:
LegacyKeyValueFormat: "ENV key=value" should be used instead of
legacy "ENV key value" format (line 304)
Signed-off-by: Simon Glass
Reviewed-by: Heinrich Schuchardt
Reviewed-by: Tom Rini
---
(no changes since v1)
tools/docker/Doc
Do not apply.
Switch over to the new multiarch image so we can try a run.
Signed-off-by: Simon Glass
---
(no changes since v1)
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index e152060b046..3275d9ffa45 100644
--- a/.gitlab
On Wed, Nov 13, 2024 at 08:09:37AM -0700, Simon Glass wrote:
> Some boards use a CONFIG option to specify the value of this variable.
> This is normally handled by efi_get_distro_fdt_name() but in the case
> of sunxi this does not work, since 'soc' is sunxi, but the files are
> in the allwinner di
Am 13. November 2024 17:03:03 MEZ schrieb Simon Glass :
>Hi Heinrich,
>
>On Wed, 13 Nov 2024 at 08:17, Heinrich Schuchardt
>wrote:
>>
>> Am 13. November 2024 15:39:22 MEZ schrieb Simon Glass :
>> >Hi,
>> >
>> >On Wed, 13 Nov 2024 at 05:52, Heinrich Schuchardt
>wrote:
>> >>
>> >> On 11/1/24 21:29,
The cache-flush function is incorrect which causes a crash in the
remoteproc tests with arm64.
Fix both problems by using map_sysmem() to convert an address to a
pointer and map_to_sysmem() to convert a pointer to an address.
Also update the image-loader's cache-flushing logic.
Signed-off-by: Si
Since char is unsigned on arm64, this test currently fails. It seems
better to use unsigned anyway, since 0xff is written into the string at
the start. Update the terminator-assert to use a character instead of a
byte.
Signed-off-by: Simon Glass
Reviewed-by: Heinrich Schuchardt
---
(no changes
All gitlab runners are currently amd64 machines. This series attempts to
create a docker image which can also support arm64 so that sandbox tests
can be run on it.
The TARGET_... environment variables for grub could perhaps be adjusted,
using the new variables, but I have not done that for now.
C
Add instructions on how to build the file for multiple architectures.
Add a message indicating what is happening.
Update the documentation as well.
Signed-off-by: Simon Glass
---
Changes in v4:
- Leave the 'sudo' in
Changes in v3:
- Move ARGs to the top
- Revise documentation to explain a comm
Am 13.11.24 um 17:00 schrieb Christoph Stoidner:
The phyCORE-i.MX 93 is available in various variants (e.g. different ram
sizes, eMMC HS400 yes/no). Enable hardware introspection for the
imx93-phyboard-segin_defconfig, so that during startup the SOM module
variant can be detected, and the hard
rcar3_salvator-x_defconfig fails to build with UEFI support on current
Ubuntu as u-boot-nodtb.bin becomes too big:
u-boot-nodtb.bin exceeds file size limit:
limit: 0x10 bytes
actual: 0x1010f8 bytes
excess: 0x10f8 bytes
Reported-by: Adriano Cordova
Signed-off-by: Heinri
Am 13.11.24 um 17:00 schrieb Christoph Stoidner:
The phyCORE-i.MX 93 is available in various variants. Relevant variant
options for the spl/u-boot are:
- with or without HS400 support for the eMMC
- with 1GB ram chip, or 2GB ram chip
The phyCORE's eeprom contains all information about the exi
Am 13.11.24 um 17:00 schrieb Christoph Stoidner:
The phyCORE-i.MX 93 is available in various variants (e.g. different ram
sizes, eMMC HS400 yes/no). It's eeprom contains information which features
the existing module supports.
Extend the existing board-code to support all the SOM variants. Th
HI Ilias,
On Mon, 11 Nov 2024 at 07:20, Ilias Apalodimas
wrote:
>
> Thanks Simon,
>
> On Mon, 11 Nov 2024 at 15:03, Simon Glass wrote:
> >
> > On Sun, 10 Nov 2024 at 01:32, Ilias Apalodimas
> > wrote:
> > >
> > > With the recent changes of lwip & mbedTLS we can now download from
> > > https://
Hi Heinrich,
On Tue, 12 Nov 2024 at 03:26, Heinrich Schuchardt
wrote:
>
> Without 'nvme scan' the ESP on the NVMe drive is not found early.
> EFI variables cannot be persisted.
>
> Hit any key to stop autoboot: 0
> Cannot persist EFI variables without system partition
> ** Booting bo
Hi Heinrich,
On Sun, 3 Nov 2024 at 15:42, Heinrich Schuchardt
wrote:
>
> We often convert hexadecimal strings to hextoull(). Provide a wrapper
> function to simple_strtoull() that does not require specifying the radix.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2:
> no change
> ---
Hi Caleb,
On Tue, 12 Nov 2024 at 21:50, Caleb Connolly wrote:
>
> The Qualcomm Robotics RB1 and RB2 boards feature MMC storage provisioned
> with a 4k sector size GPT, with factory partitions formatted with
> filesystems using 512 byte sector sizes.
>
> Whilst certainly unusual, and really not id
This series attempts to migrate all sunxi boards to use standard boot,
along with a text environment.
Unfortunately a late-breaking problem has come up with bootmgr. There
are two ways to fix this, both included in this series:
- Drop bootmgr for sunxi
- Change efi_mgr bootmeth back to sand
Drop support for distroboot and move to using bootstd instead.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Convert the other DISTRO_DEFAULTS in the Kconfig too
arch/arm/Kconfig | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/arm/Kc
Add support for booting from a script loaded over FEL. This mirrors the
bootcmd_fel provided by distro boot.
Signed-off-by: Simon Glass
Reviewed-by: Mattijs Korpershoek
---
(no changes since v4)
Changes in v4:
- Reword Kconfig
- Add a name for the bootflow
Changes in v2:
- Put the FEL bootmet
Hi Ilias,
On Wed, 13 Nov 2024 at 07:46, Ilias Apalodimas
wrote:
>
> On Wed, 13 Nov 2024 at 15:39, Simon Glass wrote:
> >
> > HI Ilias,
> >
> > On Mon, 11 Nov 2024 at 07:20, Ilias Apalodimas
> > wrote:
> > >
> > > Thanks Simon,
> > >
> > > On Mon, 11 Nov 2024 at 15:03, Simon Glass wrote:
> > >
In principle bootstd can work without block devices, even if it does
require driver model to be enabled in that case.
The use of a 'depends on BLK' for BOOTSTD conflicts with the way 'BLK'
is now defined, producing recursive errors through multiple different
paths, one of which is this (with Links
On Wed, 13 Nov 2024 at 17:09, Simon Glass wrote:
>
> Hi Ilias,
>
> On Wed, 13 Nov 2024 at 07:46, Ilias Apalodimas
> wrote:
> >
> > On Wed, 13 Nov 2024 at 15:39, Simon Glass wrote:
> > >
> > > HI Ilias,
> > >
> > > On Mon, 11 Nov 2024 at 07:20, Ilias Apalodimas
> > > wrote:
> > > >
> > > > Thank
Some boards use a CONFIG option to specify the value of this variable.
This is normally handled by efi_get_distro_fdt_name() but in the case
of sunxi this does not work, since 'soc' is sunxi, but the files are
in the allwinner directory.
Provide a work-around for this particular case.
Signed-off-
Convert these boards to use a text environment.
For the boards check, the only differences are extra spaces after the
semicolons in 'dfu_alt_info_ram' and 'partitions', both of which are
permitted.
Add in the special boot command for old kernels, dropping the
unnecessary and confusing hex prefixe
This is another option to fix sunxi booting with bootstd, which may be
better since it will work for all boards. We can then figure out how to
automatically and deterministicaly decide when bootmgr should be used.
This reverts commit f2bfa0cb17948aa4a0fa20fdf9014296b9c4d9c7.
Signed-off-by: Simon
These are not needed as bootstd handles the boot now. Drop them.
Keep BOOTCMD_SUNXI_COMPAT for now since it does not relate to
distro boot.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Keep BOOTCMD_SUNXI_COMPAT
include/configs/sunxi-common.h | 75 +---
> All `serial_putc()`-like functions that I could find are either static to the
> actual driver and thus not accessible from `board_init()` or do not accept a
> `struct udevice *` as a parameter and seem to work on the main U-Boot serial
> console device only.
Reading other board code I think I ha
Hi,
On Wed, 13 Nov 2024 at 05:52, Heinrich Schuchardt wrote:
>
> On 11/1/24 21:29, Mark Kettenis wrote:
> >> From: Janne Grunau
> >> Date: Thu, 31 Oct 2024 23:48:02 +0100
> >>
> >> DM_FLAG_VITAL marks devices which are essential for the operation of
> >> other devices. Removing these devices bef
On 11/11/24 13:47, Ilias Apalodimas wrote:
> Hi Jerome,
>
> On Tue, 5 Nov 2024 at 13:09, Jerome Forissier
> wrote:
>>
>> We don't do anything with Content-Length except a debug print, and the
>> strict_strtoul() call is incorrect (it always returns -EINVAL and leaves
>> content_length to zero
Am 13. November 2024 15:39:22 MEZ schrieb Simon Glass :
>Hi,
>
>On Wed, 13 Nov 2024 at 05:52, Heinrich Schuchardt wrote:
>>
>> On 11/1/24 21:29, Mark Kettenis wrote:
>> >> From: Janne Grunau
>> >> Date: Thu, 31 Oct 2024 23:48:02 +0100
>> >>
>> >> DM_FLAG_VITAL marks devices which are essential fo
On Wed, Nov 13, 2024 at 07:42:57AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 13 Nov 2024 at 07:12, Tom Rini wrote:
> >
> > On Wed, Nov 13, 2024 at 06:39:43AM -0700, Simon Glass wrote:
> > > Hi Heinrich,
> > >
> > > On Sun, 3 Nov 2024 at 15:42, Heinrich Schuchardt
> > > wrote:
> > > >
> > >
On Wed, Nov 13, 2024 at 07:39:53AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Fri, 18 Oct 2024 at 12:48, Simon Glass wrote:
> >
> > Hi Tom,
> >
> > On Fri, 18 Oct 2024 at 12:29, Tom Rini wrote:
> > >
> > > On Fri, Oct 18, 2024 at 12:06:46PM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > >
Hi Tom,
On Wed, 13 Nov 2024 at 07:12, Tom Rini wrote:
>
> On Wed, Nov 13, 2024 at 06:39:43AM -0700, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Sun, 3 Nov 2024 at 15:42, Heinrich Schuchardt
> > wrote:
> > >
> > > We often convert hexadecimal strings to hextoull(). Provide a wrapper
> > > func
Hi Tom,
On Fri, 18 Oct 2024 at 12:48, Simon Glass wrote:
>
> Hi Tom,
>
> On Fri, 18 Oct 2024 at 12:29, Tom Rini wrote:
> >
> > On Fri, Oct 18, 2024 at 12:06:46PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Fri, 18 Oct 2024 at 11:52, Tom Rini wrote:
> > > >
> > > > On Fri, Oct 18, 202
Hi Tom,
On Tue, 12 Nov 2024 at 19:40, Tom Rini wrote:
>
> On Fri, Nov 08, 2024 at 08:23:44AM -0700, Simon Glass wrote:
>
> > This is used by some boards in U-Boot and is a convenient way to deal
> > with common settings where using a Kconfig files is not desirable.
> >
> > Detect #include files a
Am 13. November 2024 14:32:57 MEZ schrieb Neil Armstrong
:
>On 13/11/2024 05:22, Caleb Connolly wrote:
>> Add a small utility for displaying some information about U-Boot and the
>> hardware it's running on in a similar fashion to the popular neofetch
>> tool for Linux [1].
>>
>> While the output
On Wed, 13 Nov 2024 at 15:39, Simon Glass wrote:
>
> HI Ilias,
>
> On Mon, 11 Nov 2024 at 07:20, Ilias Apalodimas
> wrote:
> >
> > Thanks Simon,
> >
> > On Mon, 11 Nov 2024 at 15:03, Simon Glass wrote:
> > >
> > > On Sun, 10 Nov 2024 at 01:32, Ilias Apalodimas
> > > wrote:
> > > >
> > > > With
On 13/11/2024 15:24, Tom Rini wrote:
> On Wed, Nov 13, 2024 at 06:30:08AM +0100, Caleb Connolly wrote:
>
>> It may be the case that MMC support is enabled even though the board
>> we're booting on doesn't have any MMC devices. Move the print over to
>> the print_mmc_devices() function where we
On 13/11/2024 15:40, Heinrich Schuchardt wrote:
Am 13. November 2024 14:32:57 MEZ schrieb Neil Armstrong
:
On 13/11/2024 05:22, Caleb Connolly wrote:
Add a small utility for displaying some information about U-Boot and the
hardware it's running on in a similar fashion to the popular neofetch
t
On Tue, 12 Nov 2024 at 21:26, Caleb Connolly wrote:
>
> Add a small utility for displaying some information about U-Boot and the
> hardware it's running on in a similar fashion to the popular neofetch
> tool for Linux [1].
>
> While the output is meant to be useful, it should also be pleasing to
>
1 - 100 of 159 matches
Mail list logo
