On Sun, Feb 28, 2016 at 7:28 AM, Peter Maydell wrote:
> On 27 February 2016 at 23:14, Peter Crosthwaite
> wrote:
>> On Tue, Jan 19, 2016 at 9:53 AM, Peter Maydell
>> wrote:
>>> Can we have a doc comment so we have something that defines what
>>> values data_swab accepts? (it's not just a bool).
On 27 February 2016 at 23:14, Peter Crosthwaite
wrote:
> On Tue, Jan 19, 2016 at 9:53 AM, Peter Maydell
> wrote:
>> Can we have a doc comment so we have something that defines what
>> values data_swab accepts? (it's not just a bool).
>>
>
> This is difficult to capture without writing to whole d
On Tue, Jan 19, 2016 at 9:53 AM, Peter Maydell wrote:
> On 18 January 2016 at 07:12, Peter Crosthwaite
> wrote:
>> Some CPUs are of an opposite data-endianness to other components in the
>> system. Sometimes elfs have the data sections layed out with this CPU
>> data-endianess accounting for when
On 18 January 2016 at 07:12, Peter Crosthwaite
wrote:
> Some CPUs are of an opposite data-endianness to other components in the
> system. Sometimes elfs have the data sections layed out with this CPU
> data-endianess accounting for when loaded via the CPU, byte swaps
> (relative to other system co
Some CPUs are of an opposite data-endianness to other components in the
system. Sometimes elfs have the data sections layed out with this CPU
data-endianess accounting for when loaded via the CPU, byte swaps
(relative to other system components) will occur.
The leading example, is ARM's BE32 mode,
