The existing sandbox implementation of virtio only tests the basic API.
It is not able to provide a block device, for example.
Add a new implementation which operations at a higher level. It makes
use of the existing MMIO driver to perform virtio operations.
This emulator-device should be the parent of a function-specific
emulator. That emulator uses this MMIO transport to communicate with the
controller:
virtio-blk {
compatible = "sandbox,virtio-blk-emul";
mmio {
compatible = "sandbox,virtio-emul";
};
};
A new UCLASS_VIRTIO_EMUL uclass is created for the child devices, which
implement the actual function (block device, random-number generator,
etc.)
Signed-off-by: Simon Glass <sjg@chromium.org>
43 lines
1.1 KiB
Plaintext
43 lines
1.1 KiB
Plaintext
CONFIG_TEXT_BASE=0
|
|
CONFIG_SYS_MALLOC_LEN=0x2000000
|
|
CONFIG_ENV_SIZE=0x2000
|
|
CONFIG_DEFAULT_DEVICE_TREE="sandbox"
|
|
CONFIG_SYS_LOAD_ADDR=0x0
|
|
CONFIG_PCI=y
|
|
# CONFIG_SANDBOX_SDL is not set
|
|
# CONFIG_EFI_LOADER is not set
|
|
CONFIG_ANDROID_BOOT_IMAGE=y
|
|
CONFIG_TIMESTAMP=y
|
|
CONFIG_FIT=y
|
|
# CONFIG_BOOTSTD_FULL is not set
|
|
# CONFIG_BOOTMETH_CROS is not set
|
|
# CONFIG_BOOTMETH_VBE is not set
|
|
CONFIG_IMAGE_PRE_LOAD=y
|
|
CONFIG_IMAGE_PRE_LOAD_SIG=y
|
|
CONFIG_USE_BOOTCOMMAND=y
|
|
CONFIG_BOOTCOMMAND="run distro_bootcmd"
|
|
# CONFIG_CMD_BOOTD is not set
|
|
# CONFIG_CMD_BOOTM is not set
|
|
# CONFIG_CMD_BOOTI is not set
|
|
# CONFIG_CMD_ELF is not set
|
|
# CONFIG_CMD_EXTENSION is not set
|
|
# CONFIG_CMD_DATE is not set
|
|
CONFIG_OF_CONTROL=y
|
|
CONFIG_SYS_RELOC_GD_ENV_ADDR=y
|
|
CONFIG_NO_NET=y
|
|
# CONFIG_ACPIGEN is not set
|
|
CONFIG_AXI=y
|
|
CONFIG_AXI_SANDBOX=y
|
|
CONFIG_SANDBOX_GPIO=y
|
|
CONFIG_PCI_SANDBOX=y
|
|
CONFIG_DM_RTC=y
|
|
CONFIG_SOUND=y
|
|
CONFIG_SYSRESET=y
|
|
CONFIG_TIMER=y
|
|
# CONFIG_VIRTIO_MMIO is not set
|
|
# CONFIG_VIRTIO_PCI is not set
|
|
# CONFIG_VIRTIO_SANDBOX is not set
|
|
# CONFIG_VIRTIO_SANDBOX_EMUL is not set
|
|
# CONFIG_GENERATE_ACPI_TABLE is not set
|
|
CONFIG_TOOLS_MKEFICAPSULE=y
|