[PATCH 1/3] doc: move PXE README into usage documentation

This is only a reformatting, with a few grammar fixes (capitalization, and a missing "is" and "be" added each). Signed-off-by: Fiona Klute Cc: Tom Rini --- doc/README.pxe | 292 -- doc/usage/index.rst | 1 + doc/u

[PATCH 2/3] doc: PXE usage: move environment variables to a separate section

This works better with RST formatting, and avoids duplication. Signed-off-by: Fiona Klute Cc: Tom Rini --- doc/usage/pxe.rst | 144 ++ 1 file changed, 70 insertions(+), 74 deletions(-) diff --git a/doc/usage/pxe.rst b/doc/usage/pxe.rst index

[PATCH 3/3] doc: PXE: mention extlinux.conf and sysboot

These use the same format as PXE boot. Signed-off-by: Fiona Klute Cc: Tom Rini --- doc/usage/pxe.rst | 23 +++ 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/doc/usage/pxe.rst b/doc/usage/pxe.rst index d23cd453227..c2dc11f218d 100644 --- a/doc/usage/pxe.rst

[PATCH 0/3] Move PXE boot from README into online documentation

nd grouped up environment variables (patch 2). There's definitely more that could be improved here (e.g. move the commands to the Shell Commands section, reduce overlap with doc/develop/distro.rst), but I hope this helps for now. Best regards, Fiona Fiona Klute (3): doc: move PXE README into

Re: [PATCH 1/1] doc: mention that extlinux.conf can use environment in "append"

Am 23.06.25 um 17:04 schrieb Tom Rini: On Mon, Jun 23, 2025 at 01:38:01PM +0200, Fiona Klute wrote: This option is very useful for A/B boot setups with read-only filesystems: Letting U-Boot fill in the rootfs (and possibly related parameters) allows keeping all boot parameters except the

[PATCH 1/1] doc: mention that extlinux.conf can use environment in "append"

This option is very useful for A/B boot setups with read-only filesystems: Letting U-Boot fill in the rootfs (and possibly related parameters) allows keeping all boot parameters except the actual slot selection in the extlinux.conf file, where they can be updated easily. Signed-off-by: Fiona

Re: [RFC] Raspberry Pi: copy /system/linux,{serial,revision} from firmware

