Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] intel-microcode: new package
Date: Thu, 20 Sep 2012 23:12:55 +0200	[thread overview]
Message-ID: <20120920211255.GA32421@mail.sceen.net> (raw)
In-Reply-To: <20120920223646.65a34101@skate>

On Thu, Sep 20, 2012 at 10:36:46PM +0200, Thomas Petazzoni wrote:
> Is there a license file somewhere that states that even though it is
> proprietary, one has the right to redistribute the binaries?

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 :

"OEM LICENSE: You may reproduce and distribute the Software only as an 
integral part of or incorporated in Your product or as a standalone 
Software maintenance update for existing end users of Your products, 
excluding any other standalone products, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel 
component products. Use of the Software in conjunction with non-Intel 
component products is not licensed hereunder.
2. You may not copy, modify, rent, sell, distribute or transfer any part 
of the Software except as provided in this Agreement, and you agree to 
prevent unauthorized copying of the Software.
3. You may not reverse engineer, decompile, or disassemble the Software. 
4. You may only distribute the Software to your customers pursuant to a 
written license agreement. Such license agreement may be a "break-the-
seal" license agreement. At a minimum such license shall safeguard 
Intel's ownership rights to the Software.
5. The Software may include portions offered on terms in addition to those
set out here, as set out in a license accompanying those portions."

-- 
Richard Braun

[1] http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21385&keyword=microcode&lang=eng

  reply	other threads:[~2012-09-20 21:12 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 [this message]
2012-09-21  8:35     ` Thomas Petazzoni
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=20120920211255.GA32421@mail.sceen.net \
    --to=rbraun@sceen.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox