From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
peter.maydell@linaro.org, crosthwaite.peter@gmail.com,
agraf@suse.de
Subject: [Qemu-devel] [PATCH v4 0/3] ARM virt: Silence dtc warnings
Date: Tue, 26 Jun 2018 22:21:29 +0200 [thread overview]
Message-ID: <1530044492-24921-1-git-send-email-eric.auger@redhat.com> (raw)
When running dtc on the guest /proc/device-tree, we get the
following warnings: "Warning (unit_address_vs_reg): Node <name>
has a reg or ranges property, but no unit name", with name:
/intc, /intc/its, /intc/v2m, /memory.
This series removes those warnings by adding the unit address to
the corresponding node names.
This is based on Peter's target-arm.next
Best Regards
Eric
History:
v3 -> v4:
- rebased on Peter's target-arm.next
v2 -> v3:
- only nop root /memory and /memory@unit-address nodes
- remove a deprecated comment
v1 -> v2:
- nop existing node-name and node-name@unit-address nodes and
add our owns.
- added 1st patch device_tree: Add qemu_fdt_node_unit_path
Eric Auger (3):
device_tree: Add qemu_fdt_node_unit_path
hw/arm/virt: Silence dtc /intc warnings
hw/arm/virt: Silence dtc /memory warning
device_tree.c | 55 ++++++++++++++++++++++++++++++++++
hw/arm/boot.c | 41 ++++++++++++++------------
hw/arm/virt.c | 70 +++++++++++++++++++++++++-------------------
include/sysemu/device_tree.h | 16 ++++++++++
4 files changed, 134 insertions(+), 48 deletions(-)
--
2.5.5
next reply other threads:[~2018-06-26 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 20:21 Eric Auger [this message]
2018-06-26 20:21 ` [Qemu-devel] [PATCH v4 1/3] device_tree: Add qemu_fdt_node_unit_path Eric Auger
2018-06-26 20:21 ` [Qemu-devel] [PATCH v4 2/3] hw/arm/virt: Silence dtc /intc warnings Eric Auger
2018-06-26 20:21 ` [Qemu-devel] [PATCH v4 3/3] hw/arm/virt: Silence dtc /memory warning Eric Auger
2018-06-28 14:15 ` [Qemu-devel] [PATCH v4 0/3] ARM virt: Silence dtc warnings Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1530044492-24921-1-git-send-email-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=agraf@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=eric.auger.pro@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).