Hi Simon,
On Fri, 2025-02-14 at 06:48 -0700, Simon Glass wrote:
> Hi Yannic,
>
> On Fri, 14 Feb 2025 at 00:05, Yannic Moog wrote:
> >
> > On Thu, 2025-02-13 at 07:01 -0700, Simon Glass wrote:
> > > Hi Yannic,
> > >
> > > On Thu, 13 Feb 2025 at 00:21, Yannic Moog wrote:
> > > >
> > > > On Mon
On Mon, Feb 10, 2025 at 12:18:28PM +0100, Heinrich Schuchardt wrote:
> The configuration descriptions generated by binman contain the vendor
> device-tree directory. Instead of adding it to all match strings just strip
> it off.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2:
> no change
On Fri, 2025-02-14 at 06:48 -0700, Simon Glass wrote:
> Hi Yannic,
>
> On Fri, 14 Feb 2025 at 00:18, Yannic Moog wrote:
> >
> > Hi Simon,
> >
> > On Thu, 2025-02-13 at 07:01 -0700, Simon Glass wrote:
> > > Hi Yannic,
> > >
> > > On Thu, 13 Feb 2025 at 00:15, Yannic Moog wrote:
> > > >
> > >
On 2/13/25 20:53, Jonathan Humphreys wrote:
For capsule update, explicitly set the dfu_alt_info environment variable
before the DFU operation, and then restore it to the original value.
Previously, the dfu_alt_info environment variable was set with the
set_dfu_alt_info() function.
The problem
On Mon, Feb 10, 2025 at 10:57:43AM +0800, Hal Feng wrote:
> Update the maintainer file and mark jh7110 / visionfive2 related files
> with N: patterns.
>
> Signed-off-by: Hal Feng
> ---
>
> Changes since v2:
> - Mark visionfive2 related files with N: pattern.
>
> Changes since v1:
> - Mark jh711
On Thu, Feb 06, 2025 at 02:05:03PM +0100, Heinrich Schuchardt wrote:
> Variable $fdtfile needs to be set for automatically loading a device-tree
> from the ESP or boot partition.
>
> * Set CONFIG_DEFAULT_FDT_FILE in the defconfig.
> * Add $fdtfile to the default environment.
>
> Signed-off-by: He
On Mon, Feb 10, 2025 at 12:22:08PM -0800, E Shattow wrote:
> Use LwIP network stack and enable wget HTTP command. The tftpput command
> is not currently supported by LwIP network stack so remove it.
>
> Signed-off-by: E Shattow
> ---
> configs/starfive_visionfive2_defconfig | 3 ++-
> 1 file cha
> -Original Message-
> From: Tom Rini
> Sent: Saturday, 18 January, 2025 1:57 AM
> To: Ng, Boon Khai
> Cc: Uboot Open List ; Chee, Tien Fong
> ; Hea, Kok Kiang ;
> Maniyam, Dinesh ; Yuslaimi, Alif Zakuan
> ; Zamri, Muhammad Hazim Izzat
>
> Subject: Re: [XGMAC dt bindings v1 1/1] dt: net:
On Sun, Feb 16, 2025 at 07:09:57AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Sat, 15 Feb 2025 at 11:21, Tom Rini wrote:
> >
> > On Sat, Feb 15, 2025 at 10:24:08AM -0700, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Sat, 15 Feb 2025 at 07:46, Tom Rini wrote:
> > > >
> > > > On Sat, Feb 15, 20
Hi Tom,
On Sun, 16 Feb 2025 at 09:21, Tom Rini wrote:
>
> On Sun, Feb 16, 2025 at 10:15:16AM -0600, Tom Rini wrote:
> > On Sun, Feb 16, 2025 at 07:09:57AM -0700, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Sat, 15 Feb 2025 at 11:21, Tom Rini wrote:
> > > >
> > > > On Sat, Feb 15, 2025 at 10:
On 2/16/25 21:43, Simon Glass wrote:
U-Boot can start and boot an OS in both qemu-x86 and qemu-x86_64 but it
is not perfect.
With both builds, executing the VESA ROM causes an intermittent hang, at
least on some AMD CPUs.
With qemu-x86_64 kvm cannot be used since the move to long mode (64-bit)
On Sun, Feb 16, 2025 at 10:15:16AM -0600, Tom Rini wrote:
> On Sun, Feb 16, 2025 at 07:09:57AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 11:21, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 10:24:08AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Sa
On Sun, Feb 16, 2025 at 01:43:45PM -0700, Simon Glass wrote:
> U-Boot can start and boot an OS in both qemu-x86 and qemu-x86_64 but it
> is not perfect.
>
> With both builds, executing the VESA ROM causes an intermittent hang, at
> least on some AMD CPUs.
>
> With qemu-x86_64 kvm cannot be used
On Sun, Feb 16, 2025 at 12:39:34PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Sun, 16 Feb 2025 at 09:07, Tom Rini wrote:
> >
> > On Sun, Feb 16, 2025 at 07:10:12AM -0700, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Sat, 15 Feb 2025 at 11:12, Tom Rini wrote:
> > > >
> > > > On Sat, Feb 15, 20
From: "J. Neuschäfer"
This is necessary for the following patch. No functional change.
Signed-off-by: J. Neuschäfer
---
drivers/net/tsec.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/drivers/net/tsec.c b/drivers/net/tsec.c
index
6
From: "J. Neuschäfer"
When an error is detected in the TSEC receive path, the driver currently
prints an error message, but leaves the corresponding packet descriptor
in its old state (i.e. owned by the CPU side). As a result, the packet
queue can be starved of available buffers if enough errors
case
drivers/net/tsec.c | 39 +--
1 file changed, 21 insertions(+), 18 deletions(-)
---
base-commit: 5919f48b1c751b85453adca96493ab16f9098be0
change-id: 20250216-tsec-2acd62b9f844
Best regards,
--
J. Neuschäfer
Some test can only be run by a particular board in a lab, e.g. because
they are loaded with an OS image used by the test. Add a way to specify
this in tests.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to allow tests to be filtered by role
test/py/conftest.py | 22 +++
Now that U-Boot can boot this quickly, using kvm, add a test that the
installer starts up correctly.
Use the qemu-x86_64 board in the SJG lab.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add more patches to support booting with kvm
- Add new patch with a test for booting Ubuntu 24.04
.git
The distro test takes a little longer to shut down and restart, so
add more time to this operation.
Disable the sleep command for now, as it seems to be unreliable on
QEMU with '-cpu host'.
More thought will be needed for both of these problems.
Signed-off-by: Simon Glass
---
(no changes since
The existing run_command() method is not great for sending things other
than U-Boot commands. Add a helper for sending arbitrary strings as well
as control characters.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch with a helper to send characters
test/py/console_base.py | 25 ++
Use the 64-bit function to detect a power-of-two. This allows use of
a full 4GB MTRR on 32-bit machines.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/mtrr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/cpu/mtrr.c b/arch/x86/cpu/mtrr.c
index
This gets the script to where it can boot with kvm:
- Use -cpu host with kvm so that the host CPU is used
- Show the full QEMU arguments
Signed-off-by: Simon Glass
---
(no changes since v1)
scripts/build-qemu.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/b
QEMU likes to have an MTRR set up, just like real machines. Add an MTRR
which covers the total RAM size.
This does nothing on machines without MTRRs.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to set an MTRR for the RAM in QEMU
arch/x86/cpu/qemu/dram.c | 15 +++
The existing function only works with ulong which is not enough on
32-bit x86 machines which need to set up MTRRs up to 4GB.
There doesn't seem to be a 64-bit version in Linux, so add one here.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch with a 64-bit version of is_power_of_2(
The CONFIG value should only be used when it cannot be read from the
CPU. This is particularly important when using kvm since the CPU size
depends on the host CPU.
Update set_var_mtrr() to use the correct function for this, which now
supports 64-bit operation. Ensure that the lower bits of the mas
At present it is not possible to find out the physical-address size in
long mode, so a predefined value is used.
Update the macros to support this properly, since it is important when
programming MTRRs.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to support CPU functions in lo
With the 64-bit descriptor we can use a jump instruction, rather than
pushing things on the stack.
Since the processor is in 64-bit mode by this point, pop a 64-bit value
from the stack, containing the target address.
This simplifies the code slightly, in particular its use of the stack.
Signed-
This value happens to be used by ctype.h so chose a different name.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to rename the _D dirty flag
arch/x86/cpu/i386/cpu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/cpu/i386/cpu.c b/arch/x86/cpu/i
Make use the existing GDT which now includes entries for 64-bit code.
Leave the interrupt descriptors alone. They can be tidied up once U-Boot
starts up.
With this, kvm mode works with QEMU.
Signed-off-by: Simon Glass
Fixes: https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/31
---
(no
This is required as part of the procedure. The existing code works
because it changes the GDT at the same time, but this makes kvm
unhappy.
Update the algorithm to disable and then re-enable paging.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/i386/call64.S | 8 +++-
Use a symbol to select the size of the GDT, rather than hard-coding a
value. This matches how it is done in start64
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/start.S | 4 +++-
arch/x86/cpu/start16.S | 3 ++-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git
This makes use of a 'bool' type, so include the required header.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/include/asm/interrupt.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/interrupt.h b/arch/x86/include/asm/interrupt.h
index e23fb2c8e72..c689
This functions normally and has done for a while, so drop this scary
message.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/spl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/lib/spl.c b/arch/x86/lib/spl.c
index 47cf9c862b5..0a6a761987e 10064
x86_cpu_init_f() is called by arch_cpu_init() a few lines below this
code. Drop the duplicate call.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/spl.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/lib/spl.c b/arch/x86/lib/spl.c
index 7a033505101..47cf9c862b
At present it is not possible to execution 64-bit code without
installing an entire new Global Descriptor Table. This is inconvenient
since kvm does not seem to like switching into long mode with a new
table.
It isn't actually necessary, since we can just extend the existing
table. Add some new en
Use some named flags when setting up the cache, so it is easier to see
what is going on.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/i386/cpu.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/x86/cpu/i386/cpu.c b/arch/x86/cpu/i386
This option is not actually defined in Kconfig anymore. Use a normal
debug print instead, which has a similar effect.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/bios.c| 18 --
arch/x86/lib/bios_interrupts.c | 6 ++
2 files changed, 10 ins
Add categories for i8259 and bios files, so that log statements have the
right category.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/bios.c| 3 +++
arch/x86/lib/bios_interrupts.c | 2 ++
arch/x86/lib/i8259.c | 2 ++
3 files changed, 7 insertions(+)
U-Boot clears the display when it starts up, so there is no need to ask
the VESA driver to do this. Fix this and add a comment explaining the
flags.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/bios.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a
This is not needed in SPL, so drop it.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/lib/Makefile b/arch/x86/lib/Makefile
index 43e6a1de77d..a908356e8a6 100644
--- a/arch/x86/lib/Makefile
+++ b/arch/x86
BSS is placed in DRAM which is actually available early with QEMU. But
it is cleared by the init sequence, so values stored there are lost.
Move the system-type flag into a function, instead.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/cpu/qemu/qemu.c | 20 ++
Provide the 'dhry' command, which helps to check that kvm is being used
properly with QEMU.
Signed-off-by: Simon Glass
---
(no changes since v1)
configs/qemu-x86_64_defconfig | 1 +
configs/qemu-x86_defconfig| 1 +
2 files changed, 2 insertions(+)
diff --git a/configs/qemu-x86_64_defconfi
The vesa display is widely used on hardware, but it is a bit of a pain
with QEMU. It requires executing option ROMs, which either doesn't work
with kvm, or is difficult to do in a kvm/QEMU-friendly way.
THe bochs display is probably better anyway, so switch to that. It works
fine with kvm as it do
The SPL and pre-reloc malloc()-space is not large enough to start up
with a display. Expand it.
Switch the order of SPL_SYS_MALLOC_F_LEN and SPL_TEXT_BASE since this
matches what 'savedefconfig' gives us.
Signed-off-by: Simon Glass
---
(no changes since v1)
configs/qemu-x86_64_defconfig | 4 +
U-Boot can start and boot an OS in both qemu-x86 and qemu-x86_64 but it
is not perfect.
With both builds, executing the VESA ROM causes an intermittent hang, at
least on some AMD CPUs.
With qemu-x86_64 kvm cannot be used since the move to long mode (64-bit)
is done in a way that works on real har
Hi Tom,
On Sun, 16 Feb 2025 at 08:04, Tom Rini wrote:
>
> On Sun, Feb 16, 2025 at 07:50:48AM -0700, Simon Glass wrote:
> > Hi Sughosh,
> >
> > On Wed, 27 Nov 2024 at 04:48, Sughosh Ganu wrote:
> > >
> > > On Tue, 26 Nov 2024 at 21:09, Simon Glass wrote:
> > > >
> > > > Hi Sughosh,
> > > >
> > >
Hi Tom,
On Sun, 16 Feb 2025 at 09:07, Tom Rini wrote:
>
> On Sun, Feb 16, 2025 at 07:10:12AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 11:12, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 10:21:16AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Sat
The Acer Iconia A500 is a tablet computer designed, developed and
marketed by Acer Inc. It is powered by 1 GHz Nvidia Tegra 2 processor
and 1GB DDR2 RAM. The A500 is sold with 64 GB, although both 16 GB
and 32 GB models are available.
Signed-off-by: Svyatoslav Ryhel
---
arch/arm/dts/Makefile
The Acer Iconia A500 is a tablet computer designed, developed and
marketed by Acer Inc. It is powered by 1 GHz Nvidia Tegra 2 processor
and 1GB DDR2 RAM. The A500 is sold with 64 GB, although both 16 GB
and 32 GB models are available.
All important functions are implemented, including:
- installat
On Sun, Feb 16, 2025 at 05:50:53PM +0100, Heinrich Schuchardt wrote:
> Am 16. Februar 2025 15:26:31 MEZ schrieb Yao Zi :
> >On Sat, Feb 15, 2025 at 05:58:18PM +0100, Heinrich Schuchardt wrote:
> >> On 15.02.25 16:54, Yao Zi wrote:
> >> > Structure jmp_buf_data provides the underlying format of jmp_
Am 16. Februar 2025 15:26:31 MEZ schrieb Yao Zi :
>On Sat, Feb 15, 2025 at 05:58:18PM +0100, Heinrich Schuchardt wrote:
>> On 15.02.25 16:54, Yao Zi wrote:
>> > Structure jmp_buf_data provides the underlying format of jmp_buf, which
>> > we actually don't care about. Clean up existing code to use t
When adding the symlink for the conf file so qemu_arm64_lwip uses
qemu_arm64 configuration information, the symlink for the boardenv file
was missed in Gitlab (but not Azure). Add that in now.
Fixes: fd10d156db3f ("CI: add qemu_arm64_lwip to the test matrix")
Signed-off-by: Tom Rini
---
I'll take
On Sun, Feb 16, 2025 at 07:10:12AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Sat, 15 Feb 2025 at 11:12, Tom Rini wrote:
> >
> > On Sat, Feb 15, 2025 at 10:21:16AM -0700, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Sat, 15 Feb 2025 at 07:41, Tom Rini wrote:
> > > >
> > > > On Sat, Feb 15, 20
On Sun, Feb 16, 2025 at 09:01:23AM -0600, Tom Rini wrote:
> On Sun, Feb 16, 2025 at 07:10:31AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 11:28, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 10:24:50AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Sa
On Sat, Feb 15, 2025 at 05:58:18PM +0100, Heinrich Schuchardt wrote:
> On 15.02.25 16:54, Yao Zi wrote:
> > Structure jmp_buf_data provides the underlying format of jmp_buf, which
> > we actually don't care about. Clean up existing code to use the standard
> > jmp_buf type. This introduces no funct
On Sun, Feb 16, 2025 at 07:50:48AM -0700, Simon Glass wrote:
> Hi Sughosh,
>
> On Wed, 27 Nov 2024 at 04:48, Sughosh Ganu wrote:
> >
> > On Tue, 26 Nov 2024 at 21:09, Simon Glass wrote:
> > >
> > > Hi Sughosh,
> > >
> > > On Thu, 21 Nov 2024 at 00:53, Sughosh Ganu
> > > wrote:
> > > >
> > > >
On Sun, Feb 16, 2025 at 07:10:31AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Sat, 15 Feb 2025 at 11:28, Tom Rini wrote:
> >
> > On Sat, Feb 15, 2025 at 10:24:50AM -0700, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Sat, 15 Feb 2025 at 08:01, Tom Rini wrote:
> > > >
> > > > On Sat, Feb 15, 20
Hi Sughosh,
On Wed, 27 Nov 2024 at 04:48, Sughosh Ganu wrote:
>
> On Tue, 26 Nov 2024 at 21:09, Simon Glass wrote:
> >
> > Hi Sughosh,
> >
> > On Thu, 21 Nov 2024 at 00:53, Sughosh Ganu wrote:
> > >
> > > On Tue, 12 Nov 2024 at 18:48, Simon Glass wrote:
> > > >
> > > > A bisect of Ubuntu 2022.
Hi Tom,
On Sat, 15 Feb 2025 at 11:28, Tom Rini wrote:
>
> On Sat, Feb 15, 2025 at 10:24:50AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 08:01, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 05:11:45AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Sat
Hi Tom,
On Sat, 15 Feb 2025 at 11:28, Tom Rini wrote:
>
> On Sat, Feb 15, 2025 at 10:23:05AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 07:59, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 04:58:24AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Tue
Hi Tom,
On Sat, 15 Feb 2025 at 11:12, Tom Rini wrote:
>
> On Sat, Feb 15, 2025 at 10:21:16AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 07:41, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 04:59:40AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Mon
Hi Tom,
On Sat, 15 Feb 2025 at 11:21, Tom Rini wrote:
>
> On Sat, Feb 15, 2025 at 10:24:08AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 15 Feb 2025 at 07:46, Tom Rini wrote:
> > >
> > > On Sat, Feb 15, 2025 at 05:06:42AM -0700, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On Fri
Hi Svyatoslav,
On Sun, 16 Feb 2025 at 06:00, Svyatoslav Ryhel wrote:
>
> нд, 16 лют. 2025 р. о 14:56 Simon Glass пише:
> >
> > Hi Svyatoslav,
> >
> > On Sat, 15 Feb 2025 at 11:12, Svyatoslav Ryhel wrote:
> > >
> > > сб, 15 лют. 2025 р. о 20:07 Simon Glass пише:
> > > >
> > > > Hi Svyatoslav,
>
Hi Simon,
On Thu, Jan 23, 2025 at 3:13 PM Tom Rini wrote:
>
> On Fri, 10 Jan 2025 16:59:59 -0700, Simon Glass wrote:
>
> > The current UPL spec[1] has been tidied up and improved over the last
> > year, since U-Boot's original UPL support was written.
> >
> > This series includes some prerequisite
Hi Patrick,
On Sun, 16 Feb 2025 at 01:28, Patrick Rudolph
wrote:
>
> Hi Simon,
> On Thu, Jan 23, 2025 at 3:13 PM Tom Rini wrote:
> >
> > On Fri, 10 Jan 2025 16:59:59 -0700, Simon Glass wrote:
> >
> > > The current UPL spec[1] has been tidied up and improved over the last
> > > year, since U-Boot
Hi Svyatoslav,
On Sat, 15 Feb 2025 at 11:10, Svyatoslav Ryhel wrote:
>
> сб, 15 лют. 2025 р. о 20:08 Simon Glass пише:
> >
> > Hi Svyatoslav,
> >
> > On Sat, 15 Feb 2025 at 10:55, Svyatoslav Ryhel wrote:
> > >
> > > Add a mostly complete list of ofnode analogs of of_graph
> > > parsing helpers.
нд, 16 лют. 2025 р. о 14:56 Simon Glass пише:
>
> Hi Svyatoslav,
>
> On Sat, 15 Feb 2025 at 11:12, Svyatoslav Ryhel wrote:
> >
> > сб, 15 лют. 2025 р. о 20:07 Simon Glass пише:
> > >
> > > Hi Svyatoslav,
> > >
> > > On Sat, 15 Feb 2025 at 10:42, Svyatoslav Ryhel wrote:
> > > >
> > > > сб, 15 лю
нд, 16 лют. 2025 р. о 14:56 Simon Glass пише:
>
> Hi Svyatoslav,
>
> On Sat, 15 Feb 2025 at 11:10, Svyatoslav Ryhel wrote:
> >
> > сб, 15 лют. 2025 р. о 20:08 Simon Glass пише:
> > >
> > > Hi Svyatoslav,
> > >
> > > On Sat, 15 Feb 2025 at 10:55, Svyatoslav Ryhel wrote:
> > > >
> > > > Add a mos
Hi Heinrich,
On Sat, 15 Feb 2025 at 10:23, Simon Glass wrote:
>
> Hi Heinrich,
>
> On Sat, 15 Feb 2025 at 08:22, Heinrich Schuchardt
> wrote:
> >
> > Up to now root has been the parent device for all block devices created via
> > calling ConnectController(). This does not work well together with
Hi Svyatoslav,
On Sat, 15 Feb 2025 at 11:12, Svyatoslav Ryhel wrote:
>
> сб, 15 лют. 2025 р. о 20:07 Simon Glass пише:
> >
> > Hi Svyatoslav,
> >
> > On Sat, 15 Feb 2025 at 10:42, Svyatoslav Ryhel wrote:
> > >
> > > сб, 15 лют. 2025 р. о 19:24 Simon Glass пише:
> > > >
> > > > Hi Svyatoslav,
>
Each MMC device has a child which ihs a block device. At present we call
mmc_deinit() when the block device is removed.
But the MMC struct (i.e. struct mmc) is attached to the MMC's device,
not its child.
So at present, when an MMC device is removed, mmc_deinit() is called
twice, once for the MMC
Add a mostly complete list of ofnode analogs of of_graph
parsing helpers.
---
Changes in v2:
- added tests
---
Svyatoslav Ryhel (2):
core: ofnode: add of_graph parsing helpers
test: dm: add ofnode_graph tests
arch/sandbox/dts/test.dts | 53 +
drivers/core/Makefile | 2 +-
Test suit for of_graph parsing helpers.
Signed-off-by: Svyatoslav Ryhel
---
arch/sandbox/dts/test.dts | 53 ++
test/dm/ofnode.c | 54 +++
2 files changed, 107 insertions(+)
diff --git a/arch/sandbox/dts/test.dts b/
Add a mostly complete list of ofnode analogs of of_graph
parsing helpers.
Signed-off-by: Svyatoslav Ryhel
---
drivers/core/Makefile | 2 +-
drivers/core/ofnode_graph.c | 217
include/dm/ofnode_graph.h | 90 +++
3 files changed, 308 inse
When building with qemu_arm64_defconfig with CONFIG_CC_OPTIMIZE_FOR_DEBUG=y
and CONFIG_EFI_LOADER an error undefined reference to efi_add_memory_map_pg
occurs.
Move the EFI dependent part of lmb_map_update_notify() to the EFI
sub-system.
Reported-by: Liya Huang <1425075...@qq.com>
Signed-off-by:
The function is only used in the efi_memory.c module.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h| 15 ---
lib/efi_loader/efi_memory.c | 1 +
2 files changed, 1 insertion(+), 15 deletions(-)
diff --git a/include/efi_loader.h b/include/efi_loader.h
index db3d
Instead of testing the value of parameter op at runtime use an enum to
ensure that only valid values are used.
Signed-off-by: Heinrich Schuchardt
---
include/lmb.h | 12
lib/lmb.c | 23 +++
2 files changed, 19 insertions(+), 16 deletions(-)
diff --git a/incl
When building with qemu_arm64_defconfig with CONFIG_CC_OPTIMIZE_FOR_DEBUG=y
and CONFIG_EFI_LOADER an error undefined reference to efi_add_memory_map_pg
occurs.
Move the EFI dependent part of lmb_map_update_notify() to the EFI
sub-system and clean up a little.
Thanks to Liya for reporting the issu
79 matches
Mail list logo
