linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter@hurleysoftware.com (Peter Hurley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ACPI: parse the SPCR table
Date: Fri, 4 Mar 2016 11:34:10 -0800	[thread overview]
Message-ID: <56D9E332.2000005@hurleysoftware.com> (raw)
In-Reply-To: <67709E22-E82E-40BA-A271-2107608F4EF3@redhat.com>

Hi Jon,

[ cc'd everyone back in on the assumption private mail was accidental ]


On 03/04/2016 12:21 AM, Jon Masters wrote:
> Top posting - in transit currently
> 
> Peter,
> 
> I would like to understand what concrete action you feel is needed in
> order to be comfortable with adding SPCR support to the Linux
> kernel?
>
> To clarify for others - this thread pertains to perceived issues with
> the license of a document describing the format of the SPCR, a
> document whose license was explicitly changed in response to previous
> concerns raised by yourself, not the code that actually implements
> SPCR support.

Not exactly, because there is no such thing as patenting a document.

The specification purports that patents apply to implementations of
SPCR, and grants rights to those patents under two optional licenses.

What I want is what is expected of any submitter to the Linux Kernel:
that the submitter has the legal right to do so as spelled out
in the Developer's Certificate of Origin (the text of which is in
Documentation/SubmittingPatches).

To have the legal right to submit material to which patents apply
requires a license.

So either
A) the submission does not infringe, and no patent license is required, or
B) the submission requires a patent license because otherwise it would
infringe.

If A, what I would like to see is the due diligence as to why the
submission does not infringe.

If B, FSF maintains an online list of GPL compatible licenses.
Neither of the two licenses offered are on the FSF online list.

The FSF also maintains a compliance lab and will render opinions on
the GPL compatibility of a license. They can be reached at
licensing at fsf.org

Alternatively, a statement from Linux Foundation that this
has been discussed and agreed upon privately is also fine.

Alternatively, any sign-off from ARM, Linaro or Red Hat legal that either
a) one of those licenses is GPL compatible, or
b) the submission does not infringe on the purported patents (and why)


> However you retain the opinion that the license under which the table
> is published "is not GPL compatible". So under what license would you
> like to see this table specification released?

Assuming none of the options above is acceptable, any license in the
"GPL-Compatible Free Software Licenses" listed here:

http://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses



> Jon.
> 
> -- Computer Architect | Sent from my 64-bit #ARM Powered phone
>> > On Mar 4, 2016, at 05:08, Peter Hurley <peter@hurleysoftware.com> wrote:
>> > 
>> > Hi Al,
>> > 
>> > Somehow your email was filtered. Apologies for that.
>> > 
>>> >> On 02/10/2016 03:39 PM, Al Stone wrote:
>>>> >>> On 01/27/2016 05:17 AM, Aleksey Makarov wrote:
>>>> >>> 
>>>> >>> 
>>>>> >>>> On 01/25/2016 07:11 PM, Peter Hurley wrote:
>>>>>> >>>>> On 01/25/2016 03:45 AM, Aleksey Makarov wrote:
>>>>>> >>>>> This patchset is based on the patchset by Leif Lindholm [1]
>>>>>> >>>>> 
>>>>>> >>>>> 'ARM Server Base Boot Requirements' [2] mention SPCR 
>>>>>> >>>>> (Serial Port Console Redirection Table) [3] as a mandatory
>>>>>> >>>>> ACPI table that specifies the configuration of serial console.
>>>>>> >>>>> 
>>>>>> >>>>> Licensing concerns have prevented implementing it in the past, but as of
>>>>>> >>>>> 10 August 2015, these tables have both been released also under 
>>>>>> >>>>> OWF 1.0 [4].
>>>>> >>>> 
>>>>> >>>> This license has a patent retaliation provision, which makes it
>>>>> >>>> incompatible with GPLv2.
>>>>> >>>> 
>>>>> >>>> *If the license applies to this code*, then this patch set does not
>>>>> >>>> meet the criteria for submission.
>>>> >>> 
>>>> >>> The license applies not to this code but to the document describing the tables.
>>> >> 
>>> >> Just for the record, the SPCR table struct definition has been part
>>> >> of the Linux kernel since at least commit b24aad44 on 2009-07-24
>>> >> (line 1112 of include/acpi/actbl2.h) -- or so git blame tells me.
>> > 
>> > Just to be clear here:
>> > 
>> > The Microsoft specification, which defines the SPCR table struct and which
>> > this patch series relies on, notes that patents apply. Specifically, it
>> > says:
>> > 
>> > Patent Notice:
>> > Microsoft is making certain patent rights available for implementations of this specification under two options:
>> > 1)  Microsoft?s Community Promise, available at http://www.microsoft.com/openspecifications/en/us/programs/community-promise/default.aspx; or
>> > 2)  The Open Web Foundation Final Specification Agreement Version 1.0 ("OWF 1.0") as of October 1, 2012, available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0. 
>> > Version 1.03 ? August 10, 2015
>> > 
>> > I don't believe either of those patent licenses are GPL compatible.
>> > 
>> > Unless you're saying Red Hat is signing off on this?
>> > 
>> > Regards,
>> > Peter Hurley

  parent reply	other threads:[~2016-03-04 19:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 11:45 [PATCH 0/3] ACPI: parse the SPCR table Aleksey Makarov
2016-01-25 11:45 ` [PATCH 1/3] printk: make preferred_console local static bool Aleksey Makarov
2016-01-25 12:45   ` Joe Perches
2016-01-25 12:51     ` Aleksey Makarov
2016-01-25 13:23       ` Joe Perches
2016-01-25 13:28         ` Aleksey Makarov
2016-01-25 16:14           ` Peter Hurley
2016-01-25 14:24   ` Andy Shevchenko
2016-01-25 14:55     ` Aleksey Makarov
2016-01-25 11:45 ` [PATCH 2/3] ACPI: parse SPCR and enable matching console Aleksey Makarov
2016-01-25 14:14   ` Andy Shevchenko
2016-01-25 15:07     ` Aleksey Makarov
2016-01-25 16:32   ` Peter Hurley
2016-01-27 13:57     ` Aleksey Makarov
2016-01-28  0:45       ` Peter Hurley
2016-01-28 13:23         ` Aleksey Makarov
2016-01-28 19:40           ` Peter Hurley
2016-02-01  9:01   ` Graeme Gregory
2016-02-01  9:13     ` Graeme Gregory
2016-01-25 11:45 ` [PATCH 3/3] serial: pl011: add acpi_match for amba-pl011.c Aleksey Makarov
2016-01-25 14:21   ` Andy Shevchenko
2016-01-25 14:22     ` Andy Shevchenko
2016-01-25 15:08       ` Aleksey Makarov
2016-01-25 16:11 ` [PATCH 0/3] ACPI: parse the SPCR table Peter Hurley
2016-01-27 12:17   ` Aleksey Makarov
2016-01-27 13:45     ` One Thousand Gnomes
2016-02-01  5:46       ` Jon Masters
2016-02-10 23:39     ` Al Stone
2016-03-03 20:08       ` Peter Hurley
     [not found]         ` <67709E22-E82E-40BA-A271-2107608F4EF3@redhat.com>
2016-03-04 19:34           ` Peter Hurley [this message]
2016-03-04 20:03             ` Peter Hurley

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=56D9E332.2000005@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).