Re: [PATCH v24 1/1] mctp pcc: Implement MCTP over PCC Transport

[Jeremy Kerr]

Hi Adam,

> > And just confirming: the pcc header format is now all host-endian - or
> > is that a firmware-specified endianness? (what happens if the OS may
> > boot in either BE or LE? is that at all possible for any PCC-capable
> > hardware, or are we otherwise guaranteed that we're the same endianness
> > as the consumer?)
> 
> The specification does not specify endianess.  It is not addressed in
> the ACPI  PCC spec nor the MCTP over PCC spec. There does not seem  to 
> be any endianess modifiers in any of the ACPI code base.

There are a few cases of endian conversion, they appear to be cases
where a pre-defined data format is used, and only where that data is BE.

That's a pretty strong indication that we don't need to worry about host
endian != firmware endian (I'm assuming that firmware is the entity
that parses the PCC headers you're constructing). All sounds good then.

Cheers,


Jeremy