Searched refs:project (Results 1 – 25 of 31) sorted by relevance
12
| /arm-trusted-firmware-2.8.0/ |
| A D | .gitreview | 4 project=TF-A/trusted-firmware-a
|
| 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.
|
| A D | .gitignore | 6 .project
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | conf.py | 16 project = 'Trusted Firmware-A' variable
|
| A 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
|
| A D | index.rst | 57 some information on the project and how it is organized.
62 The **Processes & Policies** chapter explains the project's release schedule
64 contributing to the project (including the coding style).
|
| /arm-trusted-firmware-2.8.0/docs/about/ |
| A 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:
|
| A D | release-information.rst | 7 The project currently aims to do a release once every 6 months which will be
32 depending on project requirement and partner feedback.
62 cataloging all the deprecated interfaces in TF-A project and the Release version
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | docs-build.rst | 56 Documents can be built into HTML-formatted pages from project root directory by
70 directory of the project, run the following command to see the supported
72 the command is run from the project root directory, as that would invoke the
87 from project root directory
|
| A D | tools-build.rst | 25 project. Examples below show how to build a FIP file for FVP, packaging TF-A
|
| A D | prerequisites.rst | 69 Please refer to the OpenSSL project documentation for more information.
|
| A D | image-terminology.rst | 5 images referred to in the Trusted Firmware project.
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | security.rst | 13 issues in the project's `issue tracker`_ with the ``security-advisory`` tag. You
15 project at https://developer.trustedfirmware.org/.
73 .. _issue tracker: https://developer.trustedfirmware.org/project/board/1/
|
| A D | code-review-guidelines.rst | 4 This document provides TF-A specific details about the project's code review
30 the project should:
66 of the project maintainers for help.
68 - Do the right thing for the project, not the fastest thing to get code merged.
110 - It adheres to the security model of the project. In particular, it does not
193 type of code duplication hurts the maintainability of the project. The
216 .. _Project Maintenance Process: https://developer.trustedfirmware.org/w/collaboration/project-main…
|
| A D | platform-ports-policy.rst | 12 library interfaces (like xlat_table library). The project will try to maintain
|
| A 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.
|
| A D | commit-style.rst | 152 .. _issue: https://developer.trustedfirmware.org/project/board/1/
|
| A 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.
|
| /arm-trusted-firmware-2.8.0/docs/security_advisories/ |
| A 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
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/morello/ |
| A D | index.rst | 8 Capability architecture specific changes will be added `here <https://git.morello-project.org/morel…
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A 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
|
| /arm-trusted-firmware-2.8.0/plat/mediatek/build_helpers/ |
| A D | mtk_build_helpers.mk | 127 MTK_PROJECT_CFG := $(MTK_PLAT)/project/$(PLAT)/project_config.mk
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A 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
|
| A D | uart-booting.rst | 4 This section describes how to temporary boot the Trusted Firmware-A (TF-A) project over UART
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | socionext-uniphier.rst | 65 procedure of U-Boot, refer to the document in the `U-Boot`_ project.
|
Completed in 30 milliseconds
12