From: "Grover, Andrew" <andrew.grover@intel.com>
To: acpi-devel@sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Proposed ACPI Licensing change
Date: Fri, 6 Dec 2002 16:10:00 -0800 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A57F@orsmsx119.jf.intel.com> (raw)
Hi all,
The ACPI AML interpreter (i.e. code in directories under drivers/acpi, but
not source in drivers/acpi directly) has been released by us (Intel) under
the GPL. It has also been released separately under a looser license, so
that other OS vendors may make use of it.
One consequence of this is that we have not been able to benefit directly
from patches from other Linux contributors. The reason is, patches submitted
to code only under the GPL must also be GPL, and therefore we cannot take
them directly and still make our code available under a license other than
the GPL. (We have to determine the problem the patch fixes and then do the
fix ourselves.)
This has slowed development and lessened community participation in the
development process.
In order to solve this, we are considering releasing the Linux version of
the interpreter under a dual license. This would allow direct incorporation
of changes. Any patches submitted against the ACPI core code would
implicitly be allowed to be used by us in a non-GPL context. This is already
done elsewhere in the Linux kernel source by the PCMCIA code, for example.
Comments?
Regards -- Andy
-----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover@intel.com
next reply other threads:[~2002-12-07 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 0:10 Grover, Andrew [this message]
2002-12-07 0:24 ` Adrian Bunk
2002-12-07 0:36 ` David Schwartz
2002-12-07 20:07 ` Linus Torvalds
2002-12-07 23:44 ` Hans Reiser
2002-12-09 19:39 ` H. Peter Anvin
2002-12-07 0:51 ` Christoph Hellwig
2002-12-07 2:16 ` Alan Cox
2002-12-07 9:58 ` Jeff Garzik
2002-12-07 17:46 ` Greg KH
2002-12-09 18:59 ` Pavel Machek
2002-12-07 1:06 Adrian Bunk
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=EDC461A30AC4D511ADE10002A5072CAD04C7A57F@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=acpi-devel@sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®