December 2024 - U-Boot

[PATCH 1/2] drivers: misc: gsc: add support for fan controller
by Tim Harvey 23 Dec '24

23 Dec '24

Add support for Gateworks System Controller fan tach input. Signed-off-by: Tim Harvey <tharvey(a)gateworks.com> --- drivers/misc/gsc.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/misc/gsc.c b/drivers/misc/gsc.c index dee0bdd9663a..bab405bb7226 100644 --- a/drivers/misc/gsc.c +++ b/drivers/misc/gsc.c @@ -330,6 +330,9 @@ static int gsc_hwmon(struct udevice *dev) printf("%-8s: %d.%03dV\n", label, val / 1000, val % 1000); break; + case 4: /* revolutions per minute */ + printf("%-8s: %drpm\n", label, val * 30); + break; } } -- 2.25.1

2 2

[PATCH] spi: mxc_spi: use proper clock for SPI bus
by Tim Harvey 23 Dec '24

23 Dec '24

The mxc_get_clock function is around for compatibility with older drivers that are not clock aware. In this case asking for the clk for MXC_CSPI_CLK does not take into account there are multiple SPI busses on modern IMX SoC's and it will return the clock for the first bus which may not be used or configured. In the case you are not using the first bus you will not get the proper clock. Fix this by obtaining the clock rate from the bus clock. This resolves an invalid SPI clock frequency configuration for SPI2 on a board where SPI1 is not used. Signed-off-by: Tim Harvey <tharvey(a)gateworks.com> --- drivers/spi/mxc_spi.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/drivers/spi/mxc_spi.c b/drivers/spi/mxc_spi.c index 9ab39a188b22..2c9b0ada87ba 100644 --- a/drivers/spi/mxc_spi.c +++ b/drivers/spi/mxc_spi.c @@ -114,6 +114,9 @@ struct mxc_spi_slave { u32 ctrl_reg; #if defined(MXC_ECSPI) u32 cfg_reg; +#endif +#if CONFIG_IS_ENABLED(CLK) + struct clk clk; #endif int gpio; int ss_pol; @@ -214,7 +217,11 @@ static s32 spi_cfg_mxc(struct mxc_spi_slave *mxcs, unsigned int cs) #ifdef MXC_ECSPI static s32 spi_cfg_mxc(struct mxc_spi_slave *mxcs, unsigned int cs) { +#if CONFIG_IS_ENABLED(CLK) + u32 clk_src = clk_get_rate(&mxcs->clk); +#else u32 clk_src = mxc_get_clock(MXC_CSPI_CLK); +#endif s32 reg_ctrl, reg_config; u32 ss_pol = 0, sclkpol = 0, sclkpha = 0, sclkctl = 0; u32 pre_div = 0, post_div = 0; @@ -599,14 +606,13 @@ static int mxc_spi_probe(struct udevice *bus) return -ENODEV; #if CONFIG_IS_ENABLED(CLK) - struct clk clk; - ret = clk_get_by_index(bus, 0, &clk); + ret = clk_get_by_index(bus, 0, &mxcs->clk); if (ret) return ret; - clk_enable(&clk); + clk_enable(&mxcs->clk); - mxcs->max_hz = clk_get_rate(&clk); + mxcs->max_hz = clk_get_rate(&mxcs->clk); #else int node = dev_of_offset(bus); const void *blob = gd->fdt_blob; -- 2.25.1

2 1

[PATCH RFC 0/8] Introduce J742S2 SoC and EVM
by Manorit Chawdhry 23 Dec '24

23 Dec '24

