From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/3] TI IPC: Fix License field.
Date: Thu, 24 Mar 2011 15:59:08 +0100 [thread overview]
Message-ID: <imfm7s$cd7$1@dough.gmane.org> (raw)
In-Reply-To: <1300974563.3795.29.camel@mattotaupa>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 24-03-11 14:49, Paul Menzel wrote:
> Am Donnerstag, den 24.03.2011, 18:31 +0530 schrieb Siddharth Heroor:
>> From: Siddharth Heroor <heroor@ti.com>
>>
>> * The correct license for TI IPC is BSD and not TI.
>
> Was the original license a mistake or was it relicensed?
The "LICENSE = TI" bit in the recipes is 90% a copy/paste from another
recipe. For most things we use BSD, but since that is a "fill in"
license I choose "TI" or "TI BSD" while I waited for the interna;
opensource review board to tell me which term to use. While waiting for
that the original recipes got copied a lot :)
A short rundown, not 100% accurate, but a good rule of thumb:
BSD: things that gets put into the codecserver or linked to by apps
GPLv2 or GPLv2+BSD: Kernel modules
"TI": compiler, various binary only IP, etc
Eclipse: XDC
And then we have distribution license "Technology Software Publically
Available" or TSPA which means you can download it without any login or
registration. This is not a source license.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNi1w8MkyGM64RGpERApIpAJ9HAxmnM01wjgmSvNfk9j7fl1ydqgCfSZAX
V1wHf3tSSrt/4eSXXYh3Mtk=
=IudE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-24 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 13:01 [PATCH 1/3] TI IPC: Fix License field Siddharth Heroor
2011-03-24 13:01 ` [PATCH 2/3] TI IPC: Add missing dependencies Siddharth Heroor
2011-03-24 13:01 ` [PATCH 3/3] TI IPC: Add version 1.22.04.25 Siddharth Heroor
2011-03-24 13:49 ` [PATCH 1/3] TI IPC: Fix License field Paul Menzel
2011-03-24 14:59 ` Koen Kooi [this message]
2011-03-24 17:55 ` Siddharth Heroor
2011-03-24 18:17 ` Koen Kooi
2011-03-25 11:08 ` Siddharth Heroor
2011-03-25 11:45 ` Koen Kooi
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='imfm7s$cd7$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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 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.