From 3e49aec6126574d999081f39c360d452a7104e02 Mon Sep 17 00:00:00 2001 From: "Michael S. Tsirkin" Date: Mon, 11 Mar 2019 09:15:49 -0400 Subject: conformance: fix confusion about legacy interface The text describing the legacy interface also obliquely refers to a non-transitional implementation. This seems to cause confusion and there's no good reason to do it here: this section is about legacy interface and transitional devices, it add not value at all. Just drop it. Note: the spec does not make it clear whether description of the legacy interface is normative or not, and in particular, this section is not linked to from any conformance targets. Resolving that is left for later. Fixes: https://issues.oasis-open.org/browse/VIRTIO-167 Signed-off-by: Michael S. Tsirkin Reviewed-by: Cornelia Huck Acked-by: Halil Pasic --- conformance.tex | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/conformance.tex b/conformance.tex index 6df113b..ce51463 100644 --- a/conformance.tex +++ b/conformance.tex @@ -341,13 +341,9 @@ A conformant implementation MUST be either transitional or non-transitional, see \ref{intro:Legacy Interface: Terminology}. -A non-transitional implementation conforms to this specification -if it satisfies all of the MUST or REQUIRED level requirements -defined above. - An implementation MAY choose to implement OPTIONAL support for the legacy interface, including support for legacy drivers -or devices, by additionally conforming to all of the MUST or +or devices, by conforming to all of the MUST or REQUIRED level requirements for the legacy interface for the transitional devices and drivers. -- cgit