The series adds support for J742S2 family of SoCs. Also adds J742S2 board Support and re-uses most of the stuff from the superset device J784s4. It initially cleans up the J784s4 and AM69 files so that they can be re-usable for j742s2 and then it introduces J742S2. The DT for the following SoC will be coming to U-boot during 6.13 Sync so the series is kept as RFC till then. Test logs with manual sync of 6.13-rc2 and dependent patches: https://gist.github.com/manorit2001/1a222ab8b92961eb6dc829cfd5600be4 Signed-off-by: Manorit Chawdhry <m-chawdhry(a)ti.com> --- Manorit Chawdhry (6): arm: dts: k3-j784s4-ddr: Refactor J784s4 ddr file to a common file soc: Add information to identify the J742S2 SoC family arm: mach-k3: j742s2: Introduce clock and device files for J742S2 SoC board: ti: Introduce basic board files for the J742S2 family arm: dts: Introduce J742S2 U-boot DTS files configs: Introduce configs for J742S2 Neha Malcom Francis (2): tools: binman: control.py: Delete template nodes after parsing arm: dts: k3-j784s4-binman.dtsi: Clean up and templatize boot binaries arch/arm/dts/k3-am69-sk-u-boot.dtsi | 120 +- arch/arm/dts/k3-j742s2-ddr-evm-lp4-4266.dtsi | 8756 ++++++++++++++ arch/arm/dts/k3-j742s2-evm-u-boot.dtsi | 59 + arch/arm/dts/k3-j742s2-r5-evm.dts | 18 + arch/arm/dts/k3-j784s4-binman.dtsi | 116 +- arch/arm/dts/k3-j784s4-ddr.dtsi | 13246 +++++++--------------- arch/arm/dts/k3-j784s4-evm-u-boot.dtsi | 74 + arch/arm/dts/k3-j784s4-j742s2-ddr.dtsi | 4446 ++++++++ arch/arm/mach-k3/include/mach/hardware.h | 2 + arch/arm/mach-k3/include/mach/j784s4_hardware.h | 4 + arch/arm/mach-k3/j784s4/Kconfig | 18 + board/ti/j784s4/Kconfig | 33 + board/ti/j784s4/MAINTAINERS | 10 + board/ti/j784s4/j784s4.env | 4 + configs/j742s2_evm_a72_defconfig | 9 + configs/j742s2_evm_r5_defconfig | 9 + drivers/clk/ti/clk-k3.c | 4 + drivers/power/domain/ti-power-domain.c | 4 + drivers/soc/soc_ti_k3.c | 17 +- tools/binman/control.py | 6 +- 20 files changed, 18005 insertions(+), 8950 deletions(-) --- base-commit: 9bc62c980d418f0a67632ab29cd3501072cdb6f0 change-id: 20241119-b4-upstream-j742s2-6c9b944b7091 prerequisite-message-id: 20241217-b4-upstream-dm-pre-reloc-v1-1-ccd29165bbb6(a)ti.com prerequisite-patch-id: fdbddb1d9fdaadb7551e99caf5e93e22836dd8c3 Best regards, -- Manorit Chawdhry <m-chawdhry(a)ti.com>

3 16

[PATCH v1 0/7] Bring support for Xiaomi Mi Pad 1 (Tegra K1)
by Svyatoslav Ryhel 23 Dec '24

23 Dec '24

