Hi Tom,
On Tue, 25 Jun 2024 at 15:27, Tom Rini wrote:
>
> On Tue, Jun 25, 2024 at 01:38:08PM +0100, Simon Glass wrote:
> > Hi Tom,
> >
> > On Mon, 24 Jun 2024 at 19:13, Tom Rini wrote:
> > >
> > > On Sun, Jun 23, 2024 at 02:32:02PM -0600, Simon Glass wrote:
> > >
> > > > In Labgrid there is the
On Mon, 24 Jun 2024 at 20:08, Bastian Germann wrote:
>
> Before 9d0750064e (doc: Move external FIT docs into the main body), the
> FIT property data-size was not a mandatory property and still it is not
> expected to be set alongside the data property.
>
> Move the data-size property to the "Condi
Hi Tom,
On Tue, 25 Jun 2024 at 15:14, Tom Rini wrote:
>
> On Tue, Jun 25, 2024 at 01:38:00PM +0100, Simon Glass wrote:
> > Hi Tom,
> >
> > On Mon, 24 Jun 2024 at 19:06, Tom Rini wrote:
> > >
> > > On Sun, Jun 23, 2024 at 02:32:00PM -0600, Simon Glass wrote:
> > >
> > > > When a test returns -EAG
Hi Tom,
On Tue, 25 Jun 2024 at 15:14, Tom Rini wrote:
>
> On Tue, Jun 25, 2024 at 01:38:04PM +0100, Simon Glass wrote:
> > Hi Tom,
> >
> > On Mon, 24 Jun 2024 at 19:29, Tom Rini wrote:
> > >
> > > On Sun, Jun 23, 2024 at 02:30:32PM -0600, Simon Glass wrote:
> > >
> > > > Some configuration is no
Hi Andrejs,
On Tue, 25 Jun 2024 at 16:16, Andrejs Cainikovs
wrote:
>
> On Tue, Jun 25, 2024 at 01:38:07PM +0100, Simon Glass wrote:
> > Hi Andrejs,
> >
> > On Tue, 25 Jun 2024 at 01:06, Andrejs Cainikovs
> > wrote:
> > >
> > > On Sun, Jun 23, 2024 at 11:56:20AM -0600, Simon Glass wrote:
> > > >
Hi Simon,
On Tue, Jun 25, 2024 at 01:30:18PM +0100, Simon Glass wrote:
> Hi Philip,
>
> On Mon, 24 Jun 2024 at 02:35, Philip Oberfichtner wrote:
> >
> > Implement memory barrier using mfence. Linux does it equivalently [1].
> >
> > "The MFENCE instruction establishes a memory fence for both load
Hi,
On Thu, 20 Jun 2024 09:42:49 +0200, Neil Armstrong wrote:
> Switch to set_mode callback now it's available and in the same
> time make public functions static and drop useless mach-meson
> headers that are no more needed.
>
>
Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boo
Hi,
On Sun, 23 Jun 2024 14:30:19 -0600, Simon Glass wrote:
> This series includes a number of mostly unrelated changes which are in
> service of running U-Boot on a lab using Labgrid.
>
> Changes in v2:
> - Add new patch to update u-boot.cfg with CFG_... options
>
> Simon Glass (14):
> trace:
Hi Tony,
On Sat, Jun 15, 2024 at 03:06:54PM -0700, Tony Dinh wrote:
[...]
> diff --git a/board/Synology/ds414/ds414.c b/board/Synology/ds414/ds414.c
> index abe6f9eb5e..f0b55fa095 100644
> --- a/board/Synology/ds414/ds414.c
> +++ b/board/Synology/ds414/ds414.c
> @@ -181,18 +181,9 @@ int board_init
Mashed up from different sources linked below, including the now gone
Wiki and doc/README.arm-relocation file. Tested on a custom board with
AT91 SAMA5D2 SoC and Segger J-Link Base adapter. This is only generic
advice here, the usage is not board specific. Some board docs have more
specific inst
Hi Paul,
On 6/26/2024 3:17 PM, Paul Geurts wrote:
Hi,
Thanks for the feedback.
Hi Paul,
On 6/24/2024 8:09 PM, Fabio Estevam wrote:
Hi Paul,
On Fri, Jun 21, 2024 at 10:06 AM Paul Geurts
wrote:
-struct imx_sec_config_fuse_t {
+struct imx_fuse_t {
Please make the struct renaming a separa
Hi,
Thanks for the feedback.
>Hi Paul,
>
>On 6/24/2024 8:09 PM, Fabio Estevam wrote:
>
>> Hi Paul,
>>
>> On Fri, Jun 21, 2024 at 10:06 AM Paul Geurts
>> wrote:
>>
>>> -struct imx_sec_config_fuse_t {
>>> +struct imx_fuse_t {
>> Please make the struct renaming a separate patch.
>>
>> Peng Fan, Ye
On Wed, Jun 26, 2024 at 09:00:43AM +0100, Simon Glass wrote:
> Hi Andrejs,
>
> On Tue, 25 Jun 2024 at 16:16, Andrejs Cainikovs
> wrote:
> >
> > On Tue, Jun 25, 2024 at 01:38:07PM +0100, Simon Glass wrote:
> > > Hi Andrejs,
> > >
> > > On Tue, 25 Jun 2024 at 01:06, Andrejs Cainikovs
> > > wrote:
Hi,
On Tue, 11 Jun 2024 14:01:14 -0600, Simon Glass wrote:
> Labgrid provides access to a hardware lab in an automated way. It is
> possible to boot U-Boot on boards in the lab without physically touching
> them. It relies on relays, USB UARTs and SD muxes, among other things.
>
> By way of backg
Hello!
This series adds support for the mtdblock device, which
allows to read/write data block by block. For example,
it can now be used for BCB or Android AB command:
$ bcb load mtd 0 part_name
Tested only on SPI NAND, so bind is made only for
SPI NAND drivers.
---
Changes V1 -> V2 [1]:
Add new MTD partition driver, which can be useful with
mtdblock driver combination.
Signed-off-by: Alexey Romanov
---
disk/part.c | 3 +-
drivers/mtd/Kconfig | 1 +
drivers/mtd/mtdpart.c | 76 +++
include/part.h| 3 ++
4 files change
MTD block - abstraction over MTD subsystem, allowing
to read and write in blocks using BLK UCLASS.
Signed-off-by: Alexey Romanov
---
drivers/block/blk-uclass.c | 1 +
drivers/mtd/Makefile | 3 +
drivers/mtd/mtdblock.c | 227 +
include/linux/mtd/m
Bind SPI-NAND driver to MTD block driver.
Reviewed-by: Frieder Schrempf
Signed-off-by: Alexey Romanov
---
drivers/mtd/nand/spi/core.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
index 62c28aa422..8edb468aed
Now user can pass an additional parameter 'offset'
to ubi_volume_read() function.
Signed-off-by: Alexey Romanov
Reviewed-by: Heiko Schocher
Acked-by: Heiko Schocher
---
cmd/ubi.c | 6 +++---
env/ubi.c | 6 +++---
include/ubi_uboot.h | 2 +-
3 files changed, 7 insertions(+),
Hello!
This series adds support for the UBI block device, which
allows to read/write data block by block. For example,
it can now be used for BCB or Android AB command:
$ bcb load ubi 0 part_name
Tested only on SPI NAND, so bind is made only for
SPI NAND drivers. Can be used with mtdblock devi
Introduce ubi_volume_offset_write() helper, which
allow to write to ubi volume with specified offset.
Signed-off-by: Alexey Romanov
Reviewed-by: Heiko Schocher
Acked-by: Heiko Schocher
---
cmd/ubi.c | 72 +++--
env/ubi.c | 10 +++
UBI block is an virtual device, that runs on top
of the MTD layer. The blocks are UBI volumes.
Intended to be used in combination with other MTD
drivers.
Despite the fact that it, like mtdblock abstraction,
it used with UCLASS_MTD, they can be used together
on the system without conflicting. For e
Block devices can already set partition type at initialization
stage, so, in this case is no point in searching for partition type.
Signed-off-by: Alexey Romanov
Reviewed-by: Heiko Schocher
---
disk/part.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/disk/part.c b/disk/part.c
inde
UBI partition is abstraction over UBI volumes.
Can be used by UBI block device.
Signed-off-by: Alexey Romanov
Reviewed-by: Heiko Schocher
---
drivers/mtd/ubi/Makefile | 2 +-
drivers/mtd/ubi/part.c | 99
include/part.h | 2 +
3 files change
UBI block is virtual block device, which is an abstraction
over MTD layer. Therefore it is logical to use it in combination
with MTD drivers.
Signed-off-by: Alexey Romanov
Reviewed-by: Frieder Schrempf
---
drivers/mtd/nand/spi/core.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
On Mon, 17 Jun 2024 10:03:46 +0200, Caleb Connolly wrote:
> MMU issues are some of the most frustrating to debug. To make this
> slightly less unbearable, introduce a software pagetable walker for
> ARMv8. This can be called to dump a pagetable with the default
> formatter, or a custom callback ca
On Wed, Jun 26, 2024 at 09:00:42AM +0100, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 25 Jun 2024 at 15:14, Tom Rini wrote:
> >
> > On Tue, Jun 25, 2024 at 01:38:00PM +0100, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 24 Jun 2024 at 19:06, Tom Rini wrote:
> > > >
> > > > On Sun, Jun 23, 20
On Wed, Jun 26, 2024 at 07:56:24AM -0600, Tom Rini wrote:
> On Wed, Jun 26, 2024 at 09:00:42AM +0100, Simon Glass wrote:
> > Hi Tom,
> >
> > On Tue, 25 Jun 2024 at 15:14, Tom Rini wrote:
> > >
> > > On Tue, Jun 25, 2024 at 01:38:00PM +0100, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Mo
On Wed, Jun 26, 2024 at 09:00:41AM +0100, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 25 Jun 2024 at 15:14, Tom Rini wrote:
> >
> > On Tue, Jun 25, 2024 at 01:38:04PM +0100, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 24 Jun 2024 at 19:29, Tom Rini wrote:
> > > >
> > > > On Sun, Jun 23, 20
On Wed, Jun 26, 2024 at 09:00:33AM +0100, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 25 Jun 2024 at 15:27, Tom Rini wrote:
> >
> > On Tue, Jun 25, 2024 at 01:38:08PM +0100, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 24 Jun 2024 at 19:13, Tom Rini wrote:
> > > >
> > > > On Sun, Jun 23, 20
Hi Jonas,
On Mon, 24 Jun 2024 at 09:53, Jonas Karlman wrote:
>
> Hi Simon,
>
> On 2024-06-23 19:53, Simon Glass wrote:
> > The code here is confusing due to large blocks which are #ifdefed out.
> > Add a function phase_sdram_init() which returns whether SDRAM init
> > should happen in the current
Hi Quentin,
On Mon, 24 Jun 2024 at 09:24, Quentin Schulz wrote:
>
> Hi Simon,
>
> On 6/23/24 7:53 PM, Simon Glass wrote:
> > The code here is confusing due to large blocks which are #ifdefed out.
> > Add a function phase_sdram_init() which returns whether SDRAM init
> > should happen in the curre
On Tue, Jun 25, 2024 at 09:20:54PM +0200, Christophe Leroy wrote:
>
>
> Le 25/06/2024 à 17:19, Tom Rini a écrit :
> > On Tue, Jun 25, 2024 at 03:12:38PM +, LEROY Christophe wrote:
> > > Hi All,
> > >
> > > Le 24/06/2024 à 21:30, Tom Rini a écrit :
> > > > Hey all,
> > > >
> > > > Well, once
Fix the issue where CONFIG_SYS_BOARD was incorrectly set on
Odroid XU3 boards, causing boot failure. This was resolved by
correcting the SYS_BOARD entry in Kconfig to load the correct
device tree source (dts) for the Odroid Exynos5422 Platforms.
Fixes: f76750d11133 ("Convert CONFIG_CONS_INDEX et a
Resolved a compilation issue where the build system attempted
to compile for the Odroid-XU3 platform instead of the specified
Exynos4412 platform due to an incorrect CONFIG_SYS_BOARD setting.
Updated the Makefile to ensure that compilation only occurs for
the Odroid-XU3 specified target platform.
On Wed, Jun 26, 2024 at 10:15 AM Anand Moon wrote:
>
> Fix the issue where CONFIG_SYS_BOARD was incorrectly set on
> Odroid XU3 boards, causing boot failure. This was resolved by
> correcting the SYS_BOARD entry in Kconfig to load the correct
> device tree source (dts) for the Odroid Exynos5422 Pl
On Wed, Jun 26, 2024 at 10:15 AM Anand Moon wrote:
>
> Resolved a compilation issue where the build system attempted
> to compile for the Odroid-XU3 platform instead of the specified
> Exynos4412 platform due to an incorrect CONFIG_SYS_BOARD setting.
> Updated the Makefile to ensure that compilati
On 24/06/2024 17:47, Tim Harvey wrote:
On Thu, Jun 20, 2024 at 6:58 AM Caleb Connolly
wrote:
Hi Tim,
On 18/06/2024 23:06, Tim Harvey wrote:
If RANDOMIZE_BASE is enabled in the Linux kernel instructing it to
randomize the virtual address at which the kernel image is loaded, it
expects entr
This series includes fixes to get some rockchip and nvidia boards
working again. It also drops the broken Beaglebone Black config and
provides a devicetree fix for coral (x86).
Note that since this series fixes bugs, it is targeted at -master
Changes in v5:
- Move setting of pmugrf into the probe
Tools should have an option to obtain the version, so add this to the
mkeficapsule tool.
Signed-off-by: Simon Glass
---
(no changes since v1)
doc/mkeficapsule.1 | 4
tools/mkeficapsule.c | 8 +++-
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/doc/mkeficapsule.1 b/do
Tools cannot be assumed to be present. Add a check for this with the
mkeficpasule tool.
Signed-off-by: Simon Glass
Fixes: b617611b27a ("binman: capsule: Add support for generating...")
---
(no changes since v1)
tools/binman/etype/efi_capsule.py | 4
1 file changed, 4 insertions(+)
diff -
Now that this tool has a version number, collect it.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/binman/btool/mkeficapsule.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/binman/btool/mkeficapsule.py
b/tools/binman/btool/mkeficapsule.py
index ef1d
The tool must return an error code when invalid arguments are provided,
otherwise binman has no way of knowing that anything went wrong.
Correct this.
Signed-off-by: Simon Glass
Fixes: fab430be2f4 ("tools: add mkeficapsule command for UEFI...")
---
(no changes since v1)
tools/mkeficapsule.c |
There is no need to remove input files. It makes it harder to diagnose
failures. Keep the payload file.
There is no test for this condition, but one could be added.
Signed-off-by: Simon Glass
Acked-by: Sughosh Ganu
---
(no changes since v4)
Changes in v4:
- Drop Fixes tag
tools/binman/etype
This cannot be enabled early in boot since some other init is needed.
At this point it is unclear exactly what init is needed, so disable
the debug UART to avoid a hang.
Signed-off-by: Simon Glass
---
(no changes since v1)
configs/nyan-big_defconfig | 1 -
1 file changed, 1 deletion(-)
diff -
Set a size limit for this board so that we get a build error if it grows
too much.
Note that the limit is approximately, since it does not include the FDT,
microcode and fdtmap, which can change in size. However this board is
fairly stable, so overflowing this limit will likely result in the image
With a recent change, regulators_enable_boot_on() returns an error if a
regulator is already set. Check for and handle this situation.
Fixes: d99fb64a98a power: regulator: Only run autoset once for each regulator
Reviewed-by: Jonas Karlman
Reviewed-by: Quentin Schulz
Signed-off-by: Simon Glass
It does not make sense to enable all SHA algorithms unless they are
needed. It bloats the code and in this case, causes chromebook_link to
fail to build. That board does use the TPM, but not with measured boot,
nor EFI.
Since EFI_TCG2_PROTOCOL already selects these options, we just need to
add the
Add better logging for power init so that CONFIG_LOG_ERROR_RETURN can
be enabled.
Signed-off-by: Simon Glass
Reviewed-by: Quentin Schulz
---
(no changes since v2)
Changes in v2:
- Remove the superfluous if() and drop the debug() as well
board/google/veyron/veyron.c | 30 -
On some boards, the bloblist is created in SPL once SDRAM is ready. It
cannot be accessed until that point, so is not available early in SPL.
Add a condition to avoid a hang in this case.
This fixes a hang in chromebook_coral
Fixes: 70fe2385943 ("fdt: Allow the devicetree to come from a bloblist
The dcache may not be enabled in SPL. Add a check to avoid trying to
use an undefined function.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
---
(no changes since v1)
common/spl/spl_atf.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/common/spl/spl_atf.c b/common/s
On Tue, Jun 25, 2024 at 1:02 AM Jerome Forissier
wrote:
>
> On 6/25/24 00:28, Tim Harvey wrote:
> > On Sat, Jun 22, 2024 at 1:09 AM Maxim Uvarov wrote:
> >>
> >> пт, 21 июн. 2024 г. в 21:42, Fabio Estevam :
> >>>
> >>> Hi Tim and Jerome,
> >>>
> >>> On Fri, Jun 21, 2024 at 1:08 PM Tim Harvey wro
At present gd->ram_size is 0 in SPL, meaning that it is not possible to
enable the cache. Correct this by always populating the RAM size
correctly.
This increases code size by about 500 bytes in SPL, since it must call
the rather large rockchip_sdram_size() function.
Signed-off-by: Simon Glass
R
The code here is confusing due to large blocks which are #ifdefed out.
Add a function phase_sdram_init() which returns whether SDRAM init
should happen in the current phase, using that as needed to control the
code flow.
This increases code size by about 500 bytes in SPL when the cache is on,
sinc
This causes a hang, so disable it. Unfortunately the RAM-size fix does
not resolve the problem and I am unsure what is wrong. As soon as the
cache is enabled the board appears to hang.
Fixes: 6d8cdfd1536 ("rockchip: spl: Enable caches to speed up checksum
validation")
Signed-off-by: Simon Glass
Now that am335x_evm boots OK on the Beaglebone black, drop the latter
and update the docs to cover the change.
Also add a few updates about 'make fit' and drop the note about the
security review, as U-Boot's verified boot has had quite extensive
review now.
Signed-off-by: Simon Glass
Reviewed-by
Hi Simon,
On 2024-06-26 16:54, Simon Glass wrote:
> Hi Jonas,
>
> On Mon, 24 Jun 2024 at 09:53, Jonas Karlman wrote:
>>
>> Hi Simon,
>>
>> On 2024-06-23 19:53, Simon Glass wrote:
>>> The code here is confusing due to large blocks which are #ifdefed out.
>>> Add a function phase_sdram_init() whic
Hi Simon,
On 2024-06-26 17:59, Simon Glass wrote:
> The code here is confusing due to large blocks which are #ifdefed out.
> Add a function phase_sdram_init() which returns whether SDRAM init
> should happen in the current phase, using that as needed to control the
> code flow.
>
> This increases
On Wed, Jun 26, 2024 at 04:59:29PM +0100, Simon Glass wrote:
> This series includes fixes to get some rockchip and nvidia boards
> working again. It also drops the broken Beaglebone Black config and
> provides a devicetree fix for coral (x86).
>
> Note that since this series fixes bugs, it is tar
Hi Sam,
On Wed, 19 Jun 2024 at 02:26, Sam Protsenko wrote:
>
> If there are no new comments on this series, can you please apply it?
>
> Thanks!
Tested on Odroid XU4 and Odrroid U3 boards
Please add my
Reviewed-by: Anand Moon
Tested-by: Anand Moon
Thanks
-Anand
Am 26.06.24 um 10:00 schrieb Simon Glass:
Can you please add a PR here?
https://github.com/open-source-firmware/flat-image-tree
In that copy, the property is already conditionally mandatory.
Am 15. Juni 2024 11:34:56 MESZ schrieb Frank Wunderlich :
>From: Frank Wunderlich
>
>RAM init on mt7622 based bananapi R64 is broken since v2023.10.
>
>Increasing the mem-map does not help here, so i reduced the maximum
>available ram in get_ram_size call from 2G to 1G (board has only 1G).
>
>Fixe
Insert /u-boot, = property into the U-Boot control DT
during SPL DTO application process. This can be used by user to inspect
which DTOs got applied by the SPL and in which order from running U-Boot.
Example:
```
u-boot=> fdt addr $fdtcontroladdr && fdt list /
Working FDT set to aee9aeb0
/ {
Enable 'cat' command to print file from filesystem to stdout.
Enable 'xxd' command to hexdump file from filesystem to stdout.
Signed-off-by: Marek Vasut
---
Cc: "NXP i.MX U-Boot Team"
Cc: Fabio Estevam
Cc: Stefano Babic
Cc: u-b...@dh-electronics.com
Cc: u-boot@lists.denx.de
---
configs/imx8mp
Enable PCA953x GPIO expander driver in DH i.MX8MP DHCOM PDK2 configuration.
The PCA9539 GPIO expander is used on production DH i.MX8MP DHCOM SoM rev.200.
This is already enabled in DH i.MX8MP DHCOM PDK3 configuration so align the
two configurations.
Fixes: 9de599ec3d59 ("arm64: dts: imx8mp: Update
The production DH i.MX8MP DHCOM SoM rev.200 uses updated PHY MDIO addresses
for the Fast ethernet PHYs. Update the base SoM DT and SoM rev.100 backward
compatibility DTO to cater for this change.
Since the MDIO address adjustment is now also in the rev.100 SoM DTO, not
only in the rev.100 PDK3 DTO
On Wed, 19 Jun 2024 06:34:50 -0600, Simon Glass wrote:
> Show which boot protocol is being used.
>
>
Applied to u-boot/next, thanks!
--
Tom
In case a regulator DT node contains regulator-always-on or regulator-boot-on
property, make sure the regulator gets correctly configured by U-Boot on start
up. Unconditionally probe such regulator drivers. This is a preparatory patch
for introduction of .regulator_post_probe() which would trigger
Turn regulators_enable_boot_on() and regulators_enable_boot_off() into
empty functions. Implement matching functionality in regulator_post_probe()
instead. The regulator_post_probe() is called for all regulators after they
probe, and regulators that have regulator-always-on or regulator-boot-on DT
This function is never called, drop it.
Signed-off-by: Marek Vasut
---
Cc: Ben Wolsieffer
Cc: Caleb Connolly
Cc: Chris Morgan
Cc: Dragan Simic
Cc: Eugen Hristev
Cc: Francesco Dolcini
Cc: Heinrich Schuchardt
Cc: Jaehoon Chung
Cc: Jagan Teki
Cc: Jonas Karlman
Cc: Kever Yang
Cc: Kostya Po
Both regulators_enable_boot_on/off() are unused and superseded by
regulator uclass regulator_post_probe(). Remove both functions.
Signed-off-by: Marek Vasut
---
Cc: Ben Wolsieffer
Cc: Caleb Connolly
Cc: Chris Morgan
Cc: Dragan Simic
Cc: Eugen Hristev
Cc: Francesco Dolcini
Cc: Heinrich Schuc
71 matches
Mail list logo
