cachepc-qemu

Fork of AMDESE/qemu with changes for cachepc side-channel attack
git clone https://git.sinitax.com/sinitax/cachepc-qemu
Log | Files | Refs | Submodules | LICENSE | sfeed.txt

edk2-licenses.txt (42903B)


      1==> edk2/License.txt <==
      2Copyright (c) 2019, TianoCore and contributors.  All rights reserved.
      3
      4SPDX-License-Identifier: BSD-2-Clause-Patent
      5
      6Redistribution and use in source and binary forms, with or without
      7modification, are permitted provided that the following conditions are met:
      8
      91. Redistributions of source code must retain the above copyright notice,
     10   this list of conditions and the following disclaimer.
     11
     122. Redistributions in binary form must reproduce the above copyright notice,
     13   this list of conditions and the following disclaimer in the documentation
     14   and/or other materials provided with the distribution.
     15
     16Subject to the terms and conditions of this license, each copyright holder
     17and contributor hereby grants to those receiving rights under this license
     18a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
     19(except for failure to satisfy the conditions of this license) patent
     20license to make, have made, use, offer to sell, sell, import, and otherwise
     21transfer this software, where such license applies only to those patent
     22claims, already acquired or hereafter acquired, licensable by such copyright
     23holder or contributor that are necessarily infringed by:
     24
     25(a) their Contribution(s) (the licensed copyrights of copyright holders and
     26    non-copyrightable additions of contributors, in source or binary form)
     27    alone; or
     28
     29(b) combination of their Contribution(s) with the work of authorship to
     30    which such Contribution(s) was added by such copyright holder or
     31    contributor, if, at the time the Contribution is added, such addition
     32    causes such combination to be necessarily infringed. The patent license
     33    shall not apply to any other combinations which include the
     34    Contribution.
     35
     36Except as expressly stated above, no rights or licenses from any copyright
     37holder or contributor is granted under this license, whether expressly, by
     38implication, estoppel or otherwise.
     39
     40DISCLAIMER
     41
     42THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
     43AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
     44IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
     45ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
     46LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
     47CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
     48SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
     49INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
     50CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
     51ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
     52POSSIBILITY OF SUCH DAMAGE.
     53
     54==> edk2/License-History.txt <==
     55                              License-History.txt
     56                              ===================
     57
     58This file contains the history of license change and contributor's agreement
     59changes.
     60
     61Unless otherwise noted in a specific file, the EDK2 project is now licensed
     62under the terms listed in the License.txt file.  Terms under which Contributions
     63made prior to the move to the License.txt formulation are shown below.  Those
     64terms require notice of the terms themselves be preserved and presented with the
     65contributions.  This file serves that preservation purpose as a matter of
     66documenting the history of the project.
     67
     68Key Dates
     69----------
     70* August 3, 2017
     71
     72  Update the TianoCore Contribution Agreement from Version 1.0
     73  to Version 1.1 to cover open source documentation associated
     74  with the TianoCore project.
     75
     76  Version 1.0 covers source code files.  Version 1.1 is a
     77  backwards compatible extension that adds support for document
     78  files in both source form and compiled form.
     79
     80  References:
     81      https://opensource.org/licenses/BSD-2-Clause
     82      Complete text of TianoCore Contribution Agreement 1.0 included below
     83      Complete text of TianoCore Contribution Agreement 1.1 included below
     84
     85  Proposals (RFCs):
     86      https://lists.01.org/pipermail/edk2-devel/2017-March/008654.html
     87
     88  TianoCore Bugzilla:
     89      https://bugzilla.tianocore.org/show_bug.cgi?id=629
     90
     91* April 9, 2019
     92
     93  Replace BSD 2-Clause License with BSD + Patent License removing the need for
     94  the TianoCore Contribution Agreement.
     95
     96  References:
     97      https://opensource.org/licenses/BSD-2-Clause
     98      Complete text of TianoCore Contribution Agreement 1.0 included below
     99      Complete text of TianoCore Contribution Agreement 1.1 included below
    100      https://opensource.org/licenses/BSDplusPatent
    101
    102  Proposals (RFCs):
    103      https://lists.01.org/pipermail/edk2-devel/2019-February/036260.html
    104      https://lists.01.org/pipermail/edk2-devel/2019-March/037500.html
    105
    106  TianoCore Bugzilla:
    107      https://bugzilla.tianocore.org/show_bug.cgi?id=1373
    108
    109--------------------------------------------------------------------------------
    110License.txt: BSD 2-Clause License
    111--------------------------------------------------------------------------------
    112    Redistribution and use in source and binary forms, with or without
    113    modification, are permitted provided that the following conditions
    114    are met:
    115
    116    * Redistributions of source code must retain the above copyright
    117      notice, this list of conditions and the following disclaimer.
    118    * Redistributions in binary form must reproduce the above copyright
    119      notice, this list of conditions and the following disclaimer in
    120      the documentation and/or other materials provided with the
    121      distribution.
    122
    123    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    124    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    125    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
    126    FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
    127    COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
    128    INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
    129    BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    130    LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
    131    CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
    132    LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
    133    ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
    134    POSSIBILITY OF SUCH DAMAGE.
    135--------------------------------------------------------------------------------
    136
    137--------------------------------------------------------------------------------
    138Contributions.txt: TianoCore Contribution Agreement 1.1
    139--------------------------------------------------------------------------------
    140    ======================
    141    = Code Contributions =
    142    ======================
    143
    144    To make a contribution to a TianoCore project, follow these steps.
    145    1. Create a change description in the format specified below to
    146       use in the source control commit log.
    147    2. Your commit message must include your "Signed-off-by" signature,
    148       and "Contributed-under" message.
    149    3. Your "Contributed-under" message explicitly states that the
    150       contribution is made under the terms of the specified
    151       contribution agreement.  Your "Contributed-under" message
    152       must include the name of contribution agreement and version.
    153       For example: Contributed-under: TianoCore Contribution Agreement 1.1
    154       The "TianoCore Contribution Agreement" is included below in
    155       this document.
    156    4. Submit your code to the TianoCore project using the process
    157       that the project documents on its web page.  If the process is
    158       not documented, then submit the code on development email list
    159       for the project.
    160    5. It is preferred that contributions are submitted using the same
    161       copyright license as the base project. When that is not possible,
    162       then contributions using the following licenses can be accepted:
    163       * BSD (2-clause): http://opensource.org/licenses/BSD-2-Clause
    164       * BSD (3-clause): http://opensource.org/licenses/BSD-3-Clause
    165       * MIT: http://opensource.org/licenses/MIT
    166       * Python-2.0: http://opensource.org/licenses/Python-2.0
    167       * Zlib: http://opensource.org/licenses/Zlib
    168
    169       For documentation:
    170       * FreeBSD Documentation License
    171         https://www.freebsd.org/copyright/freebsd-doc-license.html
    172
    173       Contributions of code put into the public domain can also be
    174       accepted.
    175
    176       Contributions using other licenses might be accepted, but further
    177       review will be required.
    178
    179    =====================================================
    180    = Change Description / Commit Message / Patch Email =
    181    =====================================================
    182
    183    Your change description should use the standard format for a
    184    commit message, and must include your "Signed-off-by" signature
    185    and the "Contributed-under" message.
    186
    187    == Sample Change Description / Commit Message =
    188
    189    === Start of sample patch email message ===
    190
    191    From: Contributor Name <contributor@example.com>
    192    Subject: [Repository/Branch PATCH] Module: Brief-single-line-summary
    193
    194    Full-commit-message
    195
    196    Contributed-under: TianoCore Contribution Agreement 1.1
    197    Signed-off-by: Contributor Name <contributor@example.com>
    198    ---
    199
    200    An extra message for the patch email which will not be considered part
    201    of the commit message can be added here.
    202
    203    Patch content inline or attached
    204
    205    === End of sample patch email message ===
    206
    207    === Notes for sample patch email ===
    208
    209    * The first line of commit message is taken from the email's subject
    210      line following [Repository/Branch PATCH]. The remaining portion of the
    211      commit message is the email's content until the '---' line.
    212    * git format-patch is one way to create this format
    213
    214    === Definitions for sample patch email ===
    215
    216    * "Repository" is the identifier of the repository the patch applies.
    217      This identifier should only be provided for repositories other than
    218      'edk2'. For example 'edk2-BuildSpecification' or 'staging'.
    219    * "Branch" is the identifier of the branch the patch applies. This
    220      identifier should only be provided for branches other than 'edk2/master'.
    221      For example 'edk2/UDK2015', 'edk2-BuildSpecification/release/1.27', or
    222      'staging/edk2-test'.
    223    * "Module" is a short identifier for the affected code or documentation. For
    224      example 'MdePkg', 'MdeModulePkg/UsbBusDxe', 'Introduction', or
    225      'EDK II INF File Format'.
    226    * "Brief-single-line-summary" is a short summary of the change.
    227    * The entire first line should be less than ~70 characters.
    228    * "Full-commit-message" a verbose multiple line comment describing
    229      the change.  Each line should be less than ~70 characters.
    230    * "Contributed-under" explicitly states that the contribution is
    231      made under the terms of the contribution agreement. This
    232      agreement is included below in this document.
    233    * "Signed-off-by" is the contributor's signature identifying them
    234      by their real/legal name and their email address.
    235
    236    ========================================
    237    = TianoCore Contribution Agreement 1.1 =
    238    ========================================
    239
    240    INTEL CORPORATION ("INTEL") MAKES AVAILABLE SOFTWARE, DOCUMENTATION
    241    ("DOCUMENTATION"), INFORMATION AND/OR OTHER MATERIALS FOR USE IN THE
    242    TIANOCORE OPEN SOURCE PROJECT (COLLECTIVELY "CONTENT"). USE OF THE CONTENT
    243    IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT BETWEEN YOU AND
    244    INTEL AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES
    245    INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR
    246    USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND
    247    CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR
    248    REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
    249    AGREEMENT AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
    250    AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT
    251    USE THE CONTENT.
    252
    253    Unless otherwise indicated, all Content (except Documentation) made available
    254    on the TianoCore site is provided to you under the terms and conditions of the
    255    BSD License ("BSD"). A copy of the BSD License is available at
    256    http://opensource.org/licenses/bsd-license.php
    257    or when applicable, in the associated License.txt file.
    258
    259    Unless otherwise indicated, all Documentation made available on the
    260    TianoCore site is provided to you under the terms and conditions of the
    261    FreeBSD Documentation License ("FreeBSD"). A copy of the license is
    262    available at https://www.freebsd.org/copyright/freebsd-doc-license.html or,
    263    when applicable, in the associated License.txt file.
    264
    265    Certain other content may be made available under other licenses as
    266    indicated in or with such Content (for example, in a License.txt file).
    267
    268    You accept and agree to the following terms and conditions for Your
    269    present and future Contributions submitted to TianoCore site. Except
    270    for the license granted to Intel hereunder, You reserve all right,
    271    title, and interest in and to Your Contributions.
    272
    273    == SECTION 1: Definitions ==
    274    * "You" or "Contributor" shall mean the copyright owner or legal
    275      entity authorized by the copyright owner that is making a
    276      Contribution hereunder. All other entities that control, are
    277      controlled by, or are under common control with that entity are
    278      considered to be a single Contributor. For the purposes of this
    279      definition, "control" means (i) the power, direct or indirect, to
    280      cause the direction or management of such entity, whether by
    281      contract or otherwise, or (ii) ownership of fifty percent (50%)
    282      or more of the outstanding shares, or (iii) beneficial ownership
    283      of such entity.
    284    * "Contribution" shall mean any original work of authorship,
    285      including any modifications or additions to an existing work,
    286      that is intentionally submitted by You to the TianoCore site for
    287      inclusion in, or documentation of, any of the Content. For the
    288      purposes of this definition, "submitted" means any form of
    289      electronic, verbal, or written communication sent to the
    290      TianoCore site or its representatives, including but not limited
    291      to communication on electronic mailing lists, source code
    292      control systems, and issue tracking systems that are managed by,
    293      or on behalf of, the TianoCore site for the purpose of
    294      discussing and improving the Content, but excluding
    295      communication that is conspicuously marked or otherwise
    296      designated in writing by You as "Not a Contribution."
    297
    298    == SECTION 2: License for Contributions ==
    299    * Contributor hereby agrees that redistribution and use of the
    300      Contribution in source and binary forms, with or without
    301      modification, are permitted provided that the following
    302      conditions are met:
    303    ** Redistributions of source code must retain the Contributor's
    304       copyright notice, this list of conditions and the following
    305       disclaimer.
    306    ** Redistributions in binary form must reproduce the Contributor's
    307       copyright notice, this list of conditions and the following
    308       disclaimer in the documentation and/or other materials provided
    309       with the distribution.
    310    * Disclaimer. None of the names of Contributor, Intel, or the names
    311      of their respective contributors may be used to endorse or
    312      promote products derived from this software without specific
    313      prior written permission.
    314    * Contributor grants a license (with the right to sublicense) under
    315      claims of Contributor's patents that Contributor can license that
    316      are infringed by the Contribution (as delivered by Contributor) to
    317      make, use, distribute, sell, offer for sale, and import the
    318      Contribution and derivative works thereof solely to the minimum
    319      extent necessary for licensee to exercise the granted copyright
    320      license; this patent license applies solely to those portions of
    321      the Contribution that are unmodified. No hardware per se is
    322      licensed.
    323    * EXCEPT AS EXPRESSLY SET FORTH IN SECTION 3 BELOW, THE
    324      CONTRIBUTION IS PROVIDED BY THE CONTRIBUTOR "AS IS" AND ANY
    325      EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
    326      THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
    327      PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
    328      CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    329      SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
    330      NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    331      LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    332      HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
    333      CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    334      OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE
    335      CONTRIBUTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
    336      DAMAGE.
    337
    338    == SECTION 3: Representations ==
    339    * You represent that You are legally entitled to grant the above
    340      license. If your employer(s) has rights to intellectual property
    341      that You create that includes Your Contributions, You represent
    342      that You have received permission to make Contributions on behalf
    343      of that employer, that Your employer has waived such rights for
    344      Your Contributions.
    345    * You represent that each of Your Contributions is Your original
    346      creation (see Section 4 for submissions on behalf of others).
    347      You represent that Your Contribution submissions include complete
    348      details of any third-party license or other restriction
    349      (including, but not limited to, related patents and trademarks)
    350      of which You are personally aware and which are associated with
    351      any part of Your Contributions.
    352
    353    == SECTION 4: Third Party Contributions ==
    354    * Should You wish to submit work that is not Your original creation,
    355      You may submit it to TianoCore site separately from any
    356      Contribution, identifying the complete details of its source
    357      and of any license or other restriction (including, but not
    358      limited to, related patents, trademarks, and license agreements)
    359      of which You are personally aware, and conspicuously marking the
    360      work as "Submitted on behalf of a third-party: [named here]".
    361
    362    == SECTION 5: Miscellaneous ==
    363    * Applicable Laws. Any claims arising under or relating to this
    364      Agreement shall be governed by the internal substantive laws of
    365      the State of Delaware or federal courts located in Delaware,
    366      without regard to principles of conflict of laws.
    367    * Language. This Agreement is in the English language only, which
    368      language shall be controlling in all respects, and all versions
    369      of this Agreement in any other language shall be for accommodation
    370      only and shall not be binding. All communications and notices made
    371      or given pursuant to this Agreement, and all documentation and
    372      support to be provided, unless otherwise noted, shall be in the
    373      English language.
    374--------------------------------------------------------------------------------
    375
    376--------------------------------------------------------------------------------
    377Contributions.txt: TianoCore Contribution Agreement 1.0
    378--------------------------------------------------------------------------------
    379    ======================
    380    = Code Contributions =
    381    ======================
    382
    383    To make a contribution to a TianoCore project, follow these steps.
    384    1. Create a change description in the format specified below to
    385       use in the source control commit log.
    386    2. Your commit message must include your "Signed-off-by" signature,
    387       and "Contributed-under" message.
    388    3. Your "Contributed-under" message explicitly states that the
    389       contribution is made under the terms of the specified
    390       contribution agreement.  Your "Contributed-under" message
    391       must include the name of contribution agreement and version.
    392       For example: Contributed-under: TianoCore Contribution Agreement 1.0
    393       The "TianoCore Contribution Agreement" is included below in
    394       this document.
    395    4. Submit your code to the TianoCore project using the process
    396       that the project documents on its web page.  If the process is
    397       not documented, then submit the code on development email list
    398       for the project.
    399    5. It is preferred that contributions are submitted using the same
    400       copyright license as the base project. When that is not possible,
    401       then contributions using the following licenses can be accepted:
    402       * BSD (2-clause): http://opensource.org/licenses/BSD-2-Clause
    403       * BSD (3-clause): http://opensource.org/licenses/BSD-3-Clause
    404       * MIT: http://opensource.org/licenses/MIT
    405       * Python-2.0: http://opensource.org/licenses/Python-2.0
    406       * Zlib: http://opensource.org/licenses/Zlib
    407
    408       Contributions of code put into the public domain can also be
    409       accepted.
    410
    411       Contributions using other licenses might be accepted, but further
    412       review will be required.
    413
    414    =====================================================
    415    = Change Description / Commit Message / Patch Email =
    416    =====================================================
    417
    418    Your change description should use the standard format for a
    419    commit message, and must include your "Signed-off-by" signature
    420    and the "Contributed-under" message.
    421
    422    == Sample Change Description / Commit Message =
    423
    424    === Start of sample patch email message ===
    425
    426    From: Contributor Name <contributor@example.com>
    427    Subject: [PATCH] CodeModule: Brief-single-line-summary
    428
    429    Full-commit-message
    430
    431    Contributed-under: TianoCore Contribution Agreement 1.0
    432    Signed-off-by: Contributor Name <contributor@example.com>
    433    ---
    434
    435    An extra message for the patch email which will not be considered part
    436    of the commit message can be added here.
    437
    438    Patch content inline or attached
    439
    440    === End of sample patch email message ===
    441
    442    === Notes for sample patch email ===
    443
    444    * The first line of commit message is taken from the email's subject
    445      line following [PATCH]. The remaining portion of the commit message
    446      is the email's content until the '---' line.
    447    * git format-patch is one way to create this format
    448
    449    === Definitions for sample patch email ===
    450
    451    * "CodeModule" is a short idenfier for the affected code.  For
    452      example MdePkg, or MdeModulePkg UsbBusDxe.
    453    * "Brief-single-line-summary" is a short summary of the change.
    454    * The entire first line should be less than ~70 characters.
    455    * "Full-commit-message" a verbose multiple line comment describing
    456      the change.  Each line should be less than ~70 characters.
    457    * "Contributed-under" explicitely states that the contribution is
    458      made under the terms of the contribtion agreement.  This
    459      agreement is included below in this document.
    460    * "Signed-off-by" is the contributor's signature identifying them
    461      by their real/legal name and their email address.
    462
    463    ========================================
    464    = TianoCore Contribution Agreement 1.0 =
    465    ========================================
    466
    467    INTEL CORPORATION ("INTEL") MAKES AVAILABLE SOFTWARE, DOCUMENTATION,
    468    INFORMATION AND/OR OTHER MATERIALS FOR USE IN THE TIANOCORE OPEN SOURCE
    469    PROJECT (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS GOVERNED BY THE
    470    TERMS AND CONDITIONS OF THIS AGREEMENT BETWEEN YOU AND INTEL AND/OR THE
    471    TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR
    472    REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE
    473    CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS
    474    OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
    475    BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
    476    AGREEMENT AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
    477    AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT
    478    USE THE CONTENT.
    479
    480    Unless otherwise indicated, all Content made available on the TianoCore
    481    site is provided to you under the terms and conditions of the BSD
    482    License ("BSD"). A copy of the BSD License is available at
    483    http://opensource.org/licenses/bsd-license.php
    484    or when applicable, in the associated License.txt file.
    485
    486    Certain other content may be made available under other licenses as
    487    indicated in or with such Content. (For example, in a License.txt file.)
    488
    489    You accept and agree to the following terms and conditions for Your
    490    present and future Contributions submitted to TianoCore site. Except
    491    for the license granted to Intel hereunder, You reserve all right,
    492    title, and interest in and to Your Contributions.
    493
    494    == SECTION 1: Definitions ==
    495    * "You" or "Contributor" shall mean the copyright owner or legal
    496      entity authorized by the copyright owner that is making a
    497      Contribution hereunder. All other entities that control, are
    498      controlled by, or are under common control with that entity are
    499      considered to be a single Contributor. For the purposes of this
    500      definition, "control" means (i) the power, direct or indirect, to
    501      cause the direction or management of such entity, whether by
    502      contract or otherwise, or (ii) ownership of fifty percent (50%)
    503      or more of the outstanding shares, or (iii) beneficial ownership
    504      of such entity.
    505    * "Contribution" shall mean any original work of authorship,
    506      including any modifications or additions to an existing work,
    507      that is intentionally submitted by You to the TinaoCore site for
    508      inclusion in, or documentation of, any of the Content. For the
    509      purposes of this definition, "submitted" means any form of
    510      electronic, verbal, or written communication sent to the
    511      TianoCore site or its representatives, including but not limited
    512      to communication on electronic mailing lists, source code
    513      control systems, and issue tracking systems that are managed by,
    514      or on behalf of, the TianoCore site for the purpose of
    515      discussing and improving the Content, but excluding
    516      communication that is conspicuously marked or otherwise
    517      designated in writing by You as "Not a Contribution."
    518
    519    == SECTION 2: License for Contributions ==
    520    * Contributor hereby agrees that redistribution and use of the
    521      Contribution in source and binary forms, with or without
    522      modification, are permitted provided that the following
    523      conditions are met:
    524    ** Redistributions of source code must retain the Contributor's
    525       copyright notice, this list of conditions and the following
    526       disclaimer.
    527    ** Redistributions in binary form must reproduce the Contributor's
    528       copyright notice, this list of conditions and the following
    529       disclaimer in the documentation and/or other materials provided
    530       with the distribution.
    531    * Disclaimer. None of the names of Contributor, Intel, or the names
    532      of their respective contributors may be used to endorse or
    533      promote products derived from this software without specific
    534      prior written permission.
    535    * Contributor grants a license (with the right to sublicense) under
    536      claims of Contributor's patents that Contributor can license that
    537      are infringed by the Contribution (as delivered by Contributor) to
    538      make, use, distribute, sell, offer for sale, and import the
    539      Contribution and derivative works thereof solely to the minimum
    540      extent necessary for licensee to exercise the granted copyright
    541      license; this patent license applies solely to those portions of
    542      the Contribution that are unmodified. No hardware per se is
    543      licensed.
    544    * EXCEPT AS EXPRESSLY SET FORTH IN SECTION 3 BELOW, THE
    545      CONTRIBUTION IS PROVIDED BY THE CONTRIBUTOR "AS IS" AND ANY
    546      EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
    547      THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
    548      PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
    549      CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    550      SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
    551      NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    552      LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    553      HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
    554      CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    555      OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE
    556      CONTRIBUTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
    557      DAMAGE.
    558
    559    == SECTION 3: Representations ==
    560    * You represent that You are legally entitled to grant the above
    561      license. If your employer(s) has rights to intellectual property
    562      that You create that includes Your Contributions, You represent
    563      that You have received permission to make Contributions on behalf
    564      of that employer, that Your employer has waived such rights for
    565      Your Contributions.
    566    * You represent that each of Your Contributions is Your original
    567      creation (see Section 4 for submissions on behalf of others).
    568      You represent that Your Contribution submissions include complete
    569      details of any third-party license or other restriction
    570      (including, but not limited to, related patents and trademarks)
    571      of which You are personally aware and which are associated with
    572      any part of Your Contributions.
    573
    574    == SECTION 4: Third Party Contributions ==
    575    * Should You wish to submit work that is not Your original creation,
    576      You may submit it to TianoCore site separately from any
    577      Contribution, identifying the complete details of its source
    578      and of any license or other restriction (including, but not
    579      limited to, related patents, trademarks, and license agreements)
    580      of which You are personally aware, and conspicuously marking the
    581      work as "Submitted on behalf of a third-party: [named here]".
    582
    583    == SECTION 5: Miscellaneous ==
    584    * Applicable Laws. Any claims arising under or relating to this
    585      Agreement shall be governed by the internal substantive laws of
    586      the State of Delaware or federal courts located in Delaware,
    587      without regard to principles of conflict of laws.
    588    * Language. This Agreement is in the English language only, which
    589      language shall be controlling in all respects, and all versions
    590      of this Agreement in any other language shall be for accommodation
    591      only and shall not be binding. All communications and notices made
    592      or given pursuant to this Agreement, and all documentation and
    593      support to be provided, unless otherwise noted, shall be in the
    594      English language.
    595--------------------------------------------------------------------------------
    596
    597
    598==> edk2/OvmfPkg/License.txt <==
    599Copyright (c) 2012 - 2019, Intel Corporation. All rights reserved.
    600
    601SPDX-License-Identifier: BSD-2-Clause-Patent
    602
    603Redistribution and use in source and binary forms, with or without
    604modification, are permitted provided that the following conditions are met:
    605
    6061. Redistributions of source code must retain the above copyright notice,
    607   this list of conditions and the following disclaimer.
    608
    6092. Redistributions in binary form must reproduce the above copyright notice,
    610   this list of conditions and the following disclaimer in the documentation
    611   and/or other materials provided with the distribution.
    612
    613Subject to the terms and conditions of this license, each copyright holder
    614and contributor hereby grants to those receiving rights under this license
    615a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
    616(except for failure to satisfy the conditions of this license) patent
    617license to make, have made, use, offer to sell, sell, import, and otherwise
    618transfer this software, where such license applies only to those patent
    619claims, already acquired or hereafter acquired, licensable by such copyright
    620holder or contributor that are necessarily infringed by:
    621
    622(a) their Contribution(s) (the licensed copyrights of copyright holders and
    623    non-copyrightable additions of contributors, in source or binary form)
    624    alone; or
    625
    626(b) combination of their Contribution(s) with the work of authorship to
    627    which such Contribution(s) was added by such copyright holder or
    628    contributor, if, at the time the Contribution is added, such addition
    629    causes such combination to be necessarily infringed. The patent license
    630    shall not apply to any other combinations which include the
    631    Contribution.
    632
    633Except as expressly stated above, no rights or licenses from any copyright
    634holder or contributor is granted under this license, whether expressly, by
    635implication, estoppel or otherwise.
    636
    637DISCLAIMER
    638
    639THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
    640AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    641IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
    642ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
    643LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
    644CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    645SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
    646INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
    647CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    648ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
    649POSSIBILITY OF SUCH DAMAGE.
    650
    651================================================================================
    652
    653Some files are subject to the following license, the MIT license. Those files
    654are located in:
    655- OvmfPkg/Include/IndustryStandard/Xen/
    656- OvmfPkg/XenBusDxe/
    657
    658SPDX-License-Identifier: MIT
    659
    660Permission is hereby granted, free of charge, to any person obtaining a copy
    661of this software and associated documentation files (the "Software"), to deal
    662in the Software without restriction, including without limitation the rights
    663to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
    664copies of the Software, and to permit persons to whom the Software is
    665furnished to do so, subject to the following conditions:
    666
    667The above copyright notice and this permission notice (including the next
    668paragraph) shall be included in all copies or substantial portions of the
    669Software.
    670
    671THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    672IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    673FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    674AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    675LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    676OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
    677THE SOFTWARE.
    678
    679==> edk2/ArmPkg/Library/ArmSoftFloatLib/berkeley-softfloat-3/COPYING.txt <==
    680
    681License for Berkeley SoftFloat Release 3e
    682
    683John R. Hauser
    6842018 January 20
    685
    686The following applies to the whole of SoftFloat Release 3e as well as to
    687each source file individually.
    688
    689Copyright 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018 The Regents of the
    690University of California.  All rights reserved.
    691
    692Redistribution and use in source and binary forms, with or without
    693modification, are permitted provided that the following conditions are met:
    694
    695 1. Redistributions of source code must retain the above copyright notice,
    696    this list of conditions, and the following disclaimer.
    697
    698 2. Redistributions in binary form must reproduce the above copyright
    699    notice, this list of conditions, and the following disclaimer in the
    700    documentation and/or other materials provided with the distribution.
    701
    702 3. Neither the name of the University nor the names of its contributors
    703    may be used to endorse or promote products derived from this software
    704    without specific prior written permission.
    705
    706THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS", AND ANY
    707EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
    708WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE
    709DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
    710DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
    711(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    712LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
    713ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    714(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
    715THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    716
    717
    718==> edk2/CryptoPkg/Library/OpensslLib/openssl/LICENSE <==
    719
    720  LICENSE ISSUES
    721  ==============
    722
    723  The OpenSSL toolkit stays under a double license, i.e. both the conditions of
    724  the OpenSSL License and the original SSLeay license apply to the toolkit.
    725  See below for the actual license texts.
    726
    727  OpenSSL License
    728  ---------------
    729
    730/* ====================================================================
    731 * Copyright (c) 1998-2019 The OpenSSL Project.  All rights reserved.
    732 *
    733 * Redistribution and use in source and binary forms, with or without
    734 * modification, are permitted provided that the following conditions
    735 * are met:
    736 *
    737 * 1. Redistributions of source code must retain the above copyright
    738 *    notice, this list of conditions and the following disclaimer.
    739 *
    740 * 2. Redistributions in binary form must reproduce the above copyright
    741 *    notice, this list of conditions and the following disclaimer in
    742 *    the documentation and/or other materials provided with the
    743 *    distribution.
    744 *
    745 * 3. All advertising materials mentioning features or use of this
    746 *    software must display the following acknowledgment:
    747 *    "This product includes software developed by the OpenSSL Project
    748 *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
    749 *
    750 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
    751 *    endorse or promote products derived from this software without
    752 *    prior written permission. For written permission, please contact
    753 *    openssl-core@openssl.org.
    754 *
    755 * 5. Products derived from this software may not be called "OpenSSL"
    756 *    nor may "OpenSSL" appear in their names without prior written
    757 *    permission of the OpenSSL Project.
    758 *
    759 * 6. Redistributions of any form whatsoever must retain the following
    760 *    acknowledgment:
    761 *    "This product includes software developed by the OpenSSL Project
    762 *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
    763 *
    764 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
    765 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    766 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    767 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
    768 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    769 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
    770 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    771 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    772 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
    773 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    774 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
    775 * OF THE POSSIBILITY OF SUCH DAMAGE.
    776 * ====================================================================
    777 *
    778 * This product includes cryptographic software written by Eric Young
    779 * (eay@cryptsoft.com).  This product includes software written by Tim
    780 * Hudson (tjh@cryptsoft.com).
    781 *
    782 */
    783
    784 Original SSLeay License
    785 -----------------------
    786
    787/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
    788 * All rights reserved.
    789 *
    790 * This package is an SSL implementation written
    791 * by Eric Young (eay@cryptsoft.com).
    792 * The implementation was written so as to conform with Netscapes SSL.
    793 *
    794 * This library is free for commercial and non-commercial use as long as
    795 * the following conditions are aheared to.  The following conditions
    796 * apply to all code found in this distribution, be it the RC4, RSA,
    797 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
    798 * included with this distribution is covered by the same copyright terms
    799 * except that the holder is Tim Hudson (tjh@cryptsoft.com).
    800 *
    801 * Copyright remains Eric Young's, and as such any Copyright notices in
    802 * the code are not to be removed.
    803 * If this package is used in a product, Eric Young should be given attribution
    804 * as the author of the parts of the library used.
    805 * This can be in the form of a textual message at program startup or
    806 * in documentation (online or textual) provided with the package.
    807 *
    808 * Redistribution and use in source and binary forms, with or without
    809 * modification, are permitted provided that the following conditions
    810 * are met:
    811 * 1. Redistributions of source code must retain the copyright
    812 *    notice, this list of conditions and the following disclaimer.
    813 * 2. Redistributions in binary form must reproduce the above copyright
    814 *    notice, this list of conditions and the following disclaimer in the
    815 *    documentation and/or other materials provided with the distribution.
    816 * 3. All advertising materials mentioning features or use of this software
    817 *    must display the following acknowledgement:
    818 *    "This product includes cryptographic software written by
    819 *     Eric Young (eay@cryptsoft.com)"
    820 *    The word 'cryptographic' can be left out if the rouines from the library
    821 *    being used are not cryptographic related :-).
    822 * 4. If you include any Windows specific code (or a derivative thereof) from
    823 *    the apps directory (application code) you must include an acknowledgement:
    824 *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
    825 *
    826 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
    827 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    828 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
    829 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
    830 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
    831 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
    832 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    833 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
    834 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
    835 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
    836 * SUCH DAMAGE.
    837 *
    838 * The licence and distribution terms for any publically available version or
    839 * derivative of this code cannot be changed.  i.e. this code cannot simply be
    840 * copied and put under another distribution licence
    841 * [including the GNU Public Licence.]
    842 */
    843