From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Warner Losh <imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>,
"devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: DTS license for non-linux use
Date: Wed, 18 May 2016 15:00:41 -0700 [thread overview]
Message-ID: <573CE609.2030007@gmail.com> (raw)
Warner Losh asked a question about the use of cpp #include in dts
source files, and while the topic of license of existing devicetree
source files in the linux source tree has a bearing on the question,
he adeptly tried to avoid stirring up a hornet's nest. Instead of
sidetracking his thread with license issues, this is a new thread
with my license question.
I'm sure I'll regret asking this, but what the heck.
The result of compiling a devicetree source file (.dts and .dtsi)
generates a .dtb file aka devicetree blob aka flattened device
tree (FDT). The FDT is a binary and ascii data structure that
contains no code. If the devicetree source file(s) license is
gpl, then it seems to me that the license of the blob is also
gpl.
If an operating system kernel "reads" an FDT, would that somehow
be a license, copyright, or other issue if the kernel was not also
gpl licensed?
My naive, "I'm not a lawyer", view is that there would not be
an issue, but my third hand impression is that the BSDs are
concerned that there may be an issue.
Are there any good authoritative sources that have addressed
this issue or a similar issue?
-Frank
next reply other threads:[~2016-05-18 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 22:00 Frank Rowand [this message]
[not found] ` <573CE609.2030007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-18 22:31 ` DTS license for non-linux use Warner Losh
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=573CE609.2030007@gmail.com \
--to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.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).