Somewhat clumsy since it needs a variable sized region.
Signed-off-by: Avi Kivity a...@redhat.com
---
v1.1: set access size validity for omap gpmc region to allow only 32-bit
accesses
hw/omap.h |3 ++-
hw/omap_gpmc.c | 56
On 9 August 2011 10:02, Avi Kivity a...@redhat.com wrote:
+static const MemoryRegionOps omap_gpmc_ops = {
+ .read = omap_gpmc_read,
+ .write = omap_gpmc_write,
+ .endianness = DEVICE_NATIVE_ENDIAN,
+ .valid = {
+ .min_access_size = 4,
+ .max_access_size = 4,
+
On 08/09/2011 12:23 PM, Peter Maydell wrote:
On 9 August 2011 10:02, Avi Kivitya...@redhat.com wrote:
+static const MemoryRegionOps omap_gpmc_ops = {
+.read = omap_gpmc_read,
+.write = omap_gpmc_write,
+.endianness = DEVICE_NATIVE_ENDIAN,
+.valid = {
+
On 9 August 2011 10:26, Avi Kivity a...@redhat.com wrote:
On 08/09/2011 12:23 PM, Peter Maydell wrote:
On 9 August 2011 10:02, Avi Kivitya...@redhat.com wrote:
+static const MemoryRegionOps omap_gpmc_ops = {
+ .read = omap_gpmc_read,
+ .write = omap_gpmc_write,
+
On 08/09/2011 12:41 PM, Peter Maydell wrote:
On 9 August 2011 10:26, Avi Kivitya...@redhat.com wrote:
On 08/09/2011 12:23 PM, Peter Maydell wrote:
On 9 August 2011 10:02, Avi Kivitya...@redhat.comwrote:
+static const MemoryRegionOps omap_gpmc_ops = {
+.read =