pberry-pi-revision-codes Overall I am not currently convinced this is something we currently want. Peter [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings Best regards, Fiona Am 15.02.25 um 14:01 schrieb Peter Robinson: Hi Fiona, I

[PATCH] rpi: copy /system/linux,{serial,revision} from firmware FDT

the same. [1] https://github.com/raspberrypi/linux/blob/0f292fbb6346b05766152902076895558ac23f9a/arch/arm/mach-bcm/board_bcm2835.c#L23-L33 [2] https://github.com/jgarff/rpi_ws281x/blob/7fc0bf8b31d715bbecf28e852ede5aaa388180da/rpihw.c#L579 Signed-off-by: Fiona Klute Cc: Matthias Brugger Cc

Re: [RFC] Raspberry Pi: copy /system/linux,{serial,revision} from firmware

test this the coming week and provide feedback. On Tue, 11 Feb 2025 at 13:58, Fiona Klute wrote: Both the Raspberry Pi downstream kernel [1] and some userspace tools [2] use the revision property to identify the board, and the latter fails if it is absent. The firmware creates the /system node,

Re: [RFC] Raspberry Pi: copy /system/linux,{serial,revision} from firmware

, Fiona Am 11.02.25 um 14:58 schrieb Fiona Klute: Both the Raspberry Pi downstream kernel [1] and some userspace tools [2] use the revision property to identify the board, and the latter fails if it is absent. The firmware creates the /system node, so we need to do the same. [1] https

[PATCH 2/2] Raspberry Pi: Copy Bluetooth device address in DT

The firmware sets local-bd-address, copy it when loading a new DT. Signed-off-by: Fiona Klute --- This simple copy works with upstream Linux DT, and with the downstream RPi one as long as BT has not been moved to mini-UART. The downstream DT additionally defines /aliases/bluetooth, which is

[PATCH 1/2] Raspberry Pi: Keep warnings from firmware in DT, if any

the warning can be read after boot: $ cat /proc/device-tree/chosen/user-warnings dterror: can't find symbol 'nosuchdev' Failed to resolve overlay 'error-example' Signed-off-by: Fiona Klute --- board/raspberrypi/rpi/rpi.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

[RFC] Raspberry Pi: copy /system/linux, {serial, revision} from firmware

/0f292fbb6346b05766152902076895558ac23f9a/arch/arm/mach-bcm/board_bcm2835.c#L23-L33 [2] https://github.com/jgarff/rpi_ws281x/blob/7fc0bf8b31d715bbecf28e852ede5aaa388180da/rpihw.c#L579 Signed-off-by: Fiona Klute Cc: Matthias Brugger Cc: Peter Robinson Cc: Tom Rini --- I'm sending this as RFC because I'm n

Re: Selecting serial device for console

Hi Simon, Mark, thanks for your replies! Am 08.08.24 um 16:28 schrieb Simon Glass: Hi Mark, On Tue, 6 Aug 2024 at 16:33, Mark Kettenis wrote: From: Simon Glass Date: Tue, 6 Aug 2024 15:50:44 -0600 Hi Simon, Hi Fiona, On Thu, 1 Aug 2024 at 08:07, Fiona Klute wrote: Hi everyone

Selecting serial device for console

Hi everyone, how can I configure which of the available serial devices U-Boot will use for its serial console? Background: I have a device based on a Raspberry Pi CM4, which has 6 UARTs (UART1 is a mini UART, the others PL011) [1]. In the default configuration (including the mainline Linux broad

Re: Pull request efi-2024-07-rc3

Fiona Klute (2):   doc: Detailed example for netconsole setup   doc: Update netconsole examples, mention stderr it seems the git branch contains v2 of the netconsole documentation patches, not v3 with the prompt formatting change you requested. Is that intentional

Re: [PATCH v2 1/2] doc: Detailed example for netconsole setup

Hi Tony! Am 16.05.24 um 21:28 schrieb Tony Dinh: On Thu, May 16, 2024 at 3:43 AM Fiona Klute wrote: This adds details that I would have liked to have readily available, in particular how to activate the network interface before enabling netconsole, and how to integrate netconsole so you can

Re: [PATCH 1/2] doc: Detailed example for netconsole setup

Am 17.05.24 um 09:32 schrieb Heinrich Schuchardt: On 5/14/24 22:20, Fiona Klute wrote: This adds details that I would have liked to have readily available, in particular how to activate the network interface before enabling netconsole, and how to integrate netconsole so you can use the U-Boot

[PATCH v3 2/2] doc: Update netconsole examples, mention stderr

Stderr was missing from the initial description and example. As I understand the env command documentation the subcommand style is preferred, though the old format is still fully supported. Signed-off-by: Fiona Klute Reviewed-by: Tony Dinh Reviewed-by: Heinrich Schuchardt --- Changes in v2

[PATCH v3 1/2] doc: Detailed example for netconsole setup

This adds details that I would have liked to have readily available, in particular how to activate the network interface before enabling netconsole, and how to integrate netconsole so you can use the U-Boot prompt. Signed-off-by: Fiona Klute Reviewed-by: Tony Dinh --- Changes in v2: * Include

[PATCH v2 2/2] doc: Update netconsole examples, mention stderr

Stderr was missing from the initial description and example. As I understand the env command documentation the subcommand style is preferred, though the old format is still fully supported. Signed-off-by: Fiona Klute --- Changes in v2: * Mention stderr redirection * Use 4 spaces instead of tabs

[PATCH v2 1/2] doc: Detailed example for netconsole setup

This adds details that I would have liked to have readily available, in particular how to activate the network interface before enabling netconsole, and how to integrate netconsole so you can use the U-Boot prompt. Signed-off-by: Fiona Klute --- Changes in v2: * Include stderr redirection * Use

Re: [PATCH 1/2] doc: Detailed example for netconsole setup

Am 15.05.24 um 21:05 schrieb Tony Dinh: Hi Fiona, On Tue, May 14, 2024 at 5:28 PM Fiona Klute wrote: This adds details that I would have liked to have readily available, in particular how to activate the network interface before enabling netconsole, and how to integrate netconsole so you can

[PATCH 2/2] doc: Update netconsole examples

As I understand the env command documentation the subcommand style is preferred, though the old format is still fully supported. Signed-off-by: Fiona Klute --- doc/usage/netconsole.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/usage/netconsole.rst b/doc/usage

[PATCH 1/2] doc: Detailed example for netconsole setup

This adds details that I would have liked to have readily available, in particular how to activate the network interface before enabling netconsole, and how to integrate netconsole so you can use the U-Boot prompt. Signed-off-by: Fiona Klute --- doc/usage/netconsole.rst | 33

[PATCH] Init virtio before loading ENV from EXT4 or FAT

;#if defined(CONFIG_...)", I'm sticking to the style of the existing code here. Signed-off-by: Fiona Klute CC: Joe Hershberger CC: Bin Meng CC: Rogier Stam --- env/ext4.c | 5 + env/fat.c| 5 + include/virtio.h | 1 + 3 files changed, 11 insertions(+) di