From: "Pali Rohár" <pali@kernel.org>
To: Armin Wolf <W_Armin@gmx.de>
Cc: "linux@weissschuh.net" <linux@weissschuh.net>,
Kurt Borja <kuurtb@gmail.com>,
akpm@linux-foundation.org, mcgrof@kernel.org,
russ.weight@linux.dev, dakr@kernel.org,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: In-kernel parser for the BMOF format used by WMI-ACPI
Date: Tue, 11 Mar 2025 21:13:57 +0100 [thread overview]
Message-ID: <20250311201357.tyldll7j2eogmryw@pali> (raw)
In-Reply-To: <a18f2f93-c8ee-47af-9446-97e3714fc275@gmx.de>
On Tuesday 11 March 2025 21:06:16 Armin Wolf wrote:
> - Is there any way to check whether the Doublespace compression algorithm is still encumbered by patents?
Linux kernel 2.2 or 2.4 had full read/write support for doublespace
compression algorithm in mainline kernel and it was connected with fat
driver. IIRC it was dropped for kernel 2.6 because nobody ported that
vfat code to new fs API and hence doublespace in-kernel compression
algorithm was not needed/used anymore. But I do not remember details.
So IMHO it should not be a problem to reintroduce same code into kernel
again if there is a new need for it.
And in my project I reused the doublespace compression code from old
Linux kernel.
next prev parent reply other threads:[~2025-03-11 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 20:06 In-kernel parser for the BMOF format used by WMI-ACPI Armin Wolf
2025-03-11 20:13 ` Pali Rohár [this message]
2025-03-11 20:59 ` Armin Wolf
2025-03-11 21:02 ` Pali Rohár
2025-03-12 4:56 ` Kurt Borja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250311201357.tyldll7j2eogmryw@pali \
--to=pali@kernel.org \
--cc=W_Armin@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mcgrof@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=russ.weight@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox