| Age | Commit message (Collapse) | Author |
|---|
|
For the network device, we had two device normative sections both called
"setting up receive buffers", neither of which was referenced in the
conformance section.
Let's rename the second one to "processing of packets" which seems to
better match the actual contents and reference both of them from the
conformance statement for network devices.
Resolves VIRTIO-97.
Agreed on the 2014/05/06 TC meeting.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@362 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Both device and driver conformance referred to ccw twice; let's add the
correct mmio references.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
(cherry picked from commit feeca2541850c2e1e03ed5ec3b98a5e75ccb4053)
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@361 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
This reverts commit feeca2541850c2e1e03ed5ec3b98a5e75ccb4053.
Revert temporarily so we are back to text matching WD02.
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@334 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Both device and driver conformance referred to ccw twice; let's add the
correct mmio references.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@333 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
These are never introduced, so use simpler names: virtq* for structures
and VIRTIO_ for features.
I added two notes about the old names, for helping people coming from
the old spec.
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@327 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Avoid these words where they are redundant. This also lead me to
notice that we were not consistent in the use of the term
"device-specific configuration" in the PCI section, so cleaned that up
too.
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@323 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@321 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Clean up the remaining lowercase "musts". We actually introduce a
new normative section in the balloon; for the rest we clarify them
one way or another.
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@318 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Change accepted on VIRTIO TC Meeting, 3 December 2013
VIRTIO-64
Cc: Patrick Durusau <patrick@durusau.net
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@303 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Change accepted on VIRTIO TC Meeting, 3 December 2013
document that there are two conformance levels
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@300 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
Now we have grouped all the normative statements, the conformance
clauses for drivers and devices can simply reference them.
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@278 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
We should make it clearer later, for now this should
be enough for the CSD 1.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@131 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
|
I imported latex templates from the CMIS specifications
and changed s/CMIS/VIRTIO/ everywhere.
The result is very close to one produced by exporting from the
ODF we were supplied, with the exception of the TOC formatting,
where section numbers are in blue instead of black, and major
sections don't have dots leading to page numbers.
I'm guessing this isn't very important, someone with more latex
knowledge can try to figure this out.
Generating html doesn't actually work for me.
It doesn't work for me for CMIS either, so
it's probably just an issue with my local latex setup.
I'm not sure we need html output at all.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@103 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
|
