Re: [PATCH] cmd: pxe_utils: sysboot: fix crash if either board or soc are not set.

On Tue, Jun 15, 2021 at 7:15 PM Dimitri John Ledkov wrote: > > Hi, this patch is still not pulled into master. It still applies > cleanly onto master. > > Can this patch please be pulled in? It fixes a crash of uboot. > Without this patch upstream, people who build their own uboot cannot > boot st

Re: [PATCH] cmd: pxe_utils: sysboot: fix crash if either board or soc are not set.

Hi, this patch is still not pulled into master. It still applies cleanly onto master. Can this patch please be pulled in? It fixes a crash of uboot. Without this patch upstream, people who build their own uboot cannot boot stock Ubuntu images. What can I do, for this patch to be applied? On Sat,

Re: [PATCH] cmd: pxe_utils: sysboot: fix crash if either board or soc are not set.

On Wed, Apr 21, 2021 at 5:32 PM Dimitri John Ledkov wrote: > > If the environment does not have "soc" or "board" set, and fdtdir > option is specified in extlinux.conf, the bootloader will crash whilst > dereferencing a null pointer. Add a guard against null soc or > board. Fixes a crash of qemu-r

Re: [PATCH] cmd: pxe_utils: sysboot: fix crash if either board or soc are not set.

Hi qemu-board meaintainers, The below patch affects any boards that do not have either board or soc variables set. Of which non-x86 qemu boards are exactly that, preventing to netboot the same rootfs across multiple boards and qemu at the same time. Another alternative would be for all non-x86 q

[PATCH] cmd: pxe_utils: sysboot: fix crash if either board or soc are not set.

If the environment does not have "soc" or "board" set, and fdtdir option is specified in extlinux.conf, the bootloader will crash whilst dereferencing a null pointer. Add a guard against null soc or board. Fixes a crash of qemu-riscv64_smode configuration, which does not have CONFIG_SYS_SOC defined