On Sun, Feb 12, 2012 at 07:20:07PM +0100, Andreas Färber wrote:
> Am 12.02.2012 16:06, schrieb Michael S. Tsirkin:
> > So I think the following is right?
> >
> >
> > commit 02aa79aac9bec1c8c17d1b7b5405b59b649dfdb9
> > Author: Michael S. Tsirkin
> > Date: Wed Feb 8 17:16:35 2012 +0200
> >
> >
Am 12.02.2012 16:06, schrieb Michael S. Tsirkin:
> So I think the following is right?
>
>
> commit 02aa79aac9bec1c8c17d1b7b5405b59b649dfdb9
> Author: Michael S. Tsirkin
> Date: Wed Feb 8 17:16:35 2012 +0200
>
> docs: memory.txt document the endian field
>
> This is an attempt to
On 02/12/2012 05:06 PM, Michael S. Tsirkin wrote:
> > It's really really simple:
> >
> > If the device spec says "big endian, specify DEVICE_BIG_ENDIAN, and
> > treat the data naturally in the callback.
> > If the device spec says "little endian, specify DEVICE_LITTLE_ENDIAN,
> > and treat the dat
On Sun, Feb 12, 2012 at 03:55:20PM +0200, Avi Kivity wrote:
> On 02/12/2012 03:47 PM, Michael S. Tsirkin wrote:
> > On Sun, Feb 12, 2012 at 03:02:11PM +0200, Avi Kivity wrote:
> > > On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote:
> > > > This is an attempt to document the endian
> > > > field in
On 02/12/2012 03:47 PM, Michael S. Tsirkin wrote:
> On Sun, Feb 12, 2012 at 03:02:11PM +0200, Avi Kivity wrote:
> > On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote:
> > > This is an attempt to document the endian
> > > field in memory API. As this is a confusing topic,
> > > it's best to make the
On Sun, Feb 12, 2012 at 03:02:11PM +0200, Avi Kivity wrote:
> On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote:
> > This is an attempt to document the endian
> > field in memory API. As this is a confusing topic,
> > it's best to make the text as explicit as possible.
> >
> > Signed-off-by: Michael
On 02/12/2012 02:52 PM, Michael S. Tsirkin wrote:
> This is an attempt to document the endian
> field in memory API. As this is a confusing topic,
> it's best to make the text as explicit as possible.
>
> Signed-off-by: Michael S. Tsirkin
> ---
> docs/memory.txt | 28 +++
This is an attempt to document the endian
field in memory API. As this is a confusing topic,
it's best to make the text as explicit as possible.
Signed-off-by: Michael S. Tsirkin
---
docs/memory.txt | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --gi