From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Licensing Question on ARM Semihosting Code
Date: Fri, 28 Feb 2014 13:49:19 -0500 [thread overview]
Message-ID: <5310DA2F.9030106@ti.com> (raw)
In-Reply-To: <5310D2EA.4040607@broadcom.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/28/2014 01:18 PM, Darwin Rambo wrote:
> Given the ARM header below, is this code possible to put into
> u-boot?
>
> For reference, I see this discussion below.
> http://lists.denx.de/pipermail/u-boot/2011-November/110884.html
>
> If this is not acceptable, presumably due to the "All rights
> reserved" and "Redistribution in binary form..." clauses below, we
> could try to find an alternative implementation that is GPL2.0+
> licensed or rewrite the parts we need from scratch.
>
> Any suggestions you have would be most welcome. Thanks.
So, that particular discussion was about fastboot, and in that
particular case everything is OK, in the long run (I poked TI's
lawyers about that). We're just missing a clean design version being
ported and I know of a few groups / companies leaning on another
entity to do so.
But with your particular quoted header, I think we cannot use it as it
puts restrictions on the binary redistribution as well.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTENovAAoJENk4IS6UOR1WuUYP/RukZAEnPLM4IEEIMpa9tAir
J7FUa+zIJKerQfNQ+rrW5/sWGG2Zj/1A8twjcs7W8KXrbbaQEr+jpQRPspS3pa5q
bmfeBDclNpuwqXtzeQvm6eNWVbkq0+4fJ25AI7fL1EuhpGFmcPfXoAW4DOFBJBUW
B11BHzHO1PuWl+7fm5PLBT/kMjB8rv8gx6rhyNxp0f3/aN+U4GkSNvVBXo8cBOWm
4gO2dqWM299e3x2GYVKBbYwbAydBXXOjwpa3VoGljJPiz5iBT1DrMJV9R37kTRkj
D07PUlV2aMNdZv+dNxV1FOce/bhcT8iRWyzUSlecPrNWDWp7nFaIaGBpDHh8iRKA
thB7LlT1hQI88ksQH923CBaa2N1N/HgYtXYSiwRXx8bQexLIBieCvfUsHxqtWKRQ
r+bf3febP0MYiU5BCHKHHpY3zfERGRIVmgAs/7khtm038ORAIxWLX7myvQyubfBz
jRbwkZfpR1UXQ8g6zcbRah9mB12foVURF8a67v+9JC7p4/Jrrjb3ARgw8LwA61de
kiqjUr3qDfEcow9KTxZPVFi5gLJXTSdMPzgrs/2cCJ2jFnN/olGd//eGaIZUzf6P
7L2oOEwv2i7p4FwwciTGhQWCfLO3YzU0MHnFJsHu+NaDdUxhpf/X/zwcAHvQqrc+
L6bmYpnta9ViVwJHzOSS
=Si6y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-28 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:18 [U-Boot] Licensing Question on ARM Semihosting Code Darwin Rambo
2014-02-28 18:49 ` Tom Rini [this message]
2014-03-06 20:43 ` Darwin Rambo
2014-03-06 20:47 ` Tom Rini
2014-02-28 20:55 ` Måns Rullgård
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=5310DA2F.9030106@ti.com \
--to=trini@ti.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.