From: Ben Hutchings <ben@decadent.org.uk>
To: linux-kernel@vger.kernel.org, linux-firmware@kernel.org
Subject: [PATCH linux-firmware 5/7] Add licence information for e100 microcode
Date: Sun, 18 Oct 2015 15:00:40 +0100 [thread overview]
Message-ID: <1445176840.31451.66.camel@decadent.org.uk> (raw)
In-Reply-To: <1445176757.31451.61.camel@decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2599 bytes --]
The BSDs include the same code under a typical BSD-ish licence, e.g.
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/microcode/fxp/rcvbundl.h?rev=1.2
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
LICENCE.e100 | 28 ++++++++++++++++++++++++++++
WHENCE | 4 +---
2 files changed, 29 insertions(+), 3 deletions(-)
create mode 100644 LICENCE.e100
diff --git a/LICENCE.e100 b/LICENCE.e100
new file mode 100644
index 0000000..0553817
--- /dev/null
+++ b/LICENCE.e100
@@ -0,0 +1,28 @@
+Copyright (c) 1999-2001, Intel Corporation
+
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+ 1. Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ 3. Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
diff --git a/WHENCE b/WHENCE
index 077f42d..6e7ce0a 100644
--- a/WHENCE
+++ b/WHENCE
@@ -588,9 +588,7 @@ File: e100/d101m_ucode.bin
File: e100/d101s_ucode.bin
File: e100/d102e_ucode.bin
-Licence: Unknown
-
-Found in hex form in kernel source.
+Licence: Redistributable. See LICENCE.e100 for details
--------------------------------------------------------------------------
--
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai Stevenson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-10-18 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 13:59 [PATCH linux-firmware 0/7] Metadata fixes for linux-firmware Ben Hutchings
2015-10-18 14:00 ` [PATCH linux-firmware 1/7] WHENCE: Remove listing of a nonexistent file Ben Hutchings
2015-10-18 14:00 ` [PATCH linux-firmware 2/7] WHENCE: Expand file wildcard RTL8192E/* Ben Hutchings
2015-10-18 14:00 ` [PATCH linux-firmware 3/7] WHENCE: Fix several licen[cs]e filenames Ben Hutchings
2015-10-18 14:00 ` [PATCH linux-firmware 4/7] Add licence information for kaweth firmware Ben Hutchings
2015-10-18 14:00 ` Ben Hutchings [this message]
2015-10-18 14:00 ` [PATCH linux-firmware 6/7] Add licence information for qla1280 firmware Ben Hutchings
2015-10-18 14:00 ` [PATCH linux-firmware 7/7] WHENCE: Summarise several more custom licences as 'Redistributable' Ben Hutchings
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=1445176840.31451.66.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-firmware@kernel.org \
--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®