This patch set brings support for Xiaomi Mi Pad 1 based on Tegra K1 SoC as original vendor bootloader substitution. All major features are implemented. Minor stuff that still needs to be tested and fixed includes: - minor image flickering on the right side of the panel - check if U-Boot self-upgrade feature works as intended Svyatoslav Ryhel (7): pinctrl: tegra: add Tegra K1 support video: tegra20: dc: dsi: add Tegra K1 compatible video: tegra20: mipi: add Tegra K1 support video: add TI LP855x backlight driver video: panel: add Sharp LQ079L1SX01 MIPI DSI panel driver ARM: tegra124: implement BCT patching board: xiaomi: mocha: add Xiaomi Mi Pad A0101 support arch/arm/dts/Makefile | 1 + arch/arm/dts/tegra124-xiaomi-mocha.dts | 603 ++++++++++++++++++++ arch/arm/include/asm/arch-tegra124/pinmux.h | 4 + arch/arm/mach-tegra/Kconfig | 2 +- arch/arm/mach-tegra/tegra124/Kconfig | 5 + arch/arm/mach-tegra/tegra124/Makefile | 1 + arch/arm/mach-tegra/tegra124/bct.c | 91 +++ arch/arm/mach-tegra/tegra124/bct.h | 55 ++ board/xiaomi/mocha/Kconfig | 12 + board/xiaomi/mocha/MAINTAINERS | 8 + board/xiaomi/mocha/Makefile | 9 + board/xiaomi/mocha/mocha-spl.c | 49 ++ board/xiaomi/mocha/mocha.c | 41 ++ board/xiaomi/mocha/mocha.env | 23 + configs/mocha_defconfig | 90 +++ doc/board/index.rst | 1 + doc/board/xiaomi/index.rst | 9 + doc/board/xiaomi/mocha.rst | 112 ++++ drivers/pinctrl/tegra/pinctrl-tegra.c | 56 ++ drivers/video/Kconfig | 19 + drivers/video/Makefile | 2 + drivers/video/lp855x_backlight.c | 302 ++++++++++ drivers/video/sharp-lq079l1sx01.c | 275 +++++++++ drivers/video/tegra20/tegra-dc.c | 3 + drivers/video/tegra20/tegra-dsi.c | 12 +- drivers/video/tegra20/tegra-mipi.c | 134 ++++- include/configs/mocha.h | 25 + 27 files changed, 1928 insertions(+), 16 deletions(-) create mode 100644 arch/arm/dts/tegra124-xiaomi-mocha.dts create mode 100644 arch/arm/mach-tegra/tegra124/bct.c create mode 100644 arch/arm/mach-tegra/tegra124/bct.h create mode 100644 board/xiaomi/mocha/Kconfig create mode 100644 board/xiaomi/mocha/MAINTAINERS create mode 100644 board/xiaomi/mocha/Makefile create mode 100644 board/xiaomi/mocha/mocha-spl.c create mode 100644 board/xiaomi/mocha/mocha.c create mode 100644 board/xiaomi/mocha/mocha.env create mode 100644 configs/mocha_defconfig create mode 100644 doc/board/xiaomi/index.rst create mode 100644 doc/board/xiaomi/mocha.rst create mode 100644 drivers/video/lp855x_backlight.c create mode 100644 drivers/video/sharp-lq079l1sx01.c create mode 100644 include/configs/mocha.h -- 2.43.0

1 7

[PATCH] ARM: renesas: Consistently enable ENV_OVERWRITE on Renesas R-Car
by Marek Vasut 22 Dec '24

22 Dec '24

Move CONFIG_ENV_OVERWRITE=y into commont renesas_rcar.config to make sure this configuration option is consistently enabled on all of Renesas R-Car Gen2, Gen3, Gen4. Currently this option is not enabled on Gen4, this fix corrects that omission. Signed-off-by: Marek Vasut <marek.vasut+renesas(a)mailbox.org> --- Cc: Adam Ford <aford173(a)gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu(a)nigauri.org> Cc: Paul Barker <paul.barker.ct(a)bp.renesas.com> Cc: Sumit Garg <sumit.garg(a)linaro.org> Cc: Tom Rini <trini(a)konsulko.com> Cc: u-boot(a)lists.denx.de --- configs/renesas_rcar.config | 1 + configs/renesas_rcar2.config | 1 - configs/renesas_rcar3.config | 1 - 3 files changed, 1 insertion(+), 2 deletions(-) diff --git a/configs/renesas_rcar.config b/configs/renesas_rcar.config index 351803b743a..d0a12f266aa 100644 --- a/configs/renesas_rcar.config +++ b/configs/renesas_rcar.config @@ -17,6 +17,7 @@ CONFIG_DM_REGULATOR_FIXED=y CONFIG_DM_REGULATOR_GPIO=y CONFIG_DM_SPI=y CONFIG_DM_SPI_FLASH=y +CONFIG_ENV_OVERWRITE=y CONFIG_FIT=y CONFIG_HUSH_PARSER=y CONFIG_MTD=y diff --git a/configs/renesas_rcar2.config b/configs/renesas_rcar2.config index 74dfd41f1a3..4ffc4d05882 100644 --- a/configs/renesas_rcar2.config +++ b/configs/renesas_rcar2.config @@ -14,7 +14,6 @@ CONFIG_CMD_USB=y CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x4f000000 CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK=y CONFIG_ENV_IS_IN_SPI_FLASH=y -CONFIG_ENV_OVERWRITE=y CONFIG_ENV_SECT_SIZE=0x40000 CONFIG_ENV_SIZE=0x40000 CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y diff --git a/configs/renesas_rcar3.config b/configs/renesas_rcar3.config index 228e1b4c679..7f7fab7df1d 100644 --- a/configs/renesas_rcar3.config +++ b/configs/renesas_rcar3.config @@ -2,5 +2,4 @@ CONFIG_BITBANGMII=y CONFIG_BITBANGMII_MULTI=y -CONFIG_ENV_OVERWRITE=y CONFIG_SYS_PBSIZE=2068 -- 2.45.2

1 0

[PATCH] net: rswitch: Do not register disabled ports as ethernet devices
by Marek Vasut 21 Dec '24

21 Dec '24

In case an rswitch port is described as disabled in DT, do not register it as ethernet device in U-Boot. This way, such ports cannot be accessed from U-Boot command line. Signed-off-by: Marek Vasut <marek.vasut+renesas(a)mailbox.org> --- Cc: Enric Balletbo i Serra <eballetb(a)redhat.com> Cc: Joe Hershberger <joe.hershberger(a)ni.com> Cc: Nobuhiro Iwamatsu <iwamatsu(a)nigauri.org> Cc: Ramon Fried <rfried.dev(a)gmail.com> Cc: Tom Rini <trini(a)konsulko.com> Cc: u-boot(a)lists.denx.de --- drivers/net/rswitch.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/rswitch.c b/drivers/net/rswitch.c index 97b5d1b75c1..57eff748c90 100644 --- a/drivers/net/rswitch.c +++ b/drivers/net/rswitch.c @@ -1113,6 +1113,9 @@ static int rswitch_bind(struct udevice *parent) return -ENOENT; ofnode_for_each_subnode(node, ports_np) { + if (!ofnode_is_enabled(node)) + continue; + ret = device_bind_with_driver_data(parent, drv, ofnode_get_name(node), (ulong)priv, node, &dev); -- 2.45.2

1 0

[PATCH v2] arm64: renesas: Make bottom 128 MiB of DRAM available in EL3
by Marek Vasut 21 Dec '24

21 Dec '24

In case U-Boot runs in EL3, which is the highest privilege level on ARM64, there can be no firmware running that would restrict access to the bottom 128 MiB of DRAM. In fact, it is likely that U-Boot would have to load that firmware into those bottom 128 MiB of DRAM and start that firmware. Make those bottom 128 MiB of DRAM available in case U-Boot runs in EL3 to allow loading the firmware to that area. Signed-off-by: Marek Vasut <marek.vasut+renesas(a)mailbox.org> --- Cc: Adam Ford <aford173(a)gmail.com> Cc: Biju Das <biju.das.jz(a)bp.renesas.com> Cc: Hai Pham <hai.pham.ud(a)renesas.com> Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj(a)bp.renesas.com> Cc: Nobuhiro Iwamatsu <iwamatsu(a)nigauri.org> Cc: Paul Barker <paul.barker.ct(a)bp.renesas.com> Cc: Simon Glass <sjg(a)chromium.org> Cc: Tom Rini <trini(a)konsulko.com> Cc: u-boot(a)lists.denx.de --- V2: Make this non-Gen4 specific, Gen3 an benefit from this too --- board/renesas/rcar-common/common.c | 32 +++++++++++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/board/renesas/rcar-common/common.c b/board/renesas/rcar-common/common.c index 4e35e0151c9..90eb468e4c4 100644 --- a/board/renesas/rcar-common/common.c +++ b/board/renesas/rcar-common/common.c @@ -15,6 +15,7 @@ #include <asm/io.h> #include <dm/uclass-internal.h> #include <asm/arch/renesas.h> +#include <asm/system.h> #include <linux/libfdt.h> #ifdef CONFIG_RCAR_64 @@ -23,13 +24,42 @@ DECLARE_GLOBAL_DATA_PTR; int dram_init(void) { - return fdtdec_setup_mem_size_base(); + int ret = fdtdec_setup_mem_size_base(); + + if (current_el() == 3 && gd->ram_base == 0x48000000) { + /* + * If this U-Boot runs in EL3, make the bottom 128 MiB + * available for loading of follow up firmware blobs. + */ + gd->ram_base -= 0x8000000; + gd->ram_size += 0x8000000; + } + + return ret; } int dram_init_banksize(void) { + int bank; + fdtdec_setup_memory_banksize(); + if (current_el() != 3) + return 0; + + for (bank = 0; bank < CONFIG_NR_DRAM_BANKS; bank++) { + if (gd->bd->bi_dram[bank].start != 0x48000000) + continue; + + /* + * If this U-Boot runs in EL3, make the bottom 128 MiB + * available for loading of follow up firmware blobs. + */ + gd->bd->bi_dram[bank].start -= 0x8000000; + gd->bd->bi_dram[bank].size += 0x8000000; + break; + } + return 0; } -- 2.45.2

1 0

Correct Default SPL_SIZE_LIMIT for Cyclone/Arria V (SOCFPGA_GEN5)
by Thomas Carpenter 21 Dec '24

21 Dec '24

Hi Not sure how you deal with contributions. There is a bug in the "arch/arm/mach-socfpga/Kconfig file. The default SPL_SIZE_LIMIT parameter for TARGET_SOCFPGA_GEN5 should be 60kB (0xF000) not 64kB (0x10000). Referring to the Cyclone V Hard Processor System Technical Reference Manual (same for Arria V), Section A-32, "Loading the Preloader Image". The upper 4kB of the on-chip RAM is reserved by the Boot ROM, meaning only 60kB is available for the preloader. If the SPL image size extends into this region, it causes the boot ROM to crash. Patch for `arch/arm/mach-socfpga/Kconfig`: @@ -23,7 +23,7 @@ config SOCFPGA_SECURE_VAB_AUTH_ALLOW_NON_FIT_IMAGE depends on SOCFPGA_SECURE_VAB_AUTH config SPL_SIZE_LIMIT - default 0xF000 if TARGET_SOCFPGA_GEN5 + default 0x10000 if TARGET_SOCFPGA_GEN5 config SPL_SIZE_LIMIT_PROVIDE_STACK default 0x200 if TARGET_SOCFPGA_GEN5 The incorrect limit has clearly existed for a while (same issue is in the altera-opensource/u-boot-socfpga fork as well), it's probably just not caused an issue because the default SPL config is compact enough to not exceed the actual limit by pure luck rather than by validation. In our custom configuration we exceeded the 0xF000 limit (with no error from the build tools) - took a while to figure out why the processor would fail to boot as a result. Kind Regards, Dr Thomas Carpenter

1 0

[PATCH 1/1] cmd/setexpr: support concatenation of direct strings
by Heinrich Schuchardt 21 Dec '24

21 Dec '24

Up to now the setexpr command only supported concatenating string provided by reference. Allow directly passing stings. With this patch setexpr.s foo '1' + '3' sets variable $foo to the value '13'. Update the unit test for "setexpr.s fred 0". Add a new unit test for "setexpr.s fred '1' + '3'". Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt(a)canonical.com> --- cmd/setexpr.c | 54 ++++++++++++++++++++++++++++++++-------------- test/cmd/setexpr.c | 7 +++++- 2 files changed, 44 insertions(+), 17 deletions(-) diff --git a/cmd/setexpr.c b/cmd/setexpr.c index e111b8ba98a..c45fa85c887 100644 --- a/cmd/setexpr.c +++ b/cmd/setexpr.c @@ -35,9 +35,37 @@ struct expr_arg { }; }; +/** + * arg_set_str() - copy string to expression argument + * + * The string is truncated to 64 KiB plus NUL terminator. + * + * @p: pointer to string + * @argp: pointer to expression argument + * Return: 0 on success, -ENOMEM if out of memory + */ +static int arg_set_str(void *p, struct expr_arg *argp) +{ + int len; + char *str; + + /* Maximum string length of 64 KiB plus NUL terminator */ + len = strnlen((char *)p, SZ_64K) + 1; + str = malloc(len); + if (!str) { + printf("Out of memory\n"); + return -ENOMEM; + } + memcpy(str, p, len); + str[len - 1] = '\0'; + argp->sval = str; + return 0; +} + static int get_arg(char *s, int w, struct expr_arg *argp) { struct expr_arg arg; + int ret; /* * If the parameter starts with a '*' then assume it is a pointer to @@ -47,8 +75,6 @@ static int get_arg(char *s, int w, struct expr_arg *argp) ulong *p; ulong addr; ulong val; - int len; - char *str; addr = hextoul(&s[1], NULL); switch (w) { @@ -66,18 +92,10 @@ static int get_arg(char *s, int w, struct expr_arg *argp) break; case CMD_DATA_SIZE_STR: p = map_sysmem(addr, SZ_64K); - - /* Maximum string length of 64KB plus terminator */ - len = strnlen((char *)p, SZ_64K) + 1; - str = malloc(len); - if (!str) { - printf("Out of memory\n"); - return -ENOMEM; - } - memcpy(str, p, len); - str[len - 1] = '\0'; + ret = arg_set_str(p, &arg); unmap_sysmem(p); - arg.sval = str; + if (ret) + return ret; break; case 4: p = map_sysmem(addr, sizeof(u32)); @@ -93,9 +111,13 @@ static int get_arg(char *s, int w, struct expr_arg *argp) break; } } else { - if (w == CMD_DATA_SIZE_STR) - return -EINVAL; - arg.ival = hextoul(s, NULL); + if (w == CMD_DATA_SIZE_STR) { + ret = arg_set_str(s, &arg); + if (ret) + return ret; + } else { + arg.ival = hextoul(s, NULL); + } } *argp = arg; diff --git a/test/cmd/setexpr.c b/test/cmd/setexpr.c index 21a3268bd81..00d373f35ae 100644 --- a/test/cmd/setexpr.c +++ b/test/cmd/setexpr.c @@ -310,7 +310,8 @@ static int setexpr_test_str(struct unit_test_state *uts) ut_assertok(env_set("fred", "x")); start_mem = ut_check_free(); strcpy(buf, "hello"); - ut_asserteq(1, run_command("setexpr.s fred 0", 0)); + ut_asserteq(0, run_command("setexpr.s fred 0", 0)); + ut_asserteq_str("0", env_get("fred")); ut_assertok(ut_check_delta(start_mem)); ut_assertok(env_set("fred", "12345")); @@ -335,6 +336,10 @@ static int setexpr_test_str_oper(struct unit_test_state *uts) ulong start_mem; char *buf; + /* Test concatenation of strings */ + ut_assertok(run_command("setexpr.s fred '1' + '3'", 0)); + ut_asserteq_str("13", env_get("fred")); + buf = map_sysmem(0, BUF_SIZE); memset(buf, '\xff', BUF_SIZE); strcpy(buf, "hello"); -- 2.47.1

2 1

[PATCH] doc/develop/distro.rst: Better document upstream locations of extlinux.conf
by Tom Rini 21 Dec '24

21 Dec '24

First, the "Boot Loader Specification" link has moved to a new location, so link to that directly. Second, that link does not document as much of the extlinux.conf format as I recall the old version doing at least. However, the Syslinux Wiki is the current location of the documentation linked to in doc/README.pxe and so add a link to that wiki as well. Signed-off-by: Tom Rini <trini(a)konsulko.com> --- doc/develop/distro.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/develop/distro.rst b/doc/develop/distro.rst index 637bc27fc2d7..d80c2eff6192 100644 --- a/doc/develop/distro.rst +++ b/doc/develop/distro.rst @@ -68,7 +68,8 @@ Boot Configuration Files The standard format for boot configuration files is that of extlinux.conf, as handled by U-Boot's "syslinux" (disk) or "pxe boot" (network). This is roughly -as specified at `Boot Loader Specification`_: +as specified at `Boot Loader Specification`_ and more completely at `The +Syslinux Wiki`_: ... with the exceptions that the Boot Loader Specification document: @@ -440,7 +441,8 @@ way in future u-boot versions. In particular the <device type>_boot variables (e.g. mmc_boot, usb_boot) are a strictly internal implementation detail and must not be used as a public interface. -.. _`Boot Loader Specification`: https://systemd.io/BOOT_LOADER_SPECIFICATION/ +.. _`Boot Loader Specification`: https://uapi-group.org/specifications/specs/boot_loader_specification/ +.. _`The Syslinux Wiki`: https://wiki.syslinux.org/wiki/index.php?title=PXELINUX .. sectionauthor:: (C) Copyright 2014 Red Hat Inc. .. sectionauthor:: Copyright (c) 2014-2015, NVIDIA CORPORATION. All rights reserved. -- 2.43.0

1 1