So if everyone agrees that the header should be
{
uint32_t timestamp_int;
uint32_t timestamp_frc;
uint16_t size;
uint16_t type;
}with data padded to 4+N*16 bytes, can't we just say that the code part is done? Whether the different events types are implemented as aligned platform-dependent structs or raw packed bytes or something else doesn't matter at all to the event transport extension and it doesn't make any sense to argue about it until we actually have a fixed way of sending events. --ll
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
