COPYING 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268
  1. COPYING -- Describes the terms under which Nuttx is distributed. A copy of
  2. the BSD-style licensing is included in this file. In my words -- I believe
  3. that you should free to use NuttX in any environment, private, private,
  4. commercial, open, closed, etc. provided only that you respect the modest
  5. copyright notices as described in license (below), respect Trademarks, and
  6. include a copy of the BSD license. Please feel free to contact me if you
  7. have any licensing concerns.
  8. Copyright Date Notation: Copyright information is provided in the header
  9. of each file. This copyright information includes the name of the copyright
  10. holder and the year(s) in which copyrighted additions to the file were made
  11. to the file. A comma (',') is used to separate years in the list of years.
  12. A hyphen ('-') is used as a more compact notation when additions were made
  13. over several consecutive years. So for example, "2007, 2011" would mean
  14. that copyrighted additions were made during the years of 2007 and 2011
  15. whereas "2007-2011" would indicate copyrighted additions in the years 2007,
  16. 2008, 2009, 2010, and 2011.
  17. Copyright Line Continuation: Copy information which exceeds the usable line
  18. lengh may be broken and continued on the following line, such as:
  19. Copyright (C) 2007-2010, 2012, 2014-2015, 2017 Gregory Nutt. All
  20. rights reserved.
  21. NuttX
  22. ^^^^^
  23. License for NuttX in general (authorship and copyright dates on individual
  24. files will vary):
  25. /****************************************************************************
  26. * directory path/filename
  27. *
  28. * Copyright (C) 2007-2018 Gregory Nutt. All rights reserved.
  29. * Author: Gregory Nutt <gnutt@nuttx.org>
  30. *
  31. * Redistribution and use in source and binary forms, with or without
  32. * modification, are permitted provided that the following conditions
  33. * are met:
  34. *
  35. * 1. Redistributions of source code must retain the above copyright
  36. * notice, this list of conditions and the following disclaimer.
  37. * 2. Redistributions in binary form must reproduce the above copyright
  38. * notice, this list of conditions and the following disclaimer in
  39. * the documentation and/or other materials provided with the
  40. * distribution.
  41. * 3. Neither the name NuttX nor the names of its contributors may be
  42. * used to endorse or promote products derived from this software
  43. * without specific prior written permission.
  44. *
  45. * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
  46. * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
  47. * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
  48. * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
  49. * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
  50. * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
  51. * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
  52. * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
  53. * AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  54. * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
  55. * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
  56. * POSSIBILITY OF SUCH DAMAGE.
  57. *
  58. ****************************************************************************/
  59. FAT Long File Names
  60. ^^^^^^^^^^^^^^^^^^^
  61. NOTE: If CONFIG_FAT_LFN is defined in your NuttX configuration file, then
  62. there may be some legal, patent issues. The following was extracted from
  63. the entry "File Allocation Table from Wikipedia, the free encyclopedia:
  64. "On December 3, 2003 Microsoft announced it would be offering licenses
  65. for use of its FAT specification and 'associated intellectual property',
  66. at the cost of a US$0.25 royalty per unit sold, with a $250,000 maximum
  67. royalty per license agreement.
  68. o "U.S. Patent 5,745,902 (http://www.google.com/patents?vid=5745902) -
  69. Method and system for accessing a file using file names having
  70. different file name formats. ...
  71. o "U.S. Patent 5,579,517 (http://www.google.com/patents?vid=5579517) -
  72. Common name space for long and short filenames. ...
  73. o "U.S. Patent 5,758,352 (http://www.google.com/patents?vid=5758352) -
  74. Common name space for long and short filenames. ...
  75. o "U.S. Patent 6,286,013 (http://www.google.com/patents?vid=6286013) -
  76. Method and system for providing a common name space for long and
  77. short file names in an operating system. ...
  78. "Many technical commentators have concluded that these patents only cover
  79. FAT implementations that include support for long filenames, and that
  80. removable solid state media and consumer devices only using short names
  81. would be unaffected. ..."
  82. This Wikipedia entry has been updated with recent legal decisions in favor
  83. of Microsoft. Refer to:
  84. https://en.wikipedia.org/wiki/File_Allocation_Table#Patents
  85. So you have been forewarned: Use the long filename at your own risk!
  86. uIP
  87. ^^^
  88. Many lower-level networking components of NuttX derive from uIP which
  89. has a similar BSD style license:
  90. Copyright (c) 2001-2003, Adam Dunkels.
  91. All rights reserved.
  92. IGMP
  93. ^^^^
  94. IGMP support, if enabled, adds additional logic by Steve Reynolds:
  95. Copyright (c) 2002 CITEL Technologies Ltd.
  96. All rights reserved.
  97. The HID Parser in drivers/usbhost
  98. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  99. Adapted from the LUFA Library (MIT license):
  100. Copyright 2011 Dean Camera (dean [at] fourwalledcubicle [dot] com)
  101. dean [at] fourwalledcubicle [dot] com, www.lufa-lib.org
  102. Permission to use, copy, modify, distribute, and sell this
  103. software and its documentation for any purpose is hereby granted
  104. without fee, provided that the above copyright notice appear in
  105. all copies and that both that the copyright notice and this
  106. permission notice and warranty disclaimer appear in supporting
  107. documentation, and that the name of the author not be used in
  108. advertising or publicity pertaining to distribution of the
  109. software without specific, written prior permission.
  110. The author disclaim all warranties with regard to this
  111. software, including all implied warranties of merchantability
  112. and fitness. In no event shall the author be liable for any
  113. special, indirect or consequential damages or any damages
  114. whatsoever resulting from loss of use, data or profits, whether
  115. in an action of contract, negligence or other tortious action,
  116. arising out of or in connection with the use or performance of
  117. this software.
  118. Certain functions in the NuttX C-library derive from other BSD-compatible
  119. sources:
  120. fs/nfs:
  121. ^^^^^^^
  122. NFS:
  123. Copyright (c) 1989, 1991, 1993, 1995 The Regents of the University of
  124. California. All rights reserved.
  125. and RPC also has:
  126. Copyright (c) 2004 The Regents of the University of Michigan.
  127. Copyright (c) 2004 Weston Andros Adamson <muzzle@umich.edu>.
  128. Copyright (c) 2004 Marius Aamodt Eriksen <marius@umich.edu>.
  129. The University of Michigan uses a modified BSD license equivalent to
  130. the NuttX license. The University of California code uses the original
  131. BSD license and requires that I state the following:
  132. "This product includes software developed by the University of
  133. California, Berkeley and its contributors."
  134. fs/spiffs
  135. ^^^^^^^^^
  136. The MIT License (MIT)
  137. Copyright (c) 2013-2017 Peter Andersson (pelleplutt1976<at>gmail.com)
  138. Permission is hereby granted, free of charge, to any person obtaining a copy of
  139. this software and associated documentation files (the "Software"), to deal in
  140. the Software without restriction, including without limitation the rights to
  141. use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
  142. the Software, and to permit persons to whom the Software is furnished to do so,
  143. subject to the following conditions:
  144. The above copyright notice and this permission notice shall be included in all
  145. copies or substantial portions of the Software.
  146. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  147. IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
  148. FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
  149. COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
  150. IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
  151. CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  152. strtod():
  153. ^^^^^^^^
  154. Copyright (C) 2002 Michael Ringgaard. All rights reserved.
  155. Copyright (C) 2006-2007 H. Peter Anvin.
  156. dtoa():
  157. ^^^^^^
  158. If you enable floating point conversions with CONFIG_LIBC_FLOATINGPOINT,
  159. then some files with an unmodified BSD license will be included. That
  160. license is similar to the above (modified) BSD license, but has an
  161. additional requirement that I state the following:
  162. "This product includes software developed by the University of
  163. California, Berkeley and its contributors."
  164. libc/string/lib_vikmemcpy.c
  165. ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  166. If you enable CONFIG_MEMCPY_VIK, then you will build with the optimized
  167. version of memcpy from Daniel Vik. Licensing information for that version
  168. of memcpy() follows:
  169. Copyright (C) 1999-2010 Daniel Vik
  170. This software is provided 'as-is', without any express or implied
  171. warranty. In no event will the authors be held liable for any
  172. damages arising from the use of this software.
  173. Permission is granted to anyone to use this software for any
  174. purpose, including commercial applications, and to alter it and
  175. redistribute it freely, subject to the following restrictions:
  176. 1. The origin of this software must not be misrepresented; you
  177. must not claim that you wrote the original software. If you
  178. use this software in a product, an acknowledgment in the
  179. use this software in a product, an acknowledgment in the
  180. product documentation would be appreciated but is not
  181. required.
  182. 2. Altered source versions must be plainly marked as such, and
  183. must not be misrepresented as being the original software.
  184. 3. This notice may not be removed or altered from any source
  185. distribution.
  186. libs/libc/math
  187. ^^^^^^^^^^^^^^
  188. If you enable CONFIG_LIB, you will build the math library at libc/math.
  189. This library was taken from the math library developed for the Rhombus
  190. OS by Nick Johnson (https://github.com/nickbjohnson4224/rhombus). This
  191. port was contributed by Darcy Gong. The Rhombus math library has this
  192. compatible MIT license:
  193. Copyright (C) 2009-2011 Nick Johnson <nickbjohnson4224 at gmail.com>
  194. Permission to use, copy, modify, and distribute this software for any
  195. purpose with or without fee is hereby granted, provided that the above
  196. copyright notice and this permission notice appear in all copies.
  197. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
  198. WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
  199. MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
  200. ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
  201. WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
  202. ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
  203. drivers/video/ov2640
  204. ^^^^^^^^^^^^^^^^^^^^
  205. WARNING: Some of the information in the data tables in this file came
  206. from other projects with conflicting licenses: Linux and ArduCAM. Those
  207. both have GPL licenses. I am not sure if it is proper or not to lift the
  208. content of those tables and still retain this BSD license. I am guessing
  209. so, but I am not a copyright attorney so you should use this driver in
  210. products at your own risk.