Sure, i'm very interested in.
I've used another implementation that still require large amount of data to be
allocated (but with O(1) search time)
Have a good day
--- Mer 2/3/11, Vincent Palatin ha scritto:
> Da: Vincent Palatin
> Oggetto: Re: [Qemu-devel] Memory Map
Hi,
On Wed, Mar 2, 2011 at 12:11, Salvatore Lionetti
wrote:
> Still now, some memory region is called with base+offset.
>
> So:
>
> [0x204] <= value (write from uP register)
> cause
> read(opaque, offset=204, value)
>
> while
> [0x504] <= value (write from uP register)
> cause
> read(opaque, offs
504] <= value (write from uP register)
cause
read(opaque, offset=4, value)
The two opaque are different as expected.
Where i am wrong?
--- Ven 25/2/11, Blue Swirl ha scritto:
> Da: Blue Swirl
> Oggetto: Re: [Qemu-devel] Memory Map
> A: "Salvatore Lionetti"
> Cc: qe
On Thu, Feb 24, 2011 at 11:08 AM, Salvatore Lionetti
wrote:
> Hi,
>
> This is what my board do
>
> cpu_register_physical_memory(0, 128*1024*1024, ...)
> cpu_register_physical_memory(0xFF80, 8*1024*1024, ...)
>
> and this layout does not change over the entire live (virtual) of the board.
>
> F
Hi,
This is what my board do
cpu_register_physical_memory(0, 128*1024*1024, ...)
cpu_register_physical_memory(0xFF80, 8*1024*1024, ...)
and this layout does not change over the entire live (virtual) of the board.
For the following offset (1st column) and size in bytes (2nd column)
{0x00
