On 12/04/2011 11:15 PM, Peter Maydell wrote:
> On 4 December 2011 12:17, Avi Kivity wrote:
> > On 12/02/2011 04:49 PM, Peter Maydell wrote:
> >> However what I found is that the addresses passed to the read/write
> >> functions aren't what I would expect. For instance if the board
> >> maps the co
On 4 December 2011 12:17, Avi Kivity wrote:
> On 12/02/2011 04:49 PM, Peter Maydell wrote:
>> However what I found is that the addresses passed to the read/write
>> functions aren't what I would expect. For instance if the board
>> maps the container at address 0x1e00, then a read from 0x1e000
On 12/02/2011 04:49 PM, Peter Maydell wrote:
> Hi; I was working on a refactoring of the ARM 11MPCore/A9MP private
> peripherals and encountered something odd. Rather than having a single
> large mmio region, I tried splitting into several regions, like this:
>
> memory_region_init(&s->containe
Hi; I was working on a refactoring of the ARM 11MPCore/A9MP private
peripherals and encountered something odd. Rather than having a single
large mmio region, I tried splitting into several regions, like this:
memory_region_init(&s->container, "a9mp-priv-container", 0x2000);
memory_region_i
