| /openbmc/openbmc/meta-arm/meta-arm-systemready/ |
| H A D | README.md | 4 [Arm SystemReady][] validation on the supported machines.
13 * Building the firmware for the [Arm SystemReady][] certification program
14 * Running [Arm SystemReady ACS][] (Architecture Compliance Suite) tests
20 layer to build the firmware, run the [Arm SystemReady IR][] ACS tests, and
39 There are two additional recipes for generating the Arm SystemReady ACS tests
41 [Arm SystemReady scripts][]. These packages are installed in the
46 the Arm SystemReady ACS prebuilt image and set up the `testimage` environment.
51 Parser to create a results.md file, then running the Arm SystemReady result
71 Arm SystemReady has four bands:
72 * [Arm SystemReady SR][]
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | index.rst | 2 # Copyright (c) 2022, 2024, Arm Limited.
7 Arm Corstone-1000
14 Arm reference solutions are Arm public example software projects that track and
16 published over time. Arm partners are responsible for ensuring that the
18 deploy a product derived from Arm reference solutions.
|
| /openbmc/openbmc/meta-arm/meta-arm-toolchain/ |
| H A D | README.md | 4 This layer contains recipes for the prebuilt GNU Arm toolchains.
9 Recipes for pre-built GNU Arm toolchain for Linux development are provided under
16 from the Arm Cortex-A family and implementing the Arm A-profile architecture.
21 In order to use any of pre-built Arm toolchain versions (8.2, 8.3, 9.2 and so
45 Arm A-profile architecture.
73 Pre-built Arm toolchain for bare-metal development
76 Recipes for pre-built GNU Arm toolchain for bare-metal development are provided
82 This recipe provides support for pre-built GNU Arm Embedded toolchain for
83 bare-metal software development on devices based on 32-bit Arm Cortex-A,
91 This recipe provides support for pre-built GNU Arm toolchain for bare-metal
[all …]
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | mps2.rst | 1 Arm MPS2 and MPS3 boards (``mps2-an385``, ``mps2-an386``, ``mps2-an500``, ``mps2-an505``, ``mps2-an…
4 These board models use Arm M-profile or R-profile CPUs.
6 The Arm MPS2, MPS2+ and MPS3 dev boards are FPGA based (the 2+ has a
19 Cortex-M3 as documented in Arm Application Note AN385
21 Cortex-M4 as documented in Arm Application Note AN386
23 Cortex-M7 as documented in Arm Application Note AN500
25 Cortex-M33 as documented in Arm Application Note AN505
27 Cortex-M3 'DesignStart' as documented in Arm Application Note AN511
29 Dual Cortex-M33 as documented in Arm Application Note AN521
31 Dual Cortex-M33 on an MPS3, as documented in Arm Application Note AN524
[all …]
|
| H A D | realview.rst | 1 Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``, ``realview-pb-a8``, ``realview-pbx-a9…
4 Several variants of the Arm RealView baseboard are emulated, including
17 - Arm AMBA Generic/Distributed Interrupt Controller
|
| H A D | integratorcp.rst | 1 Arm Integrator/CP (``integratorcp``)
4 The Arm Integrator/CP board is emulated with the following devices:
|
| H A D | xlnx-zcu102.rst | 14 Arm Security Extensions (TrustZone). The default is ``off``.
18 Arm Virtualization Extensions. The default is ``off``.
|
| H A D | musca.rst | 1 Arm Musca boards (``musca-a``, ``musca-b1``)
4 The Arm Musca development boards are a reference implementation
|
| /openbmc/qemu/docs/system/ |
| H A D | target-arm.rst | 3 Arm System emulator
6 QEMU can emulate both 32-bit and 64-bit Arm CPUs. Use the
7 ``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
9 to simulate a 32-bit Arm machine: in general, command lines that
13 QEMU has generally good support for Arm guests. It has support for
15 Arm hardware is much more widely varying than x86 hardware. Arm CPUs
20 small fraction of the Arm hardware ecosystem.
22 The situation for 64-bit Arm is fairly similar, except that we don't
35 For QEMU's Arm system emulation, you must specify which board
39 Because Arm systems differ so much and in fundamental ways, typically
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | fix-armv5.patch | 5 Subject: [PATCH] [3.13] gh-125444: Fix illegal instruction for older Arm
11 On Arm v5 it is not possible to get the thread ID via c13 register
13 thread ID since Arm v6K architecture variant. Other variants of
14 Arm v6 (T2, Z and base) don’t provide the thread ID via c13.
16 consider that instructions for Arm v7 only.
65 +Fix illegal instruction for older Arm architectures. Patch by Diego Russo, testing by Ross Burton.
|
| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 3 Arm takes security issues seriously and welcomes feedback from researchers and
42 Arm reference solutions are Arm public example software projects that track and
44 published over time. Arm partners are responsible for ensuring that the
46 deploy a product derived from Arm reference solutions.
|
| H A D | README.md | 3 This repository contains the Arm layers for OpenEmbedded.
7 …This layer contains general recipes for the Arm architecture, such as firmware, FVPs, and Arm-spec…
11 …This layer contains machines for Arm reference platforms, for example FVP Base, Corstone1000, and …
15 …This layer contains recipes for Arm's binary toolchains (GCC and Clang for -A and -M), and a recip…
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/arm-platforms-kmeta/bsp/arm-platforms/ |
| H A D | README.md | 1 Arm platforms BSPs
4 This directory contains Arm platforms definitions and configuration for Linux.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs/ |
| H A D | 0004-v8-don-t-override-ARM-CFLAGS.patch | 39 - # Host built with an Arm CXX compiler.
64 # Host not built with an Arm CXX compiler (simulator build).
72 - # Target built with an Arm CXX compiler.
97 # Target not built with an Arm CXX compiler (simulator build).
|
| /openbmc/openbmc/meta-arm/meta-arm-toolchain/conf/distro/include/ |
| H A D | external-arm-toolchain-versions.inc | 20 bb.error('Failed to obtain external Arm toolchain version: %s' % exc)
31 if version.split()[4] == '(Arm':
32 # gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)
42 bb.error('Failed to parse external Arm toolchain version from: %s' % version)
70 bb.error('Failed to obtain external Arm libc version: %s' % exc)
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-devtools/fvp/ |
| H A D | fvp-common.inc | 3 LICENSE_FLAGS = "Arm-FVP-EULA"
6 # FVP has an End User License Agreement. Add Arm-FVP-EULA to
10 LICENSE_FLAGS_ACCEPTED:append = " ${@oe.utils.vartrue('ARM_FVP_EULA_ACCEPT', 'Arm-FVP-EULA', '', d)…
12 LICENSE_FLAGS_DETAILS[Arm-FVP-EULA] = " \
|
| H A D | fvp-ecosystem.inc | 8 SUMMARY = "Arm Fixed Virtual Platform - ${MODEL} Ecosystem Reference Design"
11 SRC_URI = "https://developer.arm.com/-/media/Arm%20Developer%20Community/Downloads/OSS/FVP/${MODEL}…
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | arm-acpi.rst | 2 ACPI on Arm systems
6 the BSA (Arm Base System Architecture) [0] and BBR (Arm
9 Arm Servers, in addition to being BSA compliant, comply with a set
12 The Arm kernel implements the reduced hardware model of ACPI version
18 If an Arm system does not meet the requirements of the BSA and BBR,
23 industry-standard Arm systems, they also apply to more than one operating
25 ACPI and Linux only, on an Arm system -- that is, what Linux expects of
29 Why ACPI on Arm?
35 reasoning behind ACPI on Arm systems. Actually, we snitch a good portion
38 The short form of the rationale for ACPI on Arm is:
[all …]
|
| /openbmc/linux/drivers/acpi/arm64/ |
| H A D | Kconfig | 13 bool "Arm Generic Diagnostic Dump and Reset Device Interface"
16 Arm Generic Diagnostic Dump and Reset Device Interface (AGDI) is
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/files/corstone1000/ |
| H A D | 0003-dt-bindings-remoteproc-Add-Arm-remoteproc.patch | 4 Subject: [PATCH 3/6] dt-bindings: remoteproc: Add Arm remoteproc
6 introduce the bindings for Arm remoteproc support.
28 +title: Arm Remoteproc Devices
34 + Some Arm heterogeneous System-On-Chips feature remote processors that can
|
| H A D | 0001-remoteproc-Add-Arm-remoteproc-driver.patch | 4 Subject: [PATCH 1/6] remoteproc: Add Arm remoteproc driver
6 introduce remoteproc support for Arm remote processors
56 + tristate "Arm remoteproc support"
60 + Say y here to support Arm remote processors via the remote
93 + * Copyright 2024 Arm Limited and/or its affiliates <open-source-office@arm.com>
123 + * struct arm_rproc_dcfg - Arm remote processor configuration
133 + * struct arm_rproc - Arm remote processor instance
144 +/* Definitions for Arm Corstone-1000 External System */
484 +MODULE_DESCRIPTION("Arm Remote Processor Control Driver");
|
| /openbmc/linux/drivers/firmware/arm_ffa/ |
| H A D | Kconfig | 3 tristate "Arm Firmware Framework for Armv8-A"
8 This Firmware Framework(FF) for Arm A-profile processors describes
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/dynamic-layers/meta-arm-systemready/recipes-test/arm-systemready-acs/files/fvp-base/ |
| H A D | report.txt | 3 - Arm SystemReady Band: IR
11 - Company: Arm
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/ |
| H A D | linux-arm-platforms.inc | 14 # Arm platforms kmeta
44 file://0001-remoteproc-Add-Arm-remoteproc-driver.patch \
46 file://0003-dt-bindings-remoteproc-Add-Arm-remoteproc.patch \
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/ |
| H A D | 0001-Add-stub-capsule-update-service-components.patch | 42 + * Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
72 + * Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
213 + * Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
270 +# Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
320 + * Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
339 + * Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
362 + * Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.
|