Skip to content

Commit f537d94

Browse files
virtio-msg: switch endianness to normative
Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
1 parent 0b03f76 commit f537d94

1 file changed

Lines changed: 14 additions & 2 deletions

File tree

transport-msg.tex

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -345,8 +345,20 @@ \subsubsection{Error Signaling}
345345
\subsubsection{Endianness}
346346
\label{sec:Virtio Transport Options / Virtio Over Messages / Basic Concepts / Endianness}
347347

348-
All values and fields defined in the virtio-msg messages MUST
349-
be encoded in little-endian.
348+
Unless otherwise stated, all numeric fields defined for virtio-msg messages use
349+
little-endian encoding.
350+
351+
\drivernormative{\paragraph}{Endianness (Driver)}{Virtio Transport Options / Virtio Over Messages / Basic Concepts / Endianness / Driver}
352+
\begin{itemize}
353+
\item A driver MUST encode and decode the common header and payload fields defined by this transport
354+
using little-endian byte order.
355+
\end{itemize}
356+
357+
\devicenormative{\paragraph}{Endianness (Device)}{Virtio Transport Options / Virtio Over Messages / Basic Concepts / Endianness / Device}
358+
\begin{itemize}
359+
\item A device MUST emit and consume the common header and payload fields defined by this transport
360+
using little-endian byte order.
361+
\end{itemize}
350362

351363
\subsubsection{Common Message Format}
352364
\label{sec:Virtio Transport Options / Virtio Over Messages / Basic Concepts / Common Message Format}

0 commit comments

Comments
 (0)