diff options
| author | Michael S. Tsirkin <mst@redhat.com> | 2019-11-24 07:40:23 -0500 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2019-11-24 07:55:19 -0500 |
| commit | 3ea1af6afb4cccb9a12c59c27e9df74505e5289e (patch) | |
| tree | c17e97acacc87d7fafcad73e0ff9ac44eb87a8cd | |
| parent | 72a801b9a53a4aeca759458c50be67cc32914a71 (diff) | |
| download | virtio-spec-3ea1af6afb4cccb9a12c59c27e9df74505e5289e.tar.gz | |
virtio-rng: fix device/driver confusion
The point of rng is to give data to driver so of course
all buffers are driver readable. What shouldn't be there
is device readable buffers - this matches our terminology
elsewhere too (read/write-ability is from POV of device).
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/55
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| -rw-r--r-- | content.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content.tex b/content.tex index ad50c9b..1bb2745 100644 --- a/content.tex +++ b/content.tex @@ -4759,7 +4759,7 @@ by random data by the device. \drivernormative{\subsubsection}{Device Operation}{Device Types / Entropy Device / Device Operation} -The driver MUST NOT place driver-readable buffers into the queue. +The driver MUST NOT place device-readable buffers into the queue. The driver MUST examine the length written by the device to determine how many random bytes were received. |