On Thu, Jun 9, 2016 at 6:08 AM, KONRAD Frederic
wrote:
> Hi Alistair,
>
>
> Le 13/05/2016 à 00:45, Alistair Francis a écrit :
>>
>> Add memory io handlers that glue the register API to the memory API.
>> Just translation functions at this stage. Although it does allow for
>> devices to be created
On 21 June 2016 at 01:46, Alistair Francis wrote:
> On Thu, Jun 9, 2016 at 12:03 PM, Peter Maydell
> wrote:
>> Why do we need to handle big vs little endian separately rather
>> than just having the memory region say which it is and letting
>> the core memory system handle things appropriately ?
On Thu, Jun 9, 2016 at 12:03 PM, Peter Maydell wrote:
> On 12 May 2016 at 23:45, Alistair Francis wrote:
>> Add memory io handlers that glue the register API to the memory API.
>> Just translation functions at this stage. Although it does allow for
>> devices to be created without all-in-one mmio
On 12 May 2016 at 23:45, Alistair Francis wrote:
> Add memory io handlers that glue the register API to the memory API.
> Just translation functions at this stage. Although it does allow for
> devices to be created without all-in-one mmio r/w handlers.
>
> This patch also adds the RegisterInfoArra
Hi Alistair,
Le 13/05/2016 à 00:45, Alistair Francis a écrit :
Add memory io handlers that glue the register API to the memory API.
Just translation functions at this stage. Although it does allow for
devices to be created without all-in-one mmio r/w handlers.
This patch also adds the RegisterI
Add memory io handlers that glue the register API to the memory API.
Just translation functions at this stage. Although it does allow for
devices to be created without all-in-one mmio r/w handlers.
This patch also adds the RegisterInfoArray struct, which allows all of
the individual RegisterInfo s
