docs: vendor-ibm-astlpc: Increase prominence of endianness
Describe this before we get distracted by other details of the LPC FW
window.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: Ibe2c17cdc60631a4402fd182be64d636c6835605
diff --git a/docs/bindings/vendor-ibm-astlpc.md b/docs/bindings/vendor-ibm-astlpc.md
index 0163684..6b7a2ee 100644
--- a/docs/bindings/vendor-ibm-astlpc.md
+++ b/docs/bindings/vendor-ibm-astlpc.md
@@ -196,14 +196,14 @@
#define LPC_MAGIC 0x4d435450
```
+All control data is in big-endian format. MCTP packet data is transferred
+exactly as is presented, and no data escaping is performed.
+
The transmit and receive areas contain a length field, followed by the actual
MCTP packet to be transferred. At version 1, only a single MCTP packet is
present in the Rx and Tx areas. This may change for future versions of the
protocol.
-All control data is in big-endian format. MCTP packet data is transferred
-exactly as is presented, and no data escaping is performed.
-
#### Negotiation of the Maximum Transmission Unit
Version 1 of the protocol offers no mechanism for negotiation of the maximum