[PATCH 2/6] virtqueue endian-ness

[Rusty Russell <rusty@au1.ibm.com>]

From: "Michael S. Tsirkin" <mst@redhat.com>

make all ring structures LE
resolves VIRTIO-9

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
---
 virtio-v1.0-wd01-part1-specification.txt | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt
index 8340c42..7a49d6d 100644
--- a/virtio-v1.0-wd01-part1-specification.txt
+++ b/virtio-v1.0-wd01-part1-specification.txt
@@ -308,14 +308,12 @@ The legacy virtqueue layout structure therefore looks like this:
 		struct vring_used used;
 	};
 
-2.1.4.1. A Note on Virtqueue Endianness
+2.1.4.1. Legacy Interfaces: A Note on Virtqueue Endianness
 --------------------------------------
 
 Note that the endian of fields and in the virtqueue is the native
-endian of the guest, not little-endian as PCI normally is. This makes
-for simpler guest code, and it is assumed that the host already has to
-be deeply aware of the guest endian so such an “endian-aware” device
-is not a significant issue.
+endian of the guest, not little-endian as PCI normally is.
+It is assumed that the host is already aware of the guest endian.
 
 2.1.4.2. Message Framing
 -----------------------
-- 
1.8.1.2