This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: ecos license and driver code


You can find the answers to most of your questions here, I think:

http://ecos.sourceware.org/license-overview.html

In general (not based on a law degree), you would not have to release your
driver code, or .h files, if you developed the code on your own not
deriving it from eCos source code.

I believe if you modify eCos code, you would have to releae it to the eCos
community via the maintainers.

--Anthony

>>>>>>>>>>>>>>>>>>>>>

Hi,
 
I am new to ecos. At this point, we are thinking about
if the ecos license will force us to release the
source code of our own driver for our own chips.
 
We are develeping a platform (a board) with mips and
other chips of our own. We need to port all our
drivers to ecos to release to our customer. 
 
Can someone please confirm that we have no obligation
to release our driver code including .h files to the
open community?
 
The other less critical question is: if we modified
the source code for the core system, are we supposed
to release the changes to the ecos maintainer?
 
Thanks very much for your input.
 
Regards,
Jason


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]