I'm parsing MAVLINK 1.0 for my ground station.
From MAVLINK documentation, I understand that the protocol uses little-endian encoding on the wire. This assumption produces meaningful data for a lot of packets. However some packets make no sense in LE but produce meaningful data in BE, for example RC_CHANNELS_RAW message seems to encode channel values in BE uint16_t. I wonder if some fields (messages?) indeed use different endianness, and if they do, I wonder if there exists a canonical list of which messages are BE and which LE.