summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudwig Nussel <[email protected]>2026-05-04 09:10:23 +0200
committerTom Rini <[email protected]>2026-05-08 15:49:27 -0600
commit18806dae0e6fa9e0912a258e15f61b1b346dfdbc (patch)
treea21782e629d680b7c6c196115552336ebee97e57
parent55b152e6f0204e0b769f66ffd40ad02081f9bff0 (diff)
virtio: fix boot device hunting in qemu with virtio
Commit 70101c3217ae ("virtio: mmio: Return error codes on probe failures") returns -ENODEV where it would return 0 before. That path is apparently hit in qemu and breaks boot device discovery (virtio_bootdev_hunt() expects only ENOENT). So return -ENOENT in that path instead. The remaining two error returns in the function are untouched as I don't know where they play a role. Signed-off-by: Ludwig Nussel <[email protected]> Reviewed-by: Simon Glass <[email protected]> Acked-by: Kuan-Wei Chiu <[email protected]>
-rw-r--r--drivers/virtio/virtio_mmio.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c
index 62afe609ec0..d90d8309f99 100644
--- a/drivers/virtio/virtio_mmio.c
+++ b/drivers/virtio/virtio_mmio.c
@@ -372,7 +372,7 @@ static int virtio_mmio_probe(struct udevice *udev)
* virtio-mmio device with an ID 0 is a (dummy) placeholder
* with no function. End probing now with no error reported.
*/
- return -ENODEV;
+ return -ENOENT;
}
uc_priv->vendor = readl(priv->base + VIRTIO_MMIO_VENDOR_ID);