Searched refs:project (Results 1 – 25 of 34) sorted by relevance
12
| /trusted-firmware-a-latest/docs/process/ |
| D | maintenance.rst | 4 Trusted Firmware-A (TF-A) project follows the generic `trustedfirmware.org
6 TF-A project-specific decisions.
14 To be elligible to become a maintainer for TF-A project, all criteria outlined
17 - Being an active member of the project for at least a couple of years.
26 project at heart.
28 - Showing a strong will to improve the project and to do the right thing, rather
54 …intenance Process: https://developer.trustedfirmware.org/w/collaboration/project-maintenance-proce…
55 .. _here: https://developer.trustedfirmware.org/w/collaboration/project-maintenance-process/#how-to…
|
| D | code-review-guidelines.rst | 24 All contributions to Trusted Firmware-A project are reviewed by the community to
25 ensure they meet the project's expectations before they get merged, according to
51 the project should:
87 of the project maintainers for help.
89 - Do the right thing for the project, not the fastest thing to get code merged.
139 - It adheres to the security model of the project. In particular, it does not
222 type of code duplication hurts the maintainability of the project. The
245 .. _Project Maintenance Process: https://developer.trustedfirmware.org/w/collaboration/project-main…
|
| D | platform-ports-policy.rst | 12 library interfaces (like xlat_table library). The project will try to maintain
21 The project will generally not take into account downstream platforms. If those
|
| D | security.rst | 13 TF-A project's `mailing list`_.
79 .. _issue tracker: https://developer.trustedfirmware.org/project/board/1/
|
| D | contributing.rst | 29 - Ensure commits adhere to the the project's :ref:`Commit Style`.
32 contributing to a project.
65 information. Files that entirely consist of contributions to this project
118 project aspires to.
|
| D | coding-style.rst | 54 It is not possible for the project to follow all MISRA guidelines. We maintain
364 |TF-A| are *project* includes.
402 /* project header files */
|
| D | coding-guidelines.rst | 27 To assist with coding style compliance, the project Makefile contains two
29 source tree. The project also defines certain *checkpatch* options in the
480 project's maintainers and justified in the code.
502 reason, the TF-A project used to make heavy use of weak functions and there
|
| /trusted-firmware-a-latest/ |
| D | .gitreview | 4 project=TF-A/trusted-firmware-a
|
| D | dco.txt | 15 By making a contribution to this project, I certify that:
33 (d) I understand and agree that this project and the contribution
37 this project or the open source license(s) involved.
|
| D | .gitignore | 6 .project
|
| /trusted-firmware-a-latest/docs/ |
| D | conf.py | 15 project = "Trusted Firmware-A" variable
|
| D | license.rst | 5 this project are accepted under the same license with developer sign-off as
53 This project contains code from other projects as listed below. The original
61 (GPL-2.0+ OR BSD-2-Clause). It is used by this project under the terms of
66 (NCSA OR MIT). It is used by this project under the terms of the NCSA
75 (GPL-2.0+ OR BSD-3-Clause). It is used by this project under the terms of the
|
| D | index.rst | 59 some information on the project and how it is organized.
64 The **Processes & Policies** chapter explains the project's release schedule
66 contributing to the project (including the coding style).
|
| /trusted-firmware-a-latest/docs/about/ |
| D | contact.rst | 14 Public mailing lists for TF-A and the wider Trusted Firmware project are
17 in technical or organizational discussions around the project. These discussions
20 The relevant lists for the TF-A project are:
|
| D | release-information.rst | 7 The project currently aims to do a release once every 6 months which will be
44 depending on project requirement and partner feedback.
76 cataloging all the deprecated interfaces in TF-A project and the Release version
93 cataloging all the deprecated drivers in TF-A project and the Release version
|
| /trusted-firmware-a-latest/docs/getting_started/ |
| D | docs-build.rst | 58 HTML-formatted pages from the project root directory by running:
70 directory of the project, run the following command to see the supported
101 from inside the project's virtual environment. The easiest way to activate this
104 Running ``poetry shell`` from the directory containing this project, activates
124 from project root directory
|
| /trusted-firmware-a-latest/docs/threat_model/ |
| D | index.rst | 10 documents which, together, form the project's threat model. These are
22 features within the project, we have not reached that point yet. We expect
|
| D | threat_model_rss_interface.rst | 17 firmware project in the future.
|
| /trusted-firmware-a-latest/docs/security_advisories/ |
| D | security-advisory-tfv-7.rst | 31 At the time of writing, the TF-A project is not aware of a Variant 4 exploit
37 (SDEI)`_. Also, the TF-A project does not have visibility of all
38 vendor-supplied interfaces. Therefore, the TF-A project takes a conservative
101 .. _Google Project Zero: https://bugs.chromium.org/p/project-zero/issues/detail?id=1528
|
| /trusted-firmware-a-latest/plat/mediatek/build_helpers/ |
| D | mtk_build_helpers.mk | 102 MTK_PROJECT_CFG := $(MTK_PLAT)/project/$(PLAT)/project_config.mk
|
| /trusted-firmware-a-latest/docs/design_documents/ |
| D | cmake_framework.rst | 33 * Host and target system agnostic project.
34 * CMake project is scalable, supports project modularization.
36 * Out-of-the-box support for integration with several tools (e.g. project
|
| /trusted-firmware-a-latest/docs/plat/arm/morello/ |
| D | index.rst | 8 Capability architecture specific changes will be added `here <https://git.morello-project.org/morel…
|
| /trusted-firmware-a-latest/docs/plat/marvell/armada/ |
| D | build.rst | 4 This section describes how to compile the Trusted Firmware-A (TF-A) project for Marvell's platforms.
22 For example: if U-Boot project (and its images) is located at ``~/project/u-boot``,
23 BL33 should be ``~/project/u-boot/u-boot.bin``
286 CZ.NIC as part of Turris project released free and open source WTMI
|
| D | uart-booting.rst | 4 This section describes how to temporary boot the Trusted Firmware-A (TF-A) project over UART
|
| /trusted-firmware-a-latest/docs/plat/ |
| D | socionext-uniphier.rst | 65 procedure of U-Boot, refer to the document in the `U-Boot`_ project.
|
12
