[ECOS] ecos licensing FAQ queries

[ECOS] ecos licensing FAQ queries

[Butun Guang]

How do you define a LARGER WORK.
It's obvious that it covers the situation someone develops a
product on top of ecos. How about someone develops an
operating system, can he benefit from ecos packeges, i.g., just
includes or modifies one package (like just one device driver code),
and deliver within their product?

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com


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

Re: [ECOS] ecos licensing FAQ queries

[Bart Veer]

>>>>> "Butun" == Butun Guang <guangbutun@hotmail.com> writes:

    Butun> How do you define a LARGER WORK. It's obvious that it
    Butun> covers the situation someone develops a product on top of
    Butun> ecos. How about someone develops an operating system, can
    Butun> he benefit from ecos packeges, i.g., just includes or
    Butun> modifies one package (like just one device driver code),
    Butun> and deliver within their product?

Note: I am not a company lawyer so this response should be treated as
my personal opinion rather than an official position.

The RHEPL applies to the eCos source files individually, not to eCos
in its entirety. If you use one or more source files from any eCos
package, for example a device driver, with your application then the
terms of the RHEPL apply to that use. It does not matter whether or
not your application is a typical eCos application, built on top of
some eCos HAL and other packages.

Bart

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