From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH 1/4] uninorth: add impl min_access_size and max_access_size to unin_ops
Date: Sun, 6 May 2018 15:20:02 +0100 [thread overview]
Message-ID: <20180506142005.19580-2-mark.cave-ayland@ilande.co.uk> (raw)
In-Reply-To: <20180506142005.19580-1-mark.cave-ayland@ilande.co.uk>
>From testing all my local images the uninorth registers are only ever
read or written with 32-bit accesses.
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
---
hw/pci-host/uninorth.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/hw/pci-host/uninorth.c b/hw/pci-host/uninorth.c
index ba76b84dbc..a658f9230a 100644
--- a/hw/pci-host/uninorth.c
+++ b/hw/pci-host/uninorth.c
@@ -548,6 +548,10 @@ static const MemoryRegionOps unin_ops = {
.read = unin_read,
.write = unin_write,
.endianness = DEVICE_BIG_ENDIAN,
+ .impl = {
+ .min_access_size = 4,
+ .max_access_size = 4,
+ },
};
static void unin_init(Object *obj)
--
2.11.0
next prev parent reply other threads:[~2018-05-06 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 14:20 [Qemu-devel] [PATCH 0/4] uninorth/macio: minor fixups Mark Cave-Ayland
2018-05-06 14:20 ` Mark Cave-Ayland [this message]
2018-06-04 0:39 ` [Qemu-devel] [PATCH 1/4] uninorth: add impl min_access_size and max_access_size to unin_ops David Gibson
2018-05-06 14:20 ` [Qemu-devel] [PATCH 2/4] macio: add trace-events to timer device Mark Cave-Ayland
2018-05-07 13:37 ` Philippe Mathieu-Daudé
2018-06-04 0:38 ` David Gibson
2018-05-06 14:20 ` [Qemu-devel] [PATCH 3/4] macio: add impl min_access_size and max_access_size to timer_ops Mark Cave-Ayland
2018-05-06 14:20 ` [Qemu-devel] [PATCH 4/4] uninorth: remove token register from uninorth device Mark Cave-Ayland
2018-05-07 13:38 ` Philippe Mathieu-Daudé
2018-06-04 0:41 ` David Gibson
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=20180506142005.19580-2-mark.cave-ayland@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).