OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [user-guide/] [ecos-licensing.html] - Blame information for rev 199

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 28 unneback
<!-- Copyright (C) 2003 Red Hat, Inc.                                -->
2
<!-- This material may be distributed only subject to the terms      -->
3
<!-- and conditions set forth in the Open Publication License, v1.0  -->
4
<!-- or later (the latest version is presently available at          -->
5
<!-- http://www.opencontent.org/openpub/).                           -->
6
<!-- Distribution of the work or derivative of the work in any       -->
7
<!-- standard (paper) book form is prohibited unless prior           -->
8
<!-- permission is obtained from the copyright holder.               -->
9
<HTML
10
><HEAD
11
><TITLE
12
>eCos Licence Overview</TITLE
13
><meta name="MSSmartTagsPreventParsing" content="TRUE">
14
<META
15
NAME="GENERATOR"
16
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
17
"><LINK
18
REL="HOME"
19
TITLE="eCos User Guide"
20
HREF="ecos-user-guide.html"><LINK
21
REL="UP"
22
TITLE="Introduction"
23
HREF="user-guide-introduction.html"><LINK
24
REL="PREVIOUS"
25
TITLE="eCos Overview"
26
HREF="ecos-overview.html"><LINK
27
REL="NEXT"
28
TITLE="Previous License"
29
HREF="ecos-licensing-previous.html"></HEAD
30
><BODY
31
CLASS="CHAPTER"
32
BGCOLOR="#FFFFFF"
33
TEXT="#000000"
34
LINK="#0000FF"
35
VLINK="#840084"
36
ALINK="#0000FF"
37
><DIV
38
CLASS="NAVHEADER"
39
><TABLE
40
SUMMARY="Header navigation table"
41
WIDTH="100%"
42
BORDER="0"
43
CELLPADDING="0"
44
CELLSPACING="0"
45
><TR
46
><TH
47
COLSPAN="3"
48
ALIGN="center"
49
>eCos User Guide</TH
50
></TR
51
><TR
52
><TD
53
WIDTH="10%"
54
ALIGN="left"
55
VALIGN="bottom"
56
><A
57
HREF="ecos-overview.html"
58
ACCESSKEY="P"
59
>Prev</A
60
></TD
61
><TD
62
WIDTH="80%"
63
ALIGN="center"
64
VALIGN="bottom"
65
></TD
66
><TD
67
WIDTH="10%"
68
ALIGN="right"
69
VALIGN="bottom"
70
><A
71
HREF="ecos-licensing-previous.html"
72
ACCESSKEY="N"
73
>Next</A
74
></TD
75
></TR
76
></TABLE
77
><HR
78
ALIGN="LEFT"
79
WIDTH="100%"></DIV
80
><DIV
81
CLASS="CHAPTER"
82
><H1
83
><A
84
NAME="ECOS-LICENSING">Chapter 3. <SPAN
85
CLASS="PRODUCTNAME"
86
>eCos</SPAN
87
> Licence Overview</H1
88
><DIV
89
CLASS="TOC"
90
><DL
91
><DT
92
><B
93
>Table of Contents</B
94
></DT
95
><DT
96
><A
97
HREF="ecos-licensing.html#ECOS-LICENSING-QNA"
98
>Questions and answers</A
99
></DT
100
><DT
101
><A
102
HREF="ecos-licensing-previous.html"
103
>Previous License</A
104
></DT
105
></DL
106
></DIV
107
><P
108
>As of May 2002, <SPAN
109
CLASS="PRODUCTNAME"
110
>eCos</SPAN
111
> is released
112
under a modified version of the well known <A
113
HREF="http://www.gnu.org/copyleft/gpl.html"
114
TARGET="_top"
115
>GNU General Public License
116
(GPL)</A
117
>, now making it an <A
118
HREF="http://www.gnu.org/philosophy/license-list.html"
119
TARGET="_top"
120
>official
121
GPL-compatible Free Software License</A
122
>. An exception clause has
123
been added to the <SPAN
124
CLASS="PRODUCTNAME"
125
>eCos</SPAN
126
> license which limits
127
the circumstances in which the license applies to other code when used
128
in conjunction with <SPAN
129
CLASS="PRODUCTNAME"
130
>eCos</SPAN
131
>. The exception
132
clause is as follows:</P
133
><TABLE
134
BORDER="5"
135
BGCOLOR="#E0E0F0"
136
WIDTH="70%"
137
><TR
138
><TD
139
><PRE
140
CLASS="PROGRAMLISTING"
141
> As a special exception, if other files instantiate templates or use macros
142
 or inline functions from this file, or you compile this file and link it
143
 with other works to produce a work based on this file, this file does not
144
 by itself cause the resulting work to be covered by the GNU General Public
145
 License. However the source code for this file must still be made
146
 available in accordance with section (3) of the GNU General Public
147
 License.
148
 
149
 This exception does not invalidate any other reasons why a work based on
150
 this file might be covered by the GNU General Public License.</PRE
151
></TD
152
></TR
153
></TABLE
154
><P
155
>The goal of the license is to serve the
156
<SPAN
157
CLASS="PRODUCTNAME"
158
>eCos</SPAN
159
> user community as a whole. It allows
160
all <SPAN
161
CLASS="PRODUCTNAME"
162
>eCos</SPAN
163
> users to develop products without
164
paying anybody anything, no matter how many developers are working on
165
the product or how many units will be shipped. The license also
166
guarantees that the <SPAN
167
CLASS="PRODUCTNAME"
168
>eCos</SPAN
169
> source code will
170
always be freely available. This applies not only to the core
171
<SPAN
172
CLASS="PRODUCTNAME"
173
>eCos</SPAN
174
> code itself but also to any changes
175
that anybody makes to the core. In particular, it should prevent any
176
company or individual contributing code to the system and then later
177
claiming that all <SPAN
178
CLASS="PRODUCTNAME"
179
>eCos</SPAN
180
> users are now guilty
181
of copyright or patent infringements and have to pay royalties. It
182
should also prevent any company from making some small improvements,
183
calling the result a completely new system, and releasing this under a
184
new and less generous license.</P
185
><P
186
>The license does <SPAN
187
CLASS="emphasis"
188
><I
189
CLASS="EMPHASIS"
190
>not</I
191
></SPAN
192
> require users to
193
release the source code of any <SPAN
194
CLASS="emphasis"
195
><I
196
CLASS="EMPHASIS"
197
>applications</I
198
></SPAN
199
> that
200
are developed with <SPAN
201
CLASS="PRODUCTNAME"
202
>eCos</SPAN
203
>. However, if
204
anybody makes any changes to code covered by the
205
<SPAN
206
CLASS="PRODUCTNAME"
207
>eCos</SPAN
208
> license, or writes new files derived
209
in any way from <SPAN
210
CLASS="PRODUCTNAME"
211
>eCos</SPAN
212
> code, then we believe
213
that the entire user community should have the opportunity to benefit
214
from this. The license stipulates that these changes must be made
215
available in source code form to all recipients of binaries based on
216
the modified code, either by including the sources along with the
217
binaries you deliver (or with any device containing such binaries) or
218
with a written offer to supply the source code to the general public
219
for three years. It is perhaps most practical for
220
<SPAN
221
CLASS="PRODUCTNAME"
222
>eCos</SPAN
223
> developers to make the source code
224
available online and inform those who are receiving binaries
225
containing <SPAN
226
CLASS="PRODUCTNAME"
227
>eCos</SPAN
228
> code, and probably also the
229
<SPAN
230
CLASS="PRODUCTNAME"
231
>eCos</SPAN
232
> maintainers, about the location of the
233
code. See the <A
234
HREF="http://www.gnu.org/copyleft/gpl.html"
235
TARGET="_top"
236
>full
237
text of the GPL</A
238
> for the most authoritative definition of the
239
obligations.</P
240
><P
241
>Although it is not strictly necessary to contribute the modified
242
code back to the <SPAN
243
CLASS="PRODUCTNAME"
244
>eCos</SPAN
245
> open source project,
246
we are always pleased to receive code contributions and hope that
247
developers will also be keen to give back in return for what they
248
received from the <SPAN
249
CLASS="PRODUCTNAME"
250
>eCos</SPAN
251
> project completely
252
free of charge.  The <SPAN
253
CLASS="PRODUCTNAME"
254
>eCos</SPAN
255
> maintainers are
256
responsible for deciding whether such contributions should be applied
257
to the public repository. In addition, a <A
258
HREF="http://sources.redhat.com/ecos/assign.html"
259
TARGET="_top"
260
>copyright
261
assignment</A
262
> is required for any significant changes to the core
263
<SPAN
264
CLASS="PRODUCTNAME"
265
>eCos</SPAN
266
> packages.</P
267
><P
268
>The result is a royalty-free system with minimal obligations on
269
the part of application developers. This has resulted in the rapid
270
uptake of <SPAN
271
CLASS="PRODUCTNAME"
272
>eCos</SPAN
273
>. At the same time,
274
<SPAN
275
CLASS="PRODUCTNAME"
276
>eCos</SPAN
277
> is fully open source with all the
278
benefits that implies in terms of quality and innovation. We believe
279
that this is a winning combination.</P
280
><DIV
281
CLASS="SECT1"
282
><H1
283
CLASS="SECT1"
284
><A
285
NAME="ECOS-LICENSING-QNA">Questions and answers</H1
286
><P
287
>The following queries provide some clarification as to the
288
implications of the <SPAN
289
CLASS="PRODUCTNAME"
290
>eCos</SPAN
291
> license. They do
292
not consititute part of the legal meaning of the license.</P
293
><P
294
><SPAN
295
CLASS="emphasis"
296
><I
297
CLASS="EMPHASIS"
298
>Q.</I
299
></SPAN
300
> What is the effect of the
301
<SPAN
302
CLASS="PRODUCTNAME"
303
>eCos</SPAN
304
> license?</P
305
><P
306
><SPAN
307
CLASS="emphasis"
308
><I
309
CLASS="EMPHASIS"
310
>A.</I
311
></SPAN
312
> In the simplest terms, when you
313
distribute anything containing <SPAN
314
CLASS="PRODUCTNAME"
315
>eCos</SPAN
316
> code,
317
you must make the source code to <SPAN
318
CLASS="PRODUCTNAME"
319
>eCos</SPAN
320
>
321
available under the terms of the GPL.</P
322
><P
323
><SPAN
324
CLASS="emphasis"
325
><I
326
CLASS="EMPHASIS"
327
>Q.</I
328
></SPAN
329
> What if I make changes to
330
<SPAN
331
CLASS="PRODUCTNAME"
332
>eCos</SPAN
333
>, or write new code based on
334
<SPAN
335
CLASS="PRODUCTNAME"
336
>eCos</SPAN
337
> code?</P
338
><P
339
><SPAN
340
CLASS="emphasis"
341
><I
342
CLASS="EMPHASIS"
343
>A.</I
344
></SPAN
345
> Then you must make those changes
346
available as well.</P
347
><P
348
><SPAN
349
CLASS="emphasis"
350
><I
351
CLASS="EMPHASIS"
352
>Q.</I
353
></SPAN
354
> Do I have to distribute the source
355
code to my application? Isn't the GPL "viral"?</P
356
><P
357
><SPAN
358
CLASS="emphasis"
359
><I
360
CLASS="EMPHASIS"
361
>A.</I
362
></SPAN
363
> You do not have to distribute any
364
code under the terms of the GPL other than
365
<SPAN
366
CLASS="PRODUCTNAME"
367
>eCos</SPAN
368
> code or code derived from
369
<SPAN
370
CLASS="PRODUCTNAME"
371
>eCos</SPAN
372
>. For example, if you write a HAL port
373
based on copying an existing <SPAN
374
CLASS="PRODUCTNAME"
375
>eCos</SPAN
376
> HAL in
377
any way, you must make the source code available with the
378
binary. However you would not need to make available any other code,
379
such as the code of a wholly separate application linked with
380
<SPAN
381
CLASS="PRODUCTNAME"
382
>eCos</SPAN
383
>.</P
384
><P
385
><SPAN
386
CLASS="emphasis"
387
><I
388
CLASS="EMPHASIS"
389
>Q.</I
390
></SPAN
391
> I would rather stick with the
392
RHEPL code, but I updated my anonymous CVS checkout.</P
393
><P
394
><SPAN
395
CLASS="emphasis"
396
><I
397
CLASS="EMPHASIS"
398
>A.</I
399
></SPAN
400
> You can check out the final
401
version of anonymous CVS before the license change using the CVS tag
402
<TT
403
CLASS="LITERAL"
404
>last-rhepl</TT
405
>. See <A
406
HREF="http://sources.redhat.com/ecos/anoncvs.html"
407
TARGET="_top"
408
>the anonymous CVS
409
access page</A
410
>
411
for details.</P
412
></DIV
413
></DIV
414
><DIV
415
CLASS="NAVFOOTER"
416
><HR
417
ALIGN="LEFT"
418
WIDTH="100%"><TABLE
419
SUMMARY="Footer navigation table"
420
WIDTH="100%"
421
BORDER="0"
422
CELLPADDING="0"
423
CELLSPACING="0"
424
><TR
425
><TD
426
WIDTH="33%"
427
ALIGN="left"
428
VALIGN="top"
429
><A
430
HREF="ecos-overview.html"
431
ACCESSKEY="P"
432
>Prev</A
433
></TD
434
><TD
435
WIDTH="34%"
436
ALIGN="center"
437
VALIGN="top"
438
><A
439
HREF="ecos-user-guide.html"
440
ACCESSKEY="H"
441
>Home</A
442
></TD
443
><TD
444
WIDTH="33%"
445
ALIGN="right"
446
VALIGN="top"
447
><A
448
HREF="ecos-licensing-previous.html"
449
ACCESSKEY="N"
450
>Next</A
451
></TD
452
></TR
453
><TR
454
><TD
455
WIDTH="33%"
456
ALIGN="left"
457
VALIGN="top"
458
><SPAN
459
CLASS="PRODUCTNAME"
460
>eCos</SPAN
461
> Overview</TD
462
><TD
463
WIDTH="34%"
464
ALIGN="center"
465
VALIGN="top"
466
><A
467
HREF="user-guide-introduction.html"
468
ACCESSKEY="U"
469
>Up</A
470
></TD
471
><TD
472
WIDTH="33%"
473
ALIGN="right"
474
VALIGN="top"
475
>Previous License</TD
476
></TR
477
></TABLE
478
></DIV
479
></BODY
480
></HTML
481
>

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.