Hi Andrew,
On 09:55-20240104, Andrew Davis wrote:
> On 1/4/24 1:52 AM, Manorit Chawdhry wrote:
> > Hi Andrew, Simon,
> >
> > On 08:58-20240102, Andrew Davis wrote:
> > > On 12/31/23 6:48 AM, Simon Glass wrote:
> > > > Hi,
> > > >
>
From: Ion Agorria
The dollar test was merged with bagous console behavior, and
instead of fixing it, this behavior was just workarounded.
It seems like without the fix the ut_assert_skipline(); didn't clear
console and running ut_assert_skipline(); many times would give always
OK. With
lib:
From: Ion Agorria
"oem console" serves to read console record buffer.
Signed-off-by: Ion Agorria
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Mattijs Korpershoek
---
doc/android/fastboot.rst | 1 +
drivers/fastboot/Kconfig | 7 +++
drivers/fastboot/fb_command.c | 39
From: Ion Agorria
If line overflows readline it will not be returned, fix this behavior,
make it optional and documented properly.
Signed-off-by: Ion Agorria
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Mattijs Korpershoek
Reviewed-by: Simon Glass
---
boot/bootmeth_extlinux.c | 2 +-
From: Ion Agorria
Set flag to enable console record on console_record_init
and not only on console_record_reset_enable. This fixes
missing start of U-Boot log for fastboot oem console
command.
Signed-off-by: Ion Agorria
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Mattijs Korpershoek
---
From: Ion Agorria
This commit implements "fastboot getvar all" listing
by iterating the existing dispatchers that don't require
parameters (as we pass NULL), uses fastboot multiresponse.
Signed-off-by: Ion Agorria
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Mattijs Korpershoek
---
From: Ion Agorria
Add console_record_isempty to check if console record buffer
contains any data.
Signed-off-by: Ion Agorria
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Mattijs Korpershoek
---
common/console.c | 5 +
include/console.h | 13 +
2 files changed, 18
From: Ion Agorria
Currently u-boot fastboot can only send one message back to host,
so if there is a need to print more than one line messages must be
kept sending until all the required data is obtained. This behavior
can be adjusted using multiresponce ability (getting multiple lines
of
Currently u-boot fastboot can only send one message back to host,
so if there is a need to print more than one line messages must be
kept sending until all the required data is obtained. This behavior
can be adjusted using multiresponce ability (getting multiple lines
of response) proposed in this
Hi Nishanth
On 04/01/24 20:51, Nishanth Menon wrote:
On 13:23-20240104, Neha Malcom Francis wrote:
Use yamllint for checking whether YAML configuration files are adhering
to default yamllint rules.
Signed-off-by: Neha Malcom Francis
Suggested-by: Nishanth Menon
---
tools/binman/etype
On Fri, 29 Dec 2023 16:16:24 +0530, Manorit Chawdhry wrote:
> K3 devices have firewalls that are used to prevent illegal accesses to
> memory regions that are deemed secure. The series prevents the illegal
> accesses to ATF and OP-TEE regions that are present in different K3
> devices.
>
>
Hi Dominik,
The main dts should come from kernel, does this board available in
mainline kernel?
If yes, pls add the info in commit message for which tag from kernel.
This is a SoM, then is there a mainboard needed to make it work?
Thanks,
- Kever
On 2024/1/4 23:57, Dominik Poggel wrote:
From: Bin Meng
With latest coreboot (e.g.: v4.22.01), the instructions to enable
graphics support has changed. Refresh the doc.
Signed-off-by: Bin Meng
---
doc/board/coreboot/coreboot.rst | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git
Hi Simon,
On Thu, Jan 4, 2024 at 11:11 PM Simon Glass wrote:
>
> U-Boot provides support for editing settings with an 'expo', as well as
> reading and writing settings to CMOS RAM.
>
> This series integrates expo functionality with coreboot, using the
> sysinfo table to get a list of settings,
Andrew Davis writes:
* uEnv.txt processing
>>>
>>> What command can do this?
>>>
>>
>> run envboot;
>>
>> https://source.denx.de/u-boot/u-boot/-/blob/master/include/env/ti/mmc.env?ref_type=heads#L20
>
> This could be a new bootmeth which looks
Hi Rob,
On Thu, Dec 14, 2023 at 2:09 PM Simon Glass wrote:
>
> Hi Rob,
>
> On Thu, 14 Dec 2023 at 10:27, Rob Herring wrote:
> >
> > On Fri, Dec 08, 2023 at 03:58:10PM -0700, Simon Glass wrote:
> > > Hi Rob,
> > >
> > > On Fri, 8 Dec 2023 at 14:56, Rob Herring wrote:
> > > >
> > > > On Fri, Dec
> -Original Message-
> From: Ard Biesheuvel
> Sent: Thursday, January 4, 2024 12:43 AM
> To: Chiu, Chasel
> Cc: Simon Glass ; devicet...@vger.kernel.org; Mark Rutland
> ; Rob Herring ; Tan, Lean Sheng
> ; lkml ; Dhaval
> Sharma ; Brune, Maximilian
> ; Yunhui Cui ;
> Dong, Guo ; Tom
On Thu, Jan 4, 2024 at 12:02 PM Maxim Uvarov wrote:
> CI tests this in all qemu emulated boards. I tested it locally on Raspberry
> Pi - works well. This version did not
> yet tested on imx8, but the previous version worked on eth0, did not work on
> eth1. So I plan to continue testing
>
Each partition may belong to an image, which has a name. That name can
be useful for debugging as it helps identify where the partition came
from.
Signed-off-by: Brandon Maier
---
tools/zynqmpimage.c | 48
tools/zynqmpimage.h | 49
Extract partitions from a Xilinx Boot Image using dumpimage.
Add helper for_each_zynqmp_part() to reuse the partition walking code
between the printing and extracting functions.
Signed-off-by: Brandon Maier
---
tools/zynqmpimage.c | 57 +---
Two of the partition size fields are not printed. Currently only the
"total" size is displayed, which is the size of the image data
(encrypted), padding, expansion, and authentication data. Add the
"unencrypted data" size, which is the original size of the data before
being encrypted. And
The zynqmpimage_print_header() skips printing the first partition. This
is because the image header can contain duplicate fields as the first
partition. However some fields, like the partition attributes, are only
present in the partition table. It is also possible for the first
partition to not
On Thu, Jan 04, 2024 at 04:50:14PM +0100, Michal Simek wrote:
>
>
> On 1/4/24 16:30, Tom Rini wrote:
> > On Thu, Jan 04, 2024 at 03:45:10PM +0100, Michal Simek wrote:
> > > Hi Tom,
> > >
> > > On 1/4/24 14:50, Tom Rini wrote:
> > > > On Thu, Jan 04, 2024 at 06:52:32PM +0530, Sumit Garg wrote:
>
On Thu, Jan 4, 2024 at 12:54 PM Mathieu Othacehe wrote:
>
> From: Mathieu Othacehe
>
> Hello,
>
> This v5 fixes imx93_evk compilation by enabling binman support for this board.
Still fails:
https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/764792
Please run a CI job for your series
On 2024-01-04 18:12, Caleb Connolly wrote:
When attempting to probe a device which has an associated IOMMU, if the
IOMMU device can't be found (no driver, disabled driver, driver failed
to probe, etc) then we currently fail to probe the device with no
discernable error.
If we fail to hook the
Hello,
It seems like without the fix the ut_assert_skipline(); didn't clear
console and running ut_assert_skipline(); many times would give always
OK. With my fix the line is cleared correctly and next assert fails
because now there is nothing to clean which is correct if we look the
this a bit
Hi,
On 1/4/24 13:37, Patrice Chotard wrote:
In SCMI configuration, usart1 is secure, so all its resources are secured
(clock and reset) and can't be set/unset by non-secure world but by OP-TEE.
Fixes: 68d396bf ("ARM: dts: stm32: add SCMI version of STM32 boards
(DK1/DK2/ED1/EV1)")
When attempting to probe a device which has an associated IOMMU, if the
IOMMU device can't be found (no driver, disabled driver, driver failed
to probe, etc) then we currently fail to probe the device with no
discernable error.
If we fail to hook the device up to its IOMMU, we should make sure
On 2024-01-04 17:03, Caleb Connolly wrote:
Sometimes, when only one bootdev is available, and it fails to probe,
we
end up in an infinite loop calling probe() on the same device over and
over. With only debug level log output.
Break the loop if we fail to probe the same device twice in a row,
чт, 4 січ. 2024 р. о 17:00 Mattijs Korpershoek пише:
>
> Hello Svyatoslav,
>
> On jeu., déc. 28, 2023 at 20:01, Svyatoslav Ryhel wrote:
>
> > Currently u-boot fastboot can only send one message back to host,
> > so if there is a need to print more than one line messages must be
> > kept sending
Hi Simon,
On 04/01/2024 16:06, Simon Glass wrote:
> Hi Caleb,
>
> On Thu, Jan 4, 2024 at 9:03 AM Caleb Connolly
> wrote:
>>
>> Sometimes, when only one bootdev is available, and it fails to probe, we
>> end up in an infinite loop calling probe() on the same device over and
>> over. With only
From: Mathieu Othacehe
Add support for the Variscite VAR-SOM-IMX93 evaluation kit. The SoM
consists of an NXP iMX93 dual A55 CPU. The SoM is mounted on a Variscite
Symphony SBC.
Signed-off-by: Mathieu Othacehe
---
arch/arm/dts/Makefile |3 +-
From: Mathieu Othacehe
Signed-off-by: Mathieu Othacehe
---
arch/arm/dts/imx93-11x11-evk-u-boot.dtsi | 2 +
arch/arm/mach-imx/imx9/Kconfig | 1 +
configs/imx93_11x11_evk_defconfig| 2 +
configs/imx93_11x11_evk_ld_defconfig | 2 +
doc/board/nxp/imx93_11x11_evk.rst
From: Mathieu Othacehe
Add dedicated Makefile targets for the i.MX93 and a new imx93-u-boot.dtsi
device-tree to create binman images.
Signed-off-by: Mathieu Othacehe
---
arch/arm/dts/imx93-u-boot.dtsi | 88
arch/arm/mach-imx/Makefile | 22 ++-
From: Mathieu Othacehe
This is extending commit 6516c9b349b3 ("spl: binman: Disable u_boot_any
symbols for i.MX8M boards") to i.MX93 boards.
Signed-off-by: Mathieu Othacehe
---
common/spl/Kconfig | 2 +-
common/spl/Kconfig.tpl | 2 +-
common/spl/Kconfig.vpl | 2 +-
3 files changed, 3
From: Mathieu Othacehe
Hello,
This v5 fixes imx93_evk compilation by enabling binman support for this board.
Thanks,
Mathieu
v4: https://lists.denx.de/pipermail/u-boot/2024-January/542515.html
Mathieu Othacehe (4):
spl: binman: Disable u_boot_any symbols for i.MX93 boards
mach-imx: Add
Hello,
> https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/764727
>
> Take a look at the xilinx_zynqmp_virt and imx8mm-cl-iot-gate errors,
> for example.
Due to multi-threaded testing the output is a bit hard to read but I
think that those configs are working fine.
The faulty config
Hi Caleb,
On Thu, Jan 4, 2024 at 9:03 AM Caleb Connolly wrote:
>
> Sometimes, when only one bootdev is available, and it fails to probe, we
> end up in an infinite loop calling probe() on the same device over and
> over. With only debug level log output.
>
> Break the loop if we fail to probe
Sometimes, when only one bootdev is available, and it fails to probe, we
end up in an infinite loop calling probe() on the same device over and
over. With only debug level log output.
Break the loop if we fail to probe the same device twice in a row, and
promote the probe failure message to
Hi,
On Thu, Jan 4, 2024 at 5:19 AM E Shattow wrote:
>
> Hello,
>
> There is data corruption when using booti on a JH7110 (riscv64) board to
> load (over tftp or ymodem) a compressed kernel, compressed initrd, and
> device tree blob, when the data are too close together (even though not
>
Sometimes, when only one bootdev is available, and it fails to probe, we
end up in an infinite loop calling probe() on the same device over and
over. With only debug level log output.
Break the loop if we fail to probe the same device twice in a row, and
promote the probe failure message to
On 1/4/24 1:52 AM, Manorit Chawdhry wrote:
Hi Andrew, Simon,
On 08:58-20240102, Andrew Davis wrote:
On 12/31/23 6:48 AM, Simon Glass wrote:
Hi,
On Wed, Nov 29, 2023 at 7:48 PM Simon Glass wrote:
Hi Andrew,
On Mon, 6 Nov 2023 at 11:05, Andrew Davis wrote:
On 11/6/23 11:47 AM, Simon
On 1/4/24 16:30, Tom Rini wrote:
On Thu, Jan 04, 2024 at 03:45:10PM +0100, Michal Simek wrote:
Hi Tom,
On 1/4/24 14:50, Tom Rini wrote:
On Thu, Jan 04, 2024 at 06:52:32PM +0530, Sumit Garg wrote:
Hi Michal,
On Thu, 4 Jan 2024 at 15:39, Michal Simek wrote:
On 1/3/24 17:32, Tom Rini
On Thu, Dec 21, 2023 at 06:34:21PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Move all generic (NVMEM devices independent) code from NVMEM device
> driver to NVMEM layout driver. Then add a simple NVMEM layout code on
> top of it.
>
> Thanks to proper layout it's possible to support
On Thu, Jan 04, 2024 at 03:45:10PM +0100, Michal Simek wrote:
> Hi Tom,
>
> On 1/4/24 14:50, Tom Rini wrote:
> > On Thu, Jan 04, 2024 at 06:52:32PM +0530, Sumit Garg wrote:
> > > Hi Michal,
> > >
> > > On Thu, 4 Jan 2024 at 15:39, Michal Simek wrote:
> > > >
> > > >
> > > >
> > > > On 1/3/24
On 13:23-20240104, Neha Malcom Francis wrote:
> Use yamllint for checking whether YAML configuration files are adhering
> to default yamllint rules.
>
> Signed-off-by: Neha Malcom Francis
> Suggested-by: Nishanth Menon
> ---
> tools/binman/etype/ti_board_config.py
Hi Tom,
On Wed, 3 Jan 2024 at 14:08, Tom Rini wrote:
> On Tue, Jan 02, 2024 at 02:12:29PM -0800, Raymond Mao wrote:
>
> > Save boot arguments r[0-3] into an array for handover of bloblist from
> > previous boot stage.
> >
> > Signed-off-by: Raymond Mao
> > ---
> > Changes in v2
> > - New patch
Coreboot provides the CMOS layout in the tables it passes to U-Boot.
Use that to build an editor for the CMOS settings.
Signed-off-by: Simon Glass
---
Changes in v2:
- Avoid using common.h
boot/Makefile | 4 +
boot/expo_build_cb.c| 245
The real-time clock is needed for most X86 systems and it is useful to
be able to read from it. Enable the rtc command by default.
Signed-off-by: Simon Glass
---
Changes in v2:
- Rebase to -next
cmd/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index
Coreboot tables provide information about the CMOS-RAM checksum. Add a
command which can check and update this.
With this it is possible to adjust CMOS-RAM settings and tidy up the
checksum afterwards.
Signed-off-by: Simon Glass
---
Changes in v2:
- Avoid using common.h
cmd/Kconfig
Enable cedit support along with required options and a simple style.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/dts/coreboot.dts| 7 +++
configs/coreboot64_defconfig | 2 ++
configs/coreboot_defconfig | 2 ++
3 files changed, 11 insertions(+)
diff --git
Add a simple test for this command, checking that coreboot has the
required features.
Signed-off-by: Simon Glass
---
(no changes since v1)
test/cmd/Makefile | 1 +
test/cmd/coreboot.c | 36
2 files changed, 37 insertions(+)
create mode 100644
Update the cbsysinfo command to show the contents of the CMOS option
table.
While we are here, add some example output for this command, along with
mention of what the unimplemented tags are.
Signed-off-by: Simon Glass
---
(no changes since v1)
cmd/x86/cbsysinfo.c | 73
Enable unit tests so we can run command-line tests in coreboot. Enable
console recording, with enough space for the 'cbsysinfo' command. Add
to the pre-relocation malloc() space to make room for this.
Signed-off-by: Simon Glass
---
(no changes since v1)
configs/coreboot_defconfig | 4
1
At present menu items are stored according to their sequence number in
the menu. In some cases we may want to have holes in that sequence, or
not use a sequence at all.
Add a new 'value' property for menu items. This will be used for
reading and writing, if present. If there is no 'value'
Update to a newer version which supports settings in CMOS RAM.
Signed-off-by: Simon Glass
---
(no changes since v1)
.azure-pipelines.yml | 2 +-
.gitlab-ci.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index
Update the cedit read/write functions to support menu items with
values.
Signed-off-by: Simon Glass
---
(no changes since v1)
boot/cedit.c| 148 +---
boot/scene_menu.c | 2 +-
doc/usage/cmd/cedit.rst | 15 +++-
The scene_txt_str() function calls expo_str() so there is no need to
call it beforehand. Drop this unnecessary code.
Signed-off-by: Simon Glass
---
(no changes since v1)
boot/expo_build.c | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git a/boot/expo_build.c
This function is really just an assignment, so serves no useful
purpose. Drop it.
Signed-off-by: Simon Glass
---
(no changes since v1)
boot/expo_build.c | 4 ++--
boot/scene.c | 7 ---
include/expo.h| 9 -
test/boot/expo.c | 2 +-
4 files changed, 3 insertions(+), 19
Set aside some expo IDs for 'save' and 'discard' buttons. This avoids
needing to store the IDs for these. Adjust the documentation and expo
tool for the new EXPOID_BASE_ID value.
Ignore these objects when saving and loading the cedit, since they do
not contain real data.
Adjust 'cedit run' to
Add some more logging in the CMOS read/write code. Tidy up a few
comments while we are here.
Signed-off-by: Simon Glass
---
(no changes since v1)
boot/cedit.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/boot/cedit.c b/boot/cedit.c
index a53a4f28990..cc1d5b76357
At present a fixed position is used for menu items, 200 pixels to the
right of the left side of the labels. This means that a menu item with
a very long label may overlap the items.
It seems better to calculate the maximum label width and then place the
items to the right of all of them.
To
If expo_set_dynamic_start() is never called, the first scene created
will have an ID of 0, which is invalid. Correct this by setting a
default value.
Add a test to check this.
Signed-off-by: Simon Glass
---
(no changes since v1)
boot/expo.c | 1 +
test/boot/expo.c | 23
Some files may include this header file without first including dm.h
so add a forward declaration.
Signed-off-by: Simon Glass
---
(no changes since v1)
include/cedit.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/cedit.h b/include/cedit.h
index f43cafa5aa2..f9a4a6d9e8e 100644
When starting a new text line, an assumption is made that the current
vertical position is a multiple of the character height. When this is
not true, characters can be written after the end of the framebuffer.
This can causes crashes and strange errors from QEMU.
Adjust the scrolling check when
This is useful for highlighting something with a black background, as
is needed with cedit when using a white-on-black console. Add this as
a new colour.
Signed-off-by: Simon Glass
---
(no changes since v1)
boot/scene.c | 2 +-
drivers/video/video-uclass.c | 3 +++
U-Boot provides support for editing settings with an 'expo', as well as
reading and writing settings to CMOS RAM.
This series integrates expo functionality with coreboot, using the
sysinfo table to get a list of settings, creating an expo with them and
allowing them to be edited.
A new CI test
Expand the ROM for x86_64 to 2MB to make space for the font, as it is
already on the edge.
Signed-off-by: Simon Glass
---
(no changes since v1)
board/emulation/qemu-x86/Kconfig | 3 ++-
configs/qemu-x86_64_defconfig| 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git
Enable this feature to provide a larger font choice and more attractive
menus. Expand the ROM for x86_64 to 2MB to make space for the font.
Signed-off-by: Simon Glass
---
Changes in v6:
- Move 'Avoid unbinding devices in use by bootflows' to another series
Changes in v3:
- Add new patch to
Saving and restoring entries is used for expo and for the command line,
which we don't use in SPL. Drop these methods.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
Reviewed-by: Anatolij Gustschin
---
(no changes since v3)
Changes in v3:
- Add new patch to drop unnecessary truetype
Truetype fonts look better in the menu, so enable them.
Signed-off-by: Simon Glass
---
(no changes since v3)
Changes in v3:
- Add new patch to enable truetype fonts in coreboot
arch/x86/dts/coreboot.dts| 10 ++
configs/coreboot64_defconfig | 1 +
configs/coreboot_defconfig |
This is needed to support Truetype fonts. In any case, the compiler
expects SSE to be available in 64-bit mode. Provide an option to enable
SSE so that hardware floating-point arithmetic works.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
Suggested-by: Bin Meng
---
(no changes since v4)
The ANSI codes are not correctly handled at present, in that the
requested X position is added to the current one.
Correct this and also call vidconsole_entry_start() to start a new text
line.
Signed-off-by: Simon Glass
Reviewed-by: Anatolij Gustschin
---
(no changes since v1)
Provide the user with a list of available boot options. Selecting one
causes it to be booted. Pressing causes U-Boot to return to the
command-line prompt.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
Changes in v6:
- Rebase to -next
Changes in v3:
- Clear the screen before booting
This little series reprises the EFI-video fix, fixes a USB problem and
enables a boot script for coreboot.
It also moves to truetype fonts for coreboot and qemu-x86, since the
menus look much better and there are no strong size constraints.
With these changes it is possible to boot a Linux
Hi Bin,
On Thu, Jan 4, 2024 at 5:06 AM Bin Meng wrote:
>
> Hi Simon,
>
> On Sun, Dec 31, 2023 at 8:43 PM Simon Glass wrote:
> >
> > Hi Bin,
> >
> > On Sun, Dec 31, 2023 at 2:59 AM Bin Meng wrote:
> > >
> > > Hi Simon,
> > >
> > > On Wed, Nov 15, 2023 at 9:24 PM Simon Glass wrote:
> > > >
> >
Hi Simon,
On mer., janv. 03, 2024 at 18:38, Simon Glass wrote:
> Hi Mattijs,
>
> On Wed, Jan 3, 2024 at 5:41 AM Mattijs Korpershoek
> wrote:
>>
>> Hi Simon,
>>
>> On Tue, Jan 02, 2024 at 07:06, Simon Glass wrote:
>>
>> > Hi Mattijs,
>> >
>> > On Tue, Jan 2, 2024 at 2:52 AM Mattijs Korpershoek
On Wed, 3 Jan 2024 at 20:30, Fabio Estevam wrote:
> Hi Maxim,
>
> On Tue, Jan 2, 2024 at 2:31 PM Maxim Uvarov
> wrote:
> >
> > Small update here. I made changes without any board limit size changes.
> > Reordered patches to make them compile in sequence. I think I will do one
> > more clean up
Hello Svyatoslav,
On jeu., déc. 28, 2023 at 20:01, Svyatoslav Ryhel wrote:
> Currently u-boot fastboot can only send one message back to host,
> so if there is a need to print more than one line messages must be
> kept sending until all the required data is obtained. This behavior
> can be
Hi Tom,
On 1/4/24 14:50, Tom Rini wrote:
On Thu, Jan 04, 2024 at 06:52:32PM +0530, Sumit Garg wrote:
Hi Michal,
On Thu, 4 Jan 2024 at 15:39, Michal Simek wrote:
On 1/3/24 17:32, Tom Rini wrote:
On Wed, Jan 03, 2024 at 09:19:40AM -0700, Rob Herring wrote:
On Thu, Dec 28, 2023 at 4:59 AM
Hi Mathieu,
On Thu, Jan 4, 2024 at 6:14 AM Mathieu Othacehe wrote:
>
> From: Mathieu Othacehe
>
> Hello,
>
> This v4 rebases the series on top of the next branch and fixes Fabio's
> remarks.
I ran your v4 series through CI, but it failed:
On Thu, 4 Jan 2024 at 03:49, Simon Glass wrote:
>
> Standard passage provides for a bloblist to be passed from one firmware
> phase to the next. That can be used to pass the devicetree along as well.
> Add an option to support this.
>
> Tests for this will be added as part of the Universal
On Wed, Jan 03, 2024 at 06:49:19PM -0700, Simon Glass wrote:
> Standard passage provides for a bloblist to be passed from one firmware
> phase to the next. That can be used to pass the devicetree along as well.
> Add an option to support this.
>
> Tests for this will be added as part of the
On Thu, Jan 04, 2024 at 06:52:32PM +0530, Sumit Garg wrote:
> Hi Michal,
>
> On Thu, 4 Jan 2024 at 15:39, Michal Simek wrote:
> >
> >
> >
> > On 1/3/24 17:32, Tom Rini wrote:
> > > On Wed, Jan 03, 2024 at 09:19:40AM -0700, Rob Herring wrote:
> > >> On Thu, Dec 28, 2023 at 4:59 AM Sumit Garg
Since commit b45ab9ca6621 ("CI: Update to QEMU 8.0.3"), the manual
patch applying was removed, hence there is no need to do a git user
name and email configuration.
Signed-off-by: Bin Meng
---
tools/docker/Dockerfile | 3 ---
1 file changed, 3 deletions(-)
diff --git
Hi Michal,
On Thu, 4 Jan 2024 at 15:39, Michal Simek wrote:
>
>
>
> On 1/3/24 17:32, Tom Rini wrote:
> > On Wed, Jan 03, 2024 at 09:19:40AM -0700, Rob Herring wrote:
> >> On Thu, Dec 28, 2023 at 4:59 AM Sumit Garg wrote:
> > [snip]
> >>> +In order to maintain devicetree files sync, U-Boot
On 1/4/24 13:28, Weizhao Ouyang wrote:
On Thu, Jan 4, 2024 at 8:21 PM Michal Simek wrote:
On 1/4/24 13:15, Weizhao Ouyang wrote:
On Thu, Jan 4, 2024 at 8:00 PM Michal Simek wrote:
On 1/4/24 12:46, Weizhao Ouyang wrote:
Handle the return value of spi_flash_probe_bus_cs() to avoid
On 1/4/24 05:52, Tejas Bhumkar wrote:
Enabled the default utilization of the NFS command across all Xilinx
platforms to facilitate the booting of images through the network
using the NFS protocol.
Fixes: 10de12570799 ("disable NFS support by default")
Signed-off-by: Tejas Bhumkar
---
Hi
On Thu, Jan 4, 2024 at 1:40 PM Weizhao Ouyang wrote:
>
> On Thu, Jan 4, 2024 at 8:29 PM Michael Nazzareno Trimarchi
> wrote:
> >
> > Hi
> >
> > On Thu, Jan 4, 2024 at 1:16 PM Weizhao Ouyang wrote:
> > >
> > > On Thu, Jan 4, 2024 at 8:00 PM Michal Simek wrote:
> > > >
> > > >
> > > >
> > >
On Thu, Jan 4, 2024 at 8:29 PM Michael Nazzareno Trimarchi
wrote:
>
> Hi
>
> On Thu, Jan 4, 2024 at 1:16 PM Weizhao Ouyang wrote:
> >
> > On Thu, Jan 4, 2024 at 8:00 PM Michal Simek wrote:
> > >
> > >
> > >
> > > On 1/4/24 12:46, Weizhao Ouyang wrote:
> > > > Handle the return value of
In SCMI configuration, usart1 is secure, so all its resources are secured
(clock and reset) and can't be set/unset by non-secure world but by OP-TEE.
Fixes: 68d396bf ("ARM: dts: stm32: add SCMI version of STM32 boards
(DK1/DK2/ED1/EV1)")
Signed-off-by: Patrice Chotard
---
Hi Sumit,
On 03/01/2024 13:07, Sumit Garg wrote:
> In order to avoid duplication of APQ8016 derived boards specific code,
> move common bits like USB pinctrl and fastboot to board-apq8016.c file.
> This will allow future board support like SE HMIBSC board etc to reuse it.
You still haven't
Hi
On Thu, Jan 4, 2024 at 1:16 PM Weizhao Ouyang wrote:
>
> On Thu, Jan 4, 2024 at 8:00 PM Michal Simek wrote:
> >
> >
> >
> > On 1/4/24 12:46, Weizhao Ouyang wrote:
> > > Handle the return value of spi_flash_probe_bus_cs() to avoid sf probe
> > > crashes.
> > >
> > > Signed-off-by: Weizhao
On Thu, Jan 4, 2024 at 8:21 PM Michal Simek wrote:
>
>
>
> On 1/4/24 13:15, Weizhao Ouyang wrote:
> > On Thu, Jan 4, 2024 at 8:00 PM Michal Simek wrote:
> >>
> >>
> >>
> >> On 1/4/24 12:46, Weizhao Ouyang wrote:
> >>> Handle the return value of spi_flash_probe_bus_cs() to avoid sf probe
> >>>
Hi Simon,
On Thu, 28 Dec 2023 at 20:39, Simon Glass wrote:
>
> Hi Tom, Sumit,
>
> On Thu, Dec 28, 2023 at 2:03 PM Tom Rini wrote:
> >
> > On Thu, Dec 28, 2023 at 01:37:26PM +, Simon Glass wrote:
> > > Hi Sumit,
> > >
> > > On Thu, Dec 28, 2023 at 11:58 AM Sumit Garg wrote:
> > > >
> > > >
On 1/4/24 13:15, Weizhao Ouyang wrote:
On Thu, Jan 4, 2024 at 8:00 PM Michal Simek wrote:
On 1/4/24 12:46, Weizhao Ouyang wrote:
Handle the return value of spi_flash_probe_bus_cs() to avoid sf probe
crashes.
Signed-off-by: Weizhao Ouyang
---
cmd/sf.c | 5 +++--
1 file changed, 3
From: Mathieu Othacehe
Add support for the Variscite VAR-SOM-IMX93 evaluation kit. The SoM
consists of an NXP iMX93 dual A55 CPU. The SoM is mounted on a Variscite
Symphony SBC.
Signed-off-by: Mathieu Othacehe
---
arch/arm/dts/Makefile |3 +-
From: Mathieu Othacehe
Add dedicated Makefile targets for the i.MX93 and a new imx93-u-boot.dtsi
device-tree to create binman images.
Reviewed-by: Fabio Estevam
Signed-off-by: Mathieu Othacehe
---
arch/arm/dts/imx93-u-boot.dtsi | 88 ++
From: Mathieu Othacehe
This is extending commit 6516c9b349b3 ("spl: binman: Disable u_boot_any
symbols for i.MX8M boards") to i.MX93 boards.
Reviewed-by: Fabio Estevam
Signed-off-by: Mathieu Othacehe
---
common/spl/Kconfig | 2 +-
common/spl/Kconfig.tpl | 2 +-
common/spl/Kconfig.vpl | 2
From: Mathieu Othacehe
Hello,
This v4 rebases the series on top of the next branch and fixes Fabio's
remarks.
Thanks,
Mathieu
v3: https://lists.denx.de/pipermail/u-boot/2023-December/542111.html
Mathieu Othacehe (3):
spl: binman: Disable u_boot_any symbols for i.MX93 boards
mach-imx:
1 - 100 of 122 matches
Mail list logo
