public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Retallack, Mark \(Siemens\)" <mark.retallack@siemens.com>
To: "C.J." <tsai.cj@msa.hinet.net>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Clean room module loader + GPL module + Application
Date: Wed, 25 May 2005 12:37:00 -0000	[thread overview]
Message-ID: <B573B0465A4EFB42997BADDC2FBDE1540948F9@ples506a.stcl.siemens.co.uk> (raw)

I am sure others will be able to answer this in a better way, but: 

First off, eCos is (now) GPL compatible. It has an exception for static
linking against a closed source application.

If any GPL source is introduced into the eCos+Applicaion mix, and it
does not have a similar exception, then the whole
eCos+Application+OtherApp mix will become GPL. The only way to prevent
this is to not statically link the OtherApp. This would require runtime
dynamic linking and a very careful development process.   

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of C.J.
Sent: 24 May 2005 18:47
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Clean room module loader + GPL module + Application


Hi,
I know eCos mod-GPL have been discussed several times.
I also understand that eCos is not GPL compatible --- 
Using GPL code in eCos kernel will force the license 
of eCos application GPL.

GNU GPL (http://www.gnu.org/copyleft/gpl.html) states:
   The source code for a work means the preferred form of the work for
making modifications to it. 
   For an executable work, complete source code means all the source
code for all modules it contains, 
   plus any associated interface definition files, plus the scripts used
to control compilation and 
   installation of the executable. 
   However, as a special exception, the source code distributed need 
   not include anything that is normally distributed (in either source
or binary form) with the major 
   components (compiler, kernel, and so on) of the operating system on
which the executable runs, 
   unless that component itself accompanies the executable. 

Considering only legal issues (just ignore any technical or code size
issue), 
If an eCos system is implemented like this:
(a) eCos kerenl (mod-GPL)
(b) Clean room module loader  (closed license)
(c) A GPL module registers itself as "/dev/storage" (GPL)
(d) Clean room application, mount  "/dev/storage" and use eCos POSIX
layer (via FAT filesystem) 
      to access the device (closed license).

Does the GPL "special exception" apply to this situation?
Is it legal If the provider do not release the source code of  (b) and
(d)?

Best Regards,
C.J.




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

             reply	other threads:[~2005-05-25  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 12:37 Retallack, Mark (Siemens) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25 12:26 Retallack, Mark (Siemens)
2005-05-25  6:57 [ECOS] redboot startup mode yrodguez
2005-05-25  7:50 ` [ECOS] Clean room module loader + GPL module + Application C.J.
2005-05-26 12:30   ` Bart Veer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B573B0465A4EFB42997BADDC2FBDE1540948F9@ples506a.stcl.siemens.co.uk \
    --to=mark.retallack@siemens.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=tsai.cj@msa.hinet.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).