> On May 14, 2016, at 8:53 AM, Michael Zimmermann <sigmaepsilo...@gmail.com> > wrote: > > Hi, > > I'm pretty sure it's correct because the python doc says that 'uuid.bytes' > is in big endian format. > Also I can easily double check this because my tool also prints the > ready-to-use string produced by str(guid) which matches my manual output > exactly. > > Source: https://docs.python.org/2/library/uuid.html#uuid.UUID.bytes >
Sorry I was using UUID.bytes_le, but I see you are using UUID.bytes that explains the difference. Thanks, Andrew Fish > Thanks > Michael > > I think you have the wrong endian. GUID is defined as a UINT32, UINT16, >> UINT16, Byte array. >> >> (guid[3], guid[2], guid[1], guid[0], guid[5], guid[4], guid[7], guid[6], >> guid[8], guid[9], guid[10], guid[11], guid[12], guid[13], guid[14], >> guid[15]) >> >> Contributed-under: TianoCore Contribution Agreement 1.0 >> > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
