From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Philipp Zabel <p.zabel@pengutronix.de>, ptxdist@pengutronix.de
Cc: Alejandro Vazquez <avazquez.dev@gmail.com>
Subject: Re: [ptxdist] [PATCH v3] tf-a: new package for ARM trusted firmware A
Date: Tue, 25 Feb 2020 10:44:18 +0100 [thread overview]
Message-ID: <93a36c4f-0070-8e2c-1947-b64479cd1b5e@pengutronix.de> (raw)
In-Reply-To: <b7428f3ce8e0d897f37a3bbb6402cc74c81df393.camel@pengutronix.de>
Hello Philipp,
On 2/25/20 10:20 AM, Philipp Zabel wrote:
>> + Enter the TF-A git commitsh you want to build. Usally a tagged release
> ^ ^
> Some missing vowels here. Also, the git documentation uses spells it
> "commit-ish" [1], but in most places it just says "commit".
Will fix it. It is usually a tag, that's why I don't want it to say
"Enter the git commit".
> What about the other licenses listed in docs/licenses.rst, such as NCSA,
> and Zlib? Does any of this code make it into the TF-A binary?
hm. they are all compatible with BSD-3-Clause if only distributing:
BSD-3-Clause AND BSD-2-Clause AND NCSA AND Zlib
When patching some parts of the code, the patches need to be dually licensed,
thus:
BSD-3-Clause AND BSD-2-Clause AND NCSA AND Zlib AND MIT AND GPL-2.0
Is this ok?
>> +# TF_A_DEBUG=1
>
> Is this a leftover? I see no other packages with a commented out
> FOO_DEBUG=1 line.
It affects both the DEBUG=X make parameter and the build output directory.
I didn't want to hardcode both places. Would inverted logic with TF_A_RELEASE := 1
be more acceptable?
Cheers
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-02-25 9:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 10:42 Ahmad Fatoum
2020-02-25 7:31 ` Michael Tretter
2020-02-25 9:20 ` Philipp Zabel
2020-02-25 9:44 ` Ahmad Fatoum [this message]
2020-02-27 9:47 ` Roland Hieber
2020-02-27 10:56 ` Ahmad Fatoum
2020-02-25 9:44 ` Michael Olbrich
2020-02-25 10:35 ` Ahmad Fatoum
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=93a36c4f-0070-8e2c-1947-b64479cd1b5e@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=avazquez.dev@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.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