On Thu, Jan 14, 2016 at 12:24:29PM -0500, Cole Robinson wrote:
> On 01/14/2016 12:22 PM, Kevin O'Connor wrote:
> > According to SMBIOS v2.6 the first three fields are encoded in
> > little-endian format. Versions prior to v2.6 did not specify the
> > encoding, but we follow dmidecode and assume
On 01/14/2016 12:22 PM, Kevin O'Connor wrote:
> On Tue, Jan 12, 2016 at 02:22:41PM -0500, Cole Robinson wrote:
>> SMBIOS 2.6+ stores the UUID in a different format, with the first 3
>> fields in little endian format. This is what modern qemu delivers
>> and what dmidecode also handles, so let's
On Tue, Jan 12, 2016 at 02:22:41PM -0500, Cole Robinson wrote:
> SMBIOS 2.6+ stores the UUID in a different format, with the first 3
> fields in little endian format. This is what modern qemu delivers
> and what dmidecode also handles, so let's follow suit too. More
> info at this thread:
>
>
On 01/14/16 18:22, Kevin O'Connor wrote:
> On Tue, Jan 12, 2016 at 02:22:41PM -0500, Cole Robinson wrote:
>> SMBIOS 2.6+ stores the UUID in a different format, with the first 3
>> fields in little endian format. This is what modern qemu delivers
>> and what dmidecode also handles, so let's follow
Hi,
> > The above is okay to me, but I'd like to get Gerd's comments as well,
> > as I think he had some concerns the last time it came up.
>
> I don't recall Gerd's comments from last time, but I think the case is
> that some combination will be unavoidably broken.
Yes, that is the problem.
SMBIOS 2.6+ stores the UUID in a different format, with the first 3
fields in little endian format. This is what modern qemu delivers
and what dmidecode also handles, so let's follow suit too. More
info at this thread:
http://www.seabios.org/pipermail/seabios/2015-November/010031.html
The only
