Home
last modified time | relevance | path

Searched refs:project (Results 1 – 25 of 39) sorted by relevance

12

/rk3399_ARM-atf/docs/process/
H A Dmaintenance.rst4 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
H A Dcode-review-guidelines.rst24 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
H A Dplatform-ports-policy.rst12 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
H A Dcontributing.rst33 - Ensure commits adhere to the project's :ref:`Commit Style`.
36 contributing to a project.
69 information. Files that entirely consist of contributions to this project
104 submission rules specifically for the TF-A project.
130 project aspires to.
191 The TF-A project makes use of `Coverity Scan` for static analysis, a service
H A Dsecurity.rst13 TF-A project's `mailing list`_.
/rk3399_ARM-atf/docs/
H A Dlicense.rst5 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
88 - Some source files originating from the `Open Profile for DICE`_ project.
96 - Some source files originating from the `pydevicetree`_ project.
113 - Some source files originating from the `edk2`_ project.
122 - Some source files originating from the `mbed OS`_ project.
136 .. _pydevicetree: https://pypi.org/project/pydevicetree/
H A Dconf.py15 project = "Trusted Firmware-A" variable
H A Dindex.rst60 some information on the project and how it is organized.
65 The **Processes & Policies** chapter explains the project's release schedule
67 contributing to the project (including the coding style).
/rk3399_ARM-atf/
H A Ddco.txt15 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.
H A D.gitreview4 project=TF-A/trusted-firmware-a
H A D.gitignore6 .project
/rk3399_ARM-atf/docs/about/
H A Dcontact.rst14 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:
H A Drelease-information.rst7 The project currently aims to do a release once every 6 months which will be
44 depending on project requirement and partner feedback.
86 cataloging all the deprecated interfaces in TF-A project and the Release version
101 cataloging all the deprecated drivers in TF-A project and the Release version
/rk3399_ARM-atf/docs/getting_started/
H A Ddocs-build.rst40 The documentation can be compiled into HTML-formatted pages from the project
53 directory of the project, run the following command to see the supported
84 run``, which runs the specified command within the project's virtual
88 Running ``poetry shell`` from the directory containing this project, activates
108 from project root directory
H A Dprerequisites.rst76 Please refer to the OpenSSL project documentation for more information.
192 within the main project while maintaining their own commit history.
209 If the project updates the reference to a submodule (e.g., points to a new
/rk3399_ARM-atf/tools/cot_dt2c/
H A D.gitignore111 # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
116 # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
135 # Spyder project settings
139 # Rope project settings
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dindex.rst7 documents which, together, form the project's threat model. These are
19 features within the project, we have not reached that point yet. We expect
H A Dthreat_model_rse_interface.rst17 firmware project in the future.
/rk3399_ARM-atf/docs/security_advisories/
H A Dsecurity-advisory-tfv-7.rst33 At the time of writing, the TF-A project is not aware of a Variant 4 exploit
39 (SDEI)`_. Also, the TF-A project does not have visibility of all
40 vendor-supplied interfaces. Therefore, the TF-A project takes a conservative
103 .. _Google Project Zero: https://bugs.chromium.org/p/project-zero/issues/detail?id=1528
/rk3399_ARM-atf/plat/mediatek/build_helpers/
H A Dmtk_build_helpers.mk92 MTK_PROJECT_CFG := $(MTK_PLAT)/project/$(PLAT)/project_config.mk
/rk3399_ARM-atf/docs/design_documents/
H A Dcmake_framework.rst29 * Host and target system agnostic project.
30 * CMake project is scalable, supports project modularization.
32 * Out-of-the-box support for integration with several tools (e.g. project
/rk3399_ARM-atf/docs/threat_model/
H A Dsupply_chain_threat_model.rst9 software product (open-source project). These include:
11 - Malicious code commits: This attack directly injects code into a project
16 project through other piece of code or packages the project depends on. This
26 TF-A project.
31 Figure 1 shows the different software components surrounding the TF-A project.
49 compiler infrastructure project [3]_. We import the builtins library which
115 - *EDK2 UEFI*: Normal world bootloader from the EDK2 project [7]_. We use EDK2
124 The TF-A project uses several tools to build, analyze and test the TF-A source
267 | Threat and | | According to the TF project maintenance process [10]_, |
270 | | include being an active member of the project for a |
[all …]
/rk3399_ARM-atf/docs/plat/arm/morello/
H A Dindex.rst8 Capability architecture specific changes will be added `here <https://git.morello-project.org/morel…
/rk3399_ARM-atf/docs/components/
H A Drealm-management-extension.rst113 Additionally, the TF-RMM project documentation has the specific `Shrinkwrap guide`_.
117 and test suite originates from TF-a-tests project.
/rk3399_ARM-atf/docs/plat/marvell/armada/
H A Dbuild.rst4 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

12