971f552e09
This allows the fw_cfg device to be recognized by the guest linux kernel. This becomes more relavnt in the following cl where I add the option to load files into the guest via fw_cfg. The Linux kernel already has a fw_cfg driver that will automatically load these files under /sys when CONFIG_FW_CFG_SYSFS is enabled in the kernel config For arm we must add fw_cfg to the devices tree Signed-off-by: Alex Orozco <alexorozco@google.com>
29 lines
856 B
TOML
29 lines
856 B
TOML
[package]
|
|
authors = ["The Chromium OS Authors"]
|
|
edition = "2021"
|
|
name = "arch"
|
|
version = "0.1.0"
|
|
|
|
[features]
|
|
default = []
|
|
fw_cfg = []
|
|
kvm = ["hypervisor/kvm"]
|
|
sev_snp = []
|
|
tdx = []
|
|
|
|
[dependencies]
|
|
anyhow = { workspace = true }
|
|
byteorder = { workspace = true }
|
|
hypervisor = { path = "../hypervisor" }
|
|
libc = { workspace = true }
|
|
linux-loader = { workspace = true, features = ["bzimage", "elf", "pe"] }
|
|
log = { workspace = true }
|
|
serde = { workspace = true, features = ["derive", "rc"] }
|
|
thiserror = { workspace = true }
|
|
uuid = { workspace = true }
|
|
vm-memory = { workspace = true, features = ["backend-bitmap", "backend-mmap"] }
|
|
vmm-sys-util = { workspace = true, features = ["with-serde"] }
|
|
|
|
[target.'cfg(any(target_arch = "aarch64", target_arch = "riscv64"))'.dependencies]
|
|
fdt_parser = { version = "0.1.5", package = "fdt" }
|
|
vm-fdt = { workspace = true }
|