boards: Fix QEMU_VIRTIO_MMIO_NUM

Summary:
- I noticed that device discovery for virtio-mmio devices does not
  work without bus=virtio-mmio-bus.x option. Without this option,
  qemu assigns the virtio device into the virtio-mmio space
  in reverse order automatically.
- To fix this issue, we must specify the correct numbers for the
  target machines. (i.e. arm32/64->32, rv32/64->8)

Impact:
- None

Testing:
- Tested with qemu-7.2.4

Signed-off-by: Masayuki Ishikawa <Masayuki.Ishikawa@jp.sony.com>
This commit is contained in:
Masayuki Ishikawa 2023-08-22 15:23:18 +09:00 committed by Xiang Xiao
parent 1c860f38e7
commit cc906e28e4
3 changed files with 3 additions and 3 deletions

View file

@ -39,7 +39,7 @@
#define QEMU_VIRTIO_MMIO_BASE 0x0a000000
#define QEMU_VIRTIO_MMIO_REGSIZE 0x200
#define QEMU_VIRTIO_MMIO_IRQ 48
#define QEMU_VIRTIO_MMIO_NUM 4
#define QEMU_VIRTIO_MMIO_NUM 32
/****************************************************************************
* Private Functions

View file

@ -39,7 +39,7 @@
#define QEMU_VIRTIO_MMIO_BASE 0x0a000000
#define QEMU_VIRTIO_MMIO_REGSIZE 0x200
#define QEMU_VIRTIO_MMIO_IRQ 48
#define QEMU_VIRTIO_MMIO_NUM 4
#define QEMU_VIRTIO_MMIO_NUM 32
/****************************************************************************
* Private Functions

View file

@ -45,7 +45,7 @@
#else
# define QEMU_VIRTIO_MMIO_IRQ 28
#endif
#define QEMU_VIRTIO_MMIO_NUM 4
#define QEMU_VIRTIO_MMIO_NUM 8
/****************************************************************************
* Private Functions