RE: RFC: WMI Enhancements

[Mario.Limonciello]

> -----Original Message-----
> From: Andy Shevchenko [mailto:andy.shevchenko@xxxxxxxxx]
> Sent: Tuesday, May 9, 2017 2:04 PM
> To: Limonciello, Mario <Mario_Limonciello@xxxxxxxx>
> Cc: Pali RohÃr <pali.rohar@xxxxxxxxx>; dvhart@xxxxxxxxxxxxx; Rafael J. Wysocki
> <rjw@xxxxxxxxxxxxx>; Andy Lutomirski <luto@xxxxxxxxxxxxxx>; Brown, Len
> <len.brown@xxxxxxxxx>; Corentin Chary <corentin.chary@xxxxxxxxx>; Andy
> Lutomirski <luto@xxxxxxxxxx>; Andy Shevchenko
> <andriy.shevchenko@xxxxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx; Platform
> Driver <platform-driver-x86@xxxxxxxxxxxxxxx>; linux-pm@xxxxxxxxxxxxxxx
> Subject: Re: RFC: WMI Enhancements
> 
> On Tue, May 9, 2017 at 9:10 PM,  <Mario.Limonciello@xxxxxxxx> wrote:
> 
> >> > > Then took relevant decompression code and it really decompressed that
> >> > > binary MOF WMI buffer. But still decompressed format is binary, but I
> >> > > now see all WMI GUID encoded in UTF-16. Decompressed BMF file has again
> >> > > "FOMB" magic header.
> >> >
> >> > Well that's great.  Is it possible that this compression is used for every time
> >> > a class was declared?
> >>
> >> Looks like not. That decompressed output seems to be not compressed
> >> anymore. Just use same magic header.
> > Actually it looks like a new magic header to me after decompressed.
> >
> > 46 4f 4d 42 54 15 00 00  01 00 00 00 01 00 00 00
> > That's now FOMBT
> 
> I think you just mistakenly take 0x54 as letter when it looks more like
> 
> 0x00001554
> 0x00000001
> 0x00000001
> 
> from the above dump.
Ah, that's true, but second word is different than original was main point.
We didn't know what that represented (maybe it's part of magic header).

46 4f 4d 42 01 00 00 00  ed 04 00 00 d8 15 00 00
0x00000001

> --
> With Best Regards,
> Andy Shevchenko