* [ECOS] Re: ecos license question.
@ 2003-01-27 7:49 Jonathan Larmour
0 siblings, 0 replies; only message in thread
From: Jonathan Larmour @ 2003-01-27 7:49 UTC (permalink / raw)
To: jake smith; +Cc: eCos discussion
> We are developing a commercial product using eCos (x86
> platform). We have made the following changes to the
> eCos .
> 1. We have Modified eCos serial driver for BREAK
> support.
> 2. Added custom keypad driver package to the eCos. No
> eCos files are modified.
>
> Do we need to make our product Open Source ?
>
> We have also used redboot IDE source code in the
> application software.
>
> Do we need to release full or part of the
> application code ?
http://sources.redhat.com/ecos/license-overview.html has the best summary.
You are only obliged to release the eCos (and RedBoot) source code - you
can either do it directly to the people you are giving the binaries to *as
long as you put it alongside the binaries*, or you can make it available
to all. Read the overview :-).
BTW, there is already break support in the serial driver, it's just the
API isn't well documented :-|. See
devs/serial/generic/16x5x/current/src/ser_16x5x.c and search for
CYGNUM_SERIAL_STATUS_BREAK. How did you do it?
Jifl
--
eCosCentric http://www.eCosCentric.com/ <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-01-27 4:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-27 7:49 [ECOS] Re: ecos license question Jonathan Larmour
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).