For the avoidance of any doubt refer to the comment included at the top\r
of each source and header file for license and copyright information.\r
\r
-This is a list of files for which Richard Barry is not the copyright owner\r
-and are NOT COVERED BY THE GPL.\r
+This is a list of files for which Real Time Engineers Ltd are not the \r
+copyright owner and are NOT COVERED BY THE GPL.\r
\r
\r
1) Various header files provided by silicon manufacturers and tool vendors\r
Permission has been granted by the various copyright holders for these\r
files to be included in the FreeRTOS download. Users must ensure license\r
conditions are adhered to for any use other than compilation of the \r
- FreeRTOS demo application.\r
+ FreeRTOS demo applications.\r
\r
2) The uIP TCP/IP stack the copyright of which is held by Adam Dunkels.\r
Users must ensure the open source license conditions stated at the top \r
conditions stated at the top of each lwIP source file is understood and \r
adhered to.\r
\r
-4) All files contained within the FreeRTOS\Demo\CORTEX_LM3S102_GCC\hw_include\r
- directory. The copyright of these files is owned by Luminary Micro.\r
- Permission has been granted by Luminary Micro for these files to be \r
- included in the FreeRTOS download. Users must ensure the license \r
- conditions stated at the top of the human readable files are understood \r
- and adhered at all times for all files in that directory.\r
+4) Various peripheral driver source files and binaries provided by silicon\r
+ manufacturers and tool vendors. Permission has been granted by the\r
+ various copyright holders for these files to be included in the FreeRTOS\r
+ download. Users must ensure license conditions are adhered to for any\r
+ use other than compilation of the FreeRTOS demo applications.\r
\r
5) The files contained within FreeRTOS\Demo\WizNET_DEMO_TERN_186\tern_code,\r
which are slightly modified versions of code provided by and copyright to\r
\r
The GPL license text follows.\r
\r
-An exception to this license exists that can be applied should you \r
-wish to use FreeRTOS in a work that includes commercial or \r
-proprietary code without being obliged to provide source code for the \r
-proprietary components. See the licensing section of \r
-http://www.FreeRTOS.org for full details.\r
+A special exception to the GPL is included to allow you to distribute a \r
+combined work that includes FreeRTOS without being obliged to provide\r
+the source code for any proprietary components. See the licensing section\r
+of http://www.FreeRTOS.org for full details. The exception text is also\r
+included at the bottom of this file.\r
+\r
--------------------------------------------------------------------\r
\r
\r
Copyright (C) <year> <name of author>\r
\r
This program is free software; you can redistribute it and/or modify\r
- it under the terms of the GNU General Public License as published by\r
+ it under the terms of the GNU General Public License** as published by\r
the Free Software Foundation; either version 2 of the License, or\r
(at your option) any later version.\r
\r
library. If this is what you want to do, use the GNU Library General\r
Public License instead of this License.\r
\r
+----------------------------------------------------------------------------\r
+\r
+The FreeRTOS GPL Exception Text:\r
+\r
+Any FreeRTOS source code, whether modified or in it's original release form, \r
+or whether in whole or in part, can only be distributed by you under the terms \r
+of the GNU General Public License plus this exception. An independent module is \r
+a module which is not derived from or based on FreeRTOS.\r
+\r
+Clause 1:\r
+\r
+Linking FreeRTOS statically or dynamically with other modules is making a \r
+combined work based on FreeRTOS. Thus, the terms and conditions of the GNU \r
+General Public License cover the whole combination.\r
+\r
+As a special exception, the copyright holder of FreeRTOS gives you permission \r
+to link FreeRTOS with independent modules that communicate with FreeRTOS \r
+solely through the FreeRTOS API interface, regardless of the license terms of \r
+these independent modules, and to copy and distribute the resulting combined \r
+work under terms of your choice, provided that\r
+\r
+ + Every copy of the combined work is accompanied by a written statement that \r
+ details to the recipient the version of FreeRTOS used and an offer by yourself \r
+ to provide the FreeRTOS source code (including any modifications you may have \r
+ made) should the recipient request it.\r
+\r
+ + The combined work is not itself an RTOS, scheduler, kernel or related product.\r
+\r
+ + The independent modules add significant and primary functionality to FreeRTOS \r
+ and do not merely extend the existing functionality already present in FreeRTOS.\r
+\r
+Clause 2:\r
+\r
+FreeRTOS may not be used for any competitive or comparative purpose, including the \r
+publication of any form of run time or compile time metric, without the express \r
+permission of Real Time Engineers Ltd. (this is the norm within the industry and \r
+is intended to ensure information accuracy).\r
projects / freertos / blobdiff