diff options
| author | Daniel Henrique Barboza <danielhb413@gmail.com> | 2021-12-17 17:57:13 +0100 |
|---|---|---|
| committer | Cédric Le Goater <clg@kaod.org> | 2021-12-17 17:57:13 +0100 |
| commit | bbfbbff5fc0fb4cee42ed22c4430cc5d68bacc27 (patch) | |
| tree | 34ab94918bd989b4a95274a9a6bb8e99752008b8 /docs/system | |
| parent | 3e8f7158153f035477d975869d22d07da719f0be (diff) | |
| download | qemu-bbfbbff5fc0fb4cee42ed22c4430cc5d68bacc27.zip qemu-bbfbbff5fc0fb4cee42ed22c4430cc5d68bacc27.tar.gz qemu-bbfbbff5fc0fb4cee42ed22c4430cc5d68bacc27.tar.bz2 | |
ppc/pnv.c: fix "system-id" FDT when -uuid is set
Setting -uuid in the pnv machine does not work:
./qemu-system-ppc64 -machine powernv8,accel=tcg -uuid 7ff61ca1-a4a0-4bc1-944c-abd114a35e80
qemu-system-ppc64: error creating device tree: (fdt_property_string(fdt, "system-id", buf)): FDT_ERR_BADSTATE
This happens because we're using fdt_property_string(), which is a
sequential write function that is supposed to be used when we're
building a new FDT, in a case where read/writing into an existing FDT.
Fix it by using fdt_setprop_string() instead.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20211207094858.744386-1-danielhb413@gmail.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Diffstat (limited to 'docs/system')
0 files changed, 0 insertions, 0 deletions