On 3/18/25 2:02 AM, Minda Chen wrote:
On 3/17/25 12:36 PM, Minda Chen wrote:
Add USB related file to Starfive visionfive2 MAINTAINERS.
The N: pattern can override this.
Signed-off-by: Minda Chen
---
board/starfive/visionfive2/MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --g
From: Tom Rini
Sent: Thursday, March 20, 2025 3:19 PM
> On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> > On 3/20/25 3:00 PM, Quentin Schulz wrote:
> > > Hi Marek,
> > >
> > > On 3/20/25 12:49 PM, Marek Vasut wrote:
> > > > On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > > > >
Jaehoon: do you mind if I just take these both through the Qualcomm tree?
If not then feel free to pick this one up
Acked-by: Caleb Connolly
On 2/27/25 09:45, Rui Miguel Silva wrote:
Add regulator driver that allow some Qualcomm PMIC to
feed VBUS output to peripherals that are connected.
S
From: Tom Rini
Sent: Thursday, March 20, 2025 7:28 PM
> On Thu, Mar 20, 2025 at 05:58:56PM +, Christoph Niedermaier wrote:
> > From: Tom Rini
> > Sent: Thursday, March 20, 2025 3:19 PM
> > > On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> > > > On 3/20/25 3:00 PM, Quentin Schul
On 3/21/25 3:00 AM, Adam Ford wrote:
On Thu, Mar 20, 2025 at 8:55 PM Marek Vasut wrote:
On 3/21/25 2:31 AM, Adam Ford wrote:
Enable CPU_IMX to register the ARM core and identify the
speed and temperature information using the driver model.
Signed-off-by: Adam Ford
I am tempted to say, impl
If the CPU Information is displayed from imx8_cpu, it displays the
cpu temperature grade and operating temperature if CONFIG_IMX9 is defined.
This behavior is similar to what happens arch/arm/mach-imx/cpu.c except that
the latter checks for CONFIG_IMX_THERMAL or CONFIG_IMX_TMU. In preparation
to m
On 3/20/25 11:32 AM, Christoph Niedermaier wrote:
If "env select" is called without a target parameter the result is
"Select Environment on : driver not found".
Why is this not the correct output ?
Improve the output
by showing a list of available evironment targets, where the active
target i
While we can be passed an image size to use, we always called qemu-img
with 20M as the size. Fix this by using the size parameter.
Signed-off-by: Tom Rini
---
Changes in v2:
- Rebase on next after the ubman series.
- Only the image size parameter not being used in all cases was a
problem, drop
According to the binding [1] the ITS node should be a subnode of the
GICv3 node. Since the ITS node has it's own driver, manually probe for
possible subnodes after binding since dm_scan_fdt() is not recursive.
1:
https://www.kernel.org/doc/Documentation/devicetree/bindings/interrupt-controller/ar
According to the binding [1] the ITS node should be a subnode of the
GICv3 node. Thus move it now that the driver binds subnodes as well.
1:
https://www.kernel.org/doc/Documentation/devicetree/bindings/interrupt-controller/arm%2Cgic-v3.txt
Signed-off-by: Patrick Rudolph
---
arch/arm/dts/qemu-s
The ACPI IORT and ACPI MADT needs to use the same IDs when referencing
GIC ITS. The GIC-v3 ITS driver uses dev_seq(dev) to generate a unique ID
for the MADT, but qemu sbsa-ref hardcodes it.
Currently it's not the same ID, breaking interrupt routing on the OS.
Don't assume it's 0 and fetch it from
Add a little more debugging to help figure out why bootflows are not
found.
Signed-off-by: Simon Glass
---
boot/bootmeth_efi.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/boot/bootmeth_efi.c b/boot/bootmeth_efi.c
index 0c9b4c3d59d..01cc7ec3bec 100644
--- a/boot/bootm
Enable CPU_IMX to register the ARM core and identify the
speed and temperature information using the driver model.
Signed-off-by: Adam Ford
---
configs/imx8mm_beacon_defconfig | 2 ++
1 file changed, 2 insertions(+)
V2: No Change
diff --git a/configs/imx8mm_beacon_defconfig b/configs/imx8mm_be
On 3/21/25 2:31 AM, Adam Ford wrote:
Enable CPU_IMX to register the ARM core and identify the
speed and temperature information using the driver model.
Signed-off-by: Adam Ford
I am tempted to say, imply this for all iMX8M and iMX9 in arch/...
Kconfig , so it gets consistently enabled for ever
On Thu, Mar 20, 2025 at 8:55 PM Marek Vasut wrote:
>
> On 3/21/25 2:31 AM, Adam Ford wrote:
> > Enable CPU_IMX to register the ARM core and identify the
> > speed and temperature information using the driver model.
> >
> > Signed-off-by: Adam Ford
> I am tempted to say, imply this for all iMX8M a
On 3/20/25 8:01 PM, Christoph Niedermaier wrote:
If tiny printf is used with 0x%08X (upper case X) the output is
always 0x. It could be confusing if upper case instead
of lower case is used intentionally or accidentally because the
actual value is not output. To avoid this confusion, trea
Enable CPU_IMX to register the ARM core and identify the
speed and temperature information using the driver model.
Signed-off-by: Adam Ford
---
configs/imx8mp_beacon_defconfig | 2 ++
1 file changed, 2 insertions(+)
V2: No Change
diff --git a/configs/imx8mp_beacon_defconfig b/configs/imx8mp_be
ADI processors require packaging with the ldr utility for bootrom
compatibility. Normally this is available as part of our yocto-derived
toolchain but it is not a part of any other premade toolchain, so it is
otherwise unavailable in the docker image for CI. This patch adds a
source build from the
On 3/12/25 1:41 AM, Fabio Estevam wrote:
Hi Marek,
On Fri, Mar 7, 2025 at 2:42 AM Marek Vasut wrote:
So what should we do about this particular patch ?
Should this be applied ? Rebased ? Updated somehow ?
This patch causes a CI error:
https://source.denx.de/u-boot/custodians/u-boot-imx/-/
An expo generally needs to keep track of the keyboard state while it is
running, so move the context into struct expo
Signed-off-by: Simon Glass
---
boot/bootflow_menu.c | 9 +++--
boot/cedit.c | 8 +++-
boot/expo.c | 1 +
include/expo.h | 2 ++
4 files changed, 9
On 28.02.25 20:22, Benjamin Schneider wrote:
This device uses the SCSI subsystem to interface with SATA devices.
Trying to use the sata command results in an unhandled exception.
This has the side effect of also causing bootflow scan to raise
an unhandled exception when it attempts to probe the S
Hi Michael,
Thank you for the patch.
On mer., mars 12, 2025 at 08:36, Michael Walle wrote:
> Fastboot works either over TCP, UDP or USB. The latter doesn't have
> anything to do with networking, thus should work just fine with
> regardless which network stack is selected. In practice, header sy
There is no reason to enable DEBUG uart used for early debugging by default
that's why disable it.
Signed-off-by: Michal Simek
---
configs/amd_versal2_mini_defconfig | 6 --
configs/amd_versal2_mini_emmc_defconfig | 6 --
configs/amd_versal2_mini_ospi_defconfig | 6 --
configs/
Hello Wadim,
On 20/03/25 12:44, Wadim Egorov wrote:
Am 09.01.25 um 23:27 schrieb Tom Rini:
On Thu, Jan 09, 2025 at 12:41:56PM +0530, Vankar, Chintan wrote:
On 1/7/2025 7:52 PM, Tom Rini wrote:
On Tue, Jan 07, 2025 at 03:08:28PM +0530, Chintan Vankar wrote:
'sprintf()' function defined in '
From: Venkatesh Yadav Abbarapu
Update the TEXT_BASE and DTB address as per the new memory map.
Signed-off-by: Venkatesh Yadav Abbarapu
Signed-off-by: Michal Simek
---
configs/amd_versal2_virt_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/amd_versal2_vi
This series enables MUX_MMIO at SPL stage for j7200 and j721e
as it is required for successful hyperflash boot.
Test logs :
https://gist.github.com/anuragdutta731/b4c79ef8da56d8c50b38d953c9da4d45
Anurag Dutta (3):
mux: Kconfig: Add Kconfig options for MUX_MMIO
configs: j7200_evm_a72_defconfi
Am 09.01.25 um 23:27 schrieb Tom Rini:
On Thu, Jan 09, 2025 at 12:41:56PM +0530, Vankar, Chintan wrote:
On 1/7/2025 7:52 PM, Tom Rini wrote:
On Tue, Jan 07, 2025 at 03:08:28PM +0530, Chintan Vankar wrote:
'sprintf()' function defined in 'tiny-printf.c' is returning length of the
string excl
Hi Anurag,
On 20/03/25 12:00, Anurag Dutta wrote:
> Add Kconfig options for MUX_MMIO so that it can be enabled
> in SPL stage.
>
> Signed-off-by: Anurag Dutta
> ---
> drivers/mux/Kconfig | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/mux/Kconfig b/drivers/mux/Kcon
When using expo we want to be able to control the information on the
display and avoid other messages (such as USB scanning) appearing.
Add a 'quiet' flag for the console, to help with this.
The test is a little messy since stdio is still using the original
vidconsole create on start-up. So take
If tiny printf is used with 0x%08X (upper case X) the output is
always 0x. It could be confusing if upper case instead
of lower case is used intentionally or accidentally because the
actual value is not output. To avoid this confusion, tiny printf
is extended to support also the formatting
On Thu, Mar 20, 2025 at 12:49:17PM +0100, Marek Vasut wrote:
> On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > If tiny printf is used with 0x%08X (upper case X) the output is
> > always 0x. It could be confusing if upper case instead
> > of lower case is used intentionally or accident
FIXME: Reword more
The problem with using "virt-make-fs" to make a filesystem image is that
it is extremely slow. Switch to using the fs_helper functions we have
instead from the filesystem tests as these can add files to images and
are significantly faster and still do not require root access.
T
The problem with using "virt-make-fs" to make a filesystem image is that
it is extremely slow. Switch to using the fs_helper functions we have
instead from the filesystem tests as these can add files to images and
are significantly faster and still do not require root access.
Signed-off-by: Tom Ri
Now that we have no users of "virt-make-fs" nor users of "sudo" for
creating disk images update the documentation. We remove packages that
are no longer required (and related text) as well as be firm in our
wording around not using "sudo".
Signed-off-by: Tom Rini
---
Changes in v2:
- None
---
do
Hey all,
One thing that Simon Glass has noted is that our pytest run time keeps
getting longer. Looking at:
https://source.denx.de/u-boot/u-boot/-/pipelines/25011/test_report?job_name=sandbox%20test.py%3A%20%5Bfast%20amd64%5D
we can see that some of the longest running tests are a little puzzling.
On 3/20/25 3:00 PM, Quentin Schulz wrote:
Hi Marek,
On 3/20/25 12:49 PM, Marek Vasut wrote:
On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
If tiny printf is used with 0x%08X (upper case X) the output is
always 0x. It could be confusing if upper case instead
of lower case is used int
On Thu, Mar 20, 2025 at 03:14:03PM +0100, Marek Vasut wrote:
> On 3/20/25 3:00 PM, Quentin Schulz wrote:
> > Hi Marek,
> >
> > On 3/20/25 12:49 PM, Marek Vasut wrote:
> > > On 3/20/25 11:23 AM, Christoph Niedermaier wrote:
> > > > If tiny printf is used with 0x%08X (upper case X) the output is
> >
On Thu, Mar 20, 2025 at 03:39:26AM +, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 19 Mar 2025 at 15:57, Tom Rini wrote:
> >
> > On Wed, Mar 19, 2025 at 03:54:05PM +0100, Simon Glass wrote:
> >
> > > This series collects together some new features for expo to make it more
> > > useful for boot me
On Thu, Mar 20, 2025 at 03:43:30AM +, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 19 Mar 2025 at 16:38, Tom Rini wrote:
> >
> > On Wed, Mar 19, 2025 at 03:04:16PM +, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Wed, 19 Mar 2025 at 15:24, Tom Rini wrote:
> > > >
> > > > On Wed, Mar 19, 20
Hi Tom,
On Wed, 19 Mar 2025 at 16:36, Tom Rini wrote:
>
> On Wed, Mar 19, 2025 at 03:04:00PM +, Simon Glass wrote:
> > Hi Tom,
> >
> > On Wed, 19 Mar 2025 at 15:20, Tom Rini wrote:
> > >
> > > On Wed, Mar 19, 2025 at 01:12:30PM +0100, Heinrich Schuchardt wrote:
> > > > Am 19. März 2025 12:59
On 19-03-2025 15:06, Heiko Schocher wrote:
Hello Mike,
On 18.03.25 10:04, Mike Looijmans wrote:
I think I have everything set up to access MTD (and UBI) devices as
"block", however, lsblk always ignores them, and refuses to list
anything but the mmc. I can read ubifs and boot from it though, a
41 matches
Mail list logo
