Re: [ECOS] HD file system?

["Eric Verlind" <eric dot verlind at streamconcept dot be>]

Okay, that's important to realise.

Suppose my company has its own code S, which is containing the company's
patented IP, constituting the basis of the company's existence. With that we
make a product called P, which consists of a single, statically linked image
with eCos used as OS. How sure can I be that patents of my company relating
to S are not endangered?

What about modifications to the code of eCos itself. Suppose that we make
modifications to -for example- the scheduler and build in a special,
patented, scheduling scheme of our own. How secure would that be from
exposal?

Thanks,

Eric


----- Original Message -----
From: "Nick Garnett" <nickg at ecoscentric dot com>
To: "Eric Verlind" <eric dot verlind at streamconcept dot be>
Cc: <ecos-discuss at sources dot redhat dot com>
Sent: Saturday, March 01, 2003 11:42 AM
Subject: Re: [ECOS] HD file system?


> "Eric Verlind" <eric dot verlind at streamconcept dot be> writes:
>
> [Please keep the discussion on the ecos-discuss list so others may
> benefit from the mail exchange.]
>
> > Could you please elaborate on your statement about the license? Could we
> > take for instance the network driver for our pet Ethernet chip, which is
not
> > on the list of supported devices, from Linux and use it as a starting
point
> > for an eCos version?
> >
>
> Anything from Linux is pure GPL, eCos is GPL with an exception. The
> exception allows non-GPL code to be linked directly with eCos to make
> a single executable. Pure GPL does not allow that. Importing any GPL
> code into eCos would effectively nullify the exception, reverting it
> to pure GPL. We don't want that.
>
> Aside from that issue, eCos network drivers are very different from
> Linux ones, and there may not be very much code that could be used. I
> have certainly looked at Linux drivers in the past when the details of
> some controller were unclear from the documentation, but I have always
> been very careful not to just cut-n-paste code across.
>
> --
> Nick Garnett                    eCos Kernel Architect
> http://www.ecoscentric.com/     The eCos and RedBoot experts
>
>


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