linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ben bodley <benb@m2tech.co.nz>
To: embedded list <linuxppc-embedded@lists.linuxppc.org>
Subject: grey area open-source issues..
Date: Fri, 01 Sep 2000 14:35:42 +1200	[thread overview]
Message-ID: <39AF15FE.3DDE5D49@m2tech.co.nz> (raw)


hello all,

i have a few questions regarding the publishing of linux kernel source
code.. i know its a little off topic, but i'm sure many developers here
will have experienced some sort of issues when it comes to a customer
paying for kernel development, and wanting to keep certain ip in-house..

the thing is, i have ported a lot of code over to linux, that has an
object only license (ie. we cannot give away the source code, but object
code is fine).. the linux kernel however is under the GPL license, and
having modified parts of it, i must make this code available publically
with the product..

the code i have ported has to be compiled into the kernel..

i can't give it away as i break one license, but break another if i dont
make it public..



what is the story here??, and is there exceptions for modules??

cheers for any insights,

ben

--
/\\------------------------------------------------------------------
ben.bodley/.m2technologyltd.nz/.benb@m2tech.co.nz/.64.9.4448307ext130


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-09-01  2:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-01  2:35 ben bodley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-01 10:26 grey area open-source issues kd

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=39AF15FE.3DDE5D49@m2tech.co.nz \
    --to=benb@m2tech.co.nz \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 NNTP newsgroup(s).