From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] intel-microcode: new package
Date: Fri, 21 Sep 2012 10:35:13 +0200 [thread overview]
Message-ID: <20120921103513.01871dd2@skate> (raw)
In-Reply-To: <20120920211255.GA32421@mail.sceen.net>
Dear Richard Braun,
On Thu, 20 Sep 2012 23:12:55 +0200, Richard Braun wrote:
> On the Intel download site, after searching for the last version of the
> microcode data file [1], the download link leads to a license agreement
> page which describes three license terms, depending on the nature of the
> distributor (network administrator, end user or OEM). I think the OEM
> license applies to most buildroot users. Here is the content :
Ok. Thanks. And there is no zip file or tarball that contains both
the license and the firmware? I'm simply worried about having just
FOO_LICENSE = PROPRIETARY without a proper license file that indicates
what license it is. Or maybe we need to put a special license file in
package/intel-microcode/ and find a way to tell the license
infrastructure that the license file is here rather than in the package
itself?
Cc'ing Luca on this.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-21 8:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 15:12 [Buildroot] [PATCH] intel-microcode: new package Richard Braun
2012-09-20 20:36 ` Thomas Petazzoni
2012-09-20 21:12 ` Richard Braun
2012-09-21 8:35 ` Thomas Petazzoni [this message]
2012-09-22 9:42 ` Richard Braun
2012-09-28 12:17 ` Richard Braun
2012-09-28 12:20 ` [Buildroot] [PATCH] pkg-infra: produce legal info for proprietary packages Richard Braun
2012-09-28 12:23 ` Thomas Petazzoni
2012-09-28 16:40 ` Thomas De Schampheleire
2012-09-28 17:05 ` Thomas Petazzoni
2012-09-28 18:52 ` Thomas De Schampheleire
2012-09-30 14:22 ` Arnout Vandecappelle
2012-10-02 13:41 ` Luca Ceresoli
2012-10-02 14:35 ` Arnout Vandecappelle
2012-10-02 17:50 ` Thomas De Schampheleire
2012-10-16 15:42 ` Richard Braun
2012-10-20 20:51 ` Luca Ceresoli
2012-10-20 21:55 ` Richard Braun
2012-09-28 12:20 ` [Buildroot] [PATCH] intel-microcode: new package Richard Braun
2012-09-28 12:24 ` Thomas Petazzoni
2012-09-29 9:31 ` Thomas De Schampheleire
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=20120921103513.01871dd2@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.