diff options
| author | Michael S. Tsirkin <mst@redhat.com> | 2019-11-24 07:40:23 -0500 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2020-01-28 07:56:15 -0500 |
| commit | d7e91b5469fb8b8b2a92edeca90f6ed0805e5e43 (patch) | |
| tree | 5d02399d067a42582e27ef9d982a686af7f8f505 | |
| parent | 6914d2df75ec0479df59ae9054ee4be1564c5172 (diff) | |
| download | virtio-spec-d7e91b5469fb8b8b2a92edeca90f6ed0805e5e43.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>
Reviewed-by: Pankaj Gupta <pagupta@redhat.com>
| -rw-r--r-- | content.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content.tex b/content.tex index fb10061..307e66f 100644 --- a/content.tex +++ b/content.tex @@ -4938,7 +4938,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. |