edk2-licenses.txt 42 KB

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