[PATCH v2] vbe: Allow probing the VBE bootmeth to fail in OS fixup
authorSimon Glass <sjg@chromium.org>
Thu, 12 Jan 2023 23:48:54 +0000 (16:48 -0700)
committerVagrant Cascadian <vagrant@debian.org>
Wed, 18 Jan 2023 01:57:16 +0000 (01:57 +0000)
commitcf13ef80880733e7186679a3dfcc348b0d710acc
treebf5b9016a0228628ec22f49d92b6afa665edbb36
parentfaa5101a6f113e02cd88c6660037807f7102c6a2
[PATCH v2] vbe: Allow probing the VBE bootmeth to fail in OS fixup

To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
 Karsten Merker <merker@debian.org>,
 Heinrich Schuchardt <xypron.glpk@gmx.de>
Message-Id: <20230112234854.936325-1-sjg@chromium.org>
Origin: https://patchwork.ozlabs.org/project/uboot/patch/20230112234854.936325-1-sjg@chromium.org/
Bug-Debian: https://bugs.debian.org/1028343

This device is created when there are no bootmeths defined in the device
tree. But it cannot be probed without a device tree node.

For now, ignore a probe failure.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reported-by: Karsten Merker <merker@debian.org>
Suggested-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Fixes: a56f663f0707 ("vbe: Add info about the VBE device to the fwupd node")
Gbp-Pq: Topic riscv64
Gbp-Pq: Name vbe-Allow-probing-the-VBE-bootmeth-to-fail-in-OS-fixup.patch
boot/vbe_simple_os.c