From 7317dc565b19c5845c921b8152a5e3271ff9f81a Mon Sep 17 00:00:00 2001 From: mstsirkin Date: Wed, 21 Oct 2015 14:20:51 +0000 Subject: intro: add advice on transition from legacy interfaces Reading legacy chapters gives a hint about what changed, let's help readers discover this useful shortcut. This resolves VIRTIO-146. Signed-off-by: Michael S. Tsirkin Reviewed-by: Cornelia Huck Accepted by electronic ballot: https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2866 git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@548 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- introduction.tex | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/introduction.tex b/introduction.tex index ac7eefa..ba67137 100644 --- a/introduction.tex +++ b/introduction.tex @@ -126,6 +126,16 @@ Similarly, a driver MAY implement: Devices or drivers with no legacy compatibility are referred to as non-transitional devices and drivers, respectively. +\subsection{Transition from earlier specification drafts} + +For devices and drivers already implementing the legacy +interface, some changes will have to be made to support this +specification. + +In this case, it might be beneficial for the reader to focus on +sections tagged "Legacy Interface" in the section title. +These highlight the changes made since the earlier drafts. + \section{Structure Specifications} Many device and driver in-memory structure layouts are documented using -- cgit v1.2.3