From: Marc Leeman <marc.leeman@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] GPL Licensing issues
Date: Mon, 27 Sep 2004 08:27:17 +0200 [thread overview]
Message-ID: <1f729c4804092623274a63a453@mail.gmail.com> (raw)
In-Reply-To: <6.1.1.1.0.20040926174406.01e1d130@wheresmymailserver.com>
> The files in the examples directory - since everything needs to be linked
> to u-boot to work, and u-boot is released under the GPL, does that mean
> that custom user applications are also under the GPL - or do you use
> Linus's relationship of kernel/application separation?
Didn't linux say that linking involves using the GPL. I remember a
discussion about this very topic a couple of months ago on the lkml
(about the nvidia modules).
As far as I am concerned, including GPL header files makes your
application GPL (since you implicitly verbatim copy code).
This being said, I have problems convincing collegues who are
convinced that they write a piece of 'original' code and don't want to
make it public...
--
ash nazg durbatul?k, ash nazg gimbatul,
ash nazg thrakatul?k agh burzum-ishi krimpatul
next prev parent reply other threads:[~2004-09-27 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 20:29 [U-Boot-Users] U-Boot not responding back to ARP requests? Robin Getz
2004-09-26 22:47 ` Wolfgang Denk
2004-09-27 0:54 ` [U-Boot-Users] GPL Licensing issues Robin Getz
2004-09-27 6:27 ` Marc Leeman [this message]
2004-09-27 7:28 ` Wolfgang Denk
2004-09-27 8:24 ` Marc Leeman
2004-09-27 10:29 ` Marius Groeger
2004-09-27 11:12 ` Marc Leeman
2004-09-27 12:40 ` Doug Kehn
2004-09-27 20:20 ` Wolfgang Denk
2004-09-27 7:22 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 8:04 Robin Getz
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=1f729c4804092623274a63a453@mail.gmail.com \
--to=marc.leeman@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.