From 305bbaed001e6fd99d3de1dbe26a230a435abb7d Mon Sep 17 00:00:00 2001 From: rusty Date: Fri, 4 Oct 2013 04:41:45 +0000 Subject: 2.3.1.2.5: emphasize that PCI device-specific config byte-accessible legacy only This clarification taken from a larger patch by MST: http://markmail.org/search/?q=subject%3A%22[PATCH]%20configuration%20space%20endian-ness%22+list%3A%22org.oasis-open.lists.virtio%22#query:subject%3A%22[PATCH]%20configuration%20space%20endian-ness%22%20list%3A%22org.oasis-open.lists.virtio%22+page:1+mid:6k3im4t3csdukbzm+state:results Signed-off-by: Rusty Russell git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@53 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- virtio-v1.0-wd01-part1-specification.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt index b5a5835..75557aa 100644 --- a/virtio-v1.0-wd01-part1-specification.txt +++ b/virtio-v1.0-wd01-part1-specification.txt @@ -882,7 +882,8 @@ region of the PCI device, as documented below. There may be different widths of accesses to the I/O region; the “natural” access method for each field in the virtio header must be -used (i.e. 32-bit accesses for 32-bit fields, etc), but the +used (i.e. 32-bit accesses for 32-bit fields, etc), but +when accessed through the legacy interface the device-specific region can be accessed using any width accesses, and should obtain the same results. -- cgit v1.2.3