[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ceae37c323d43f8b1cf6c9aafe55d5e@ausx13mpc120.AMER.DELL.COM>
Date: Tue, 9 May 2017 01:10:54 +0000
From: <Mario.Limonciello@...l.com>
To: <pali.rohar@...il.com>
CC: <dvhart@...radead.org>, <rjw@...ysocki.net>, <luto@...capital.net>,
<len.brown@...el.com>, <corentin.chary@...il.com>,
<luto@...nel.org>, <andriy.shevchenko@...ux.intel.com>,
<linux-kernel@...r.kernel.org>,
<platform-driver-x86@...r.kernel.org>, <linux-pm@...r.kernel.org>
Subject: RE: RFC: WMI Enhancements
>
> I found dmsdos implementation of that DS compression at:
> http://cmp.felk.cvut.cz/~pisa/dmsdos
>
> 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?
>
> I pushed my decompression utility here:
> https://github.com/pali/bmfdec
Did you forget another commit for pulling in arguments and opening a file
or were you just putting the whole buffer into pin?
>
> So next step is to decode that decompressed binary MOF file.
>
> > 44 53 looks promising to be quantum compression.
Powered by blists - more mailing lists