From: William Zhang <william.zhang@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot standalone application license question
Date: Thu, 1 Aug 2019 16:12:20 -0700 [thread overview]
Message-ID: <58471ccbc8487faec4b1c4afb537cc5d@mail.gmail.com> (raw)
Hi,
We are looking at the standalone application support in u-boot and we feel
it will be a good fit for our DDR initialization code that includes a
library that we have no right to distribute in source. But we have some
questions in regards to the GPL license exception here:
https://gitlab.denx.de/u-boot/u-boot/blob/master/Licenses/Exceptions
GPL License Exception:
Even though U-Boot in general is covered by the GPL-2.0/GPL-2.0+,
this does *not* cover the so-called "standalone" applications that
use U-Boot services by means of the jump table provided by U-Boot
exactly for this purpose - this is merely considered normal use of
U-Boot, and does *not* fall under the heading of "derived work".
The header files "include/image.h" and "arch/*/include/asm/u-boot.h"
define interfaces to U-Boot. Including these (unmodified) header
files in another file is considered normal use of U-Boot, and does
*not* fall under the heading of "derived work".
-- Wolfgang Denk
Looking at the standalone examples/hello_world.c, it now includes
common.h(gpl license header) and exports.h(no license header). Same to
the stub.c(with compiler.h in addition) which is required to build
standalone app. Would that still consider OK and be exempted from GPL
license if we follow this example and include both common.h, exports.h and
stub.c in our standalone code?
Thanks in advance for any feedbacks and comments!
Regards,
William
reply other threads:[~2019-08-01 23:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=58471ccbc8487faec4b1c4afb537cc5d@mail.gmail.com \
--to=william.zhang@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox