Home
last modified time | relevance | path

Searched +full:arm +full:- +full:firmware +full:- +full:suite (Results 1 – 25 of 41) sorted by relevance

12

/openbmc/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Darm,arm-firmware-suite.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/arm,arm-firmware-suite.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ARM Firmware Suite (AFS) Partitions
10 - Linus Walleij <linus.walleij@linaro.org>
15 The ARM Firmware Suite is a flash partitioning system found on the
16 ARM reference designs: Integrator AP, Integrator CP, Versatile AB,
21 const: arm,arm-firmware-suite
26 - |
[all …]
H A Dpartitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - Miquel Raynal <miquel.raynal@bootlin.com>
17 - $ref: arm,arm-firmware-suite.yaml
18 - $ref: brcm,bcm4908-partitions.yaml
19 - $ref: brcm,bcm947xx-cfe-partitions.yaml
20 - $ref: fixed-partitions.yaml
21 - $ref: linksys,ns-partitions.yaml
22 - $ref: qcom,smem-part.yaml
[all …]
/openbmc/openbmc/meta-arm/meta-arm-systemready/
H A DREADME.md1 # meta-arm-systemready Yocto Layer
4 [Arm SystemReady][] validation on the supported machines.
7 top-level meta-arm [README.md](../README.md) file.
13 * Building the firmware for the [Arm SystemReady][] certification program
14 * Running [Arm SystemReady ACS][] (Architecture Compliance Suite) tests
18 [`meta-arm-bsp`][] layer in the top-level meta-arm defines the
19 [`fvp-base`][] machine, which can be used with the recipes provided by this
20 layer to build the firmware, run the [Arm SystemReady IR][] ACS tests, and
24 ### Firmware Build
26 The `arm-systemready-firmware.bb` recipe is to build the firmware. It requires
[all …]
/openbmc/linux/drivers/mtd/parsers/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
24 tristate "Broadcom's U-Boot partition parser"
27 Broadcom uses a custom way of storing U-Boot environment variables.
28 They are placed inside U-Boot partition itself at unspecified offset.
49 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
51 <mtd-id> := unique id used in mapping driver/device
52 <size> := standard linux memsize OR "-" to denote all
62 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
63 mtdparts=sa1100:-
65 Same flash, but 2 named partitions, the first one being read-only:
[all …]
H A Dafs.c1 // SPDX-License-Identifier: GPL-2.0-or-later
4 drivers/mtd/afs.c: ARM Flash Layout/Partitioning
6 Copyright © 2000 ARM Limited
10 This is access code for flashes using ARM's flash partitioning
34 u32 type; /* Area type: ARM Image, SIB, customer */
47 u32 headerType; /* AIF, RLF, s-record etc. */
56 while (num--) in word_sum()
81 u_int ptr = off + mtd->erasesize - 12; in afs_is_v1()
101 u_int ptr = off + mtd->erasesize - 8; in afs_is_v2()
140 mask = mtd->size - 1; in afs_parse_v1_partition()
[all …]
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-m/
H A Dtrusted-firmware-m.inc1 # SPDX-License-Identifier: MIT
3 # Copyright (c) 2020 Arm Limited
6 SUMMARY = "Trusted Firmware for Cortex-M"
7 DESCRIPTION = "Trusted Firmware-M"
8 HOMEPAGE = "https://git.trustedfirmware.org/trusted-firmware-m.git"
9 PROVIDES = "virtual/trusted-firmware-m"
11 UPSTREAM_CHECK_GITTAGREGEX = "^TF-Mv(?P<pver>\d+(\.\d+)+)$"
15 # cmake here. You can easily short-circuit the toolchain but the install
25 # At present, TF-M Select other GNU Arm compiler versions instead of 11.2:
26 # https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/getting_started/tfm_getting…
[all …]
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/uefi/
H A Dsbsa-acs_7.1.4.bb1 require recipes-bsp/uefi/edk2-firmware_202408.bb
4 LICENSE += "& Apache-2.0"
5 LIC_FILES_CHKSUM += "file://ShellPkg/Application/sbsa-acs/LICENSE.md;md5=2a944942e1496af1886903d274…
7 SRC_URI += "git://github.com/ARM-software/sbsa-acs;destsuffix=edk2/ShellPkg/Application/sbsa-acs;pr…
8 …git://github.com/tianocore/edk2-libc;destsuffix=edk2/edk2-libc;protocol=https;branch=master;name=l…
9 file://0001-Patch-in-the-paths-to-the-SBSA-test-suite.patch \
10 file://0002-Enforce-using-good-old-BFD-linker.patch \
16 UPSTREAM_CHECK_URI = "https://github.com/ARM-software/sbsa-acs/releases"
18 COMPATIBLE_HOST = "aarch64.*-linux"
24 EDK2_EXTRA_BUILD = "--module ShellPkg/Application/sbsa-acs/uefi_app/SbsaAvs.inf"
[all …]
/openbmc/linux/drivers/firmware/arm_scmi/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "ARM System Control and Management Interface Protocol"
5 tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
6 depends on ARM || ARM64 || COMPILE_TEST
8 ARM System Control and Management Interface (SCMI) protocol is a
9 set of operating system-independent software interfaces that are
11 interfaces for: Discovery and self-description of the interfaces
13 a given device or domain into the various power-saving states that
55 operate normally, thing which could make an SCMI test suite using the
86 If you want the ARM SCMI PROTOCOL stack to include support for a
[all …]
/openbmc/linux/arch/arm/boot/dts/arm/
H A Darm-realview-eb.dtsi23 #include <dt-bindings/interrupt-controller/irq.h>
24 #include <dt-bindings/gpio/gpio.h>
27 #address-cells = <1>;
28 #size-cells = <1>;
29 compatible = "arm,realview-eb";
49 compatible = "regulator-fixed";
50 regulator-name = "vmmc";
51 regulator-min-microvolt = <3300000>;
52 regulator-max-microvolt = <3300000>;
53 regulator-boot-on;
[all …]
H A Dintegrator.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * SoC core Device Tree for the ARM Integrator platforms
7 #address-cells = <1>;
8 #size-cells = <1>;
15 core-module@10000000 {
16 compatible = "arm,core-module-integrator", "syscon", "simple-mfd";
19 #address-cells = <1>;
20 #size-cells = <1>;
24 compatible = "register-bit-led";
29 linux,default-trigger = "cpu0";
[all …]
H A Darm-realview-pbx.dtsi23 #include <dt-bindings/interrupt-controller/irq.h>
24 #include <dt-bindings/gpio/gpio.h>
27 #address-cells = <1>;
28 #size-cells = <1>;
29 compatible = "arm,realview-pbx";
49 vmmc: regulator-vmmc {
50 compatible = "regulator-fixed";
51 regulator-name = "vmmc";
52 regulator-min-microvolt = <3300000>;
53 regulator-max-microvolt = <3300000>;
[all …]
H A Darm-realview-pb1176.dts23 /dts-v1/;
24 #include <dt-bindings/interrupt-controller/irq.h>
25 #include <dt-bindings/gpio/gpio.h>
28 #address-cells = <1>;
29 #size-cells = <1>;
30 model = "ARM RealView PB1176";
31 compatible = "arm,realview-pb1176";
50 vmmc: regulator-vmmc {
51 compatible = "regulator-fixed";
52 regulator-name = "vmmc";
[all …]
H A Darm-realview-pb11mp.dts23 /dts-v1/;
24 #include <dt-bindings/interrupt-controller/irq.h>
25 #include <dt-bindings/gpio/gpio.h>
28 #address-cells = <1>;
29 #size-cells = <1>;
30 model = "ARM RealView PB11MPcore";
31 compatible = "arm,realview-pb11mp";
52 #address-cells = <1>;
53 #size-cells = <0>;
54 enable-method = "arm,realview-smp";
[all …]
H A Dversatile-ab.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
5 model = "ARM Versatile AB";
6 compatible = "arm,versatile-ab";
7 #address-cells = <1>;
8 #size-cells = <1>;
9 interrupt-parent = <&vic>;
19 stdout-path = &uart0;
28 #clock-cells = <0>;
29 compatible = "fixed-clock";
[all …]
H A Dvexpress-v2m.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * ARM Ltd. Versatile Express
6 * V2M-P1
8 * HBI-0190D
14 * RS1 variant (vexpress-v2m-rs1.dtsi), but there is a strong
18 * CHANGES TO vexpress-v2m-rs1.dtsi!
20 #include <dt-bindings/interrupt-controller/arm-gic.h>
24 compatible = "simple-bus";
25 #address-cells = <1>;
26 #size-cells = <1>;
[all …]
H A Dvexpress-v2m-rs1.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * ARM Ltd. Versatile Express
6 * V2M-P1
8 * HBI-0190D
10 * RS1 memory map ("ARM Cortex-A Series memory map" in the board's
14 * original variant (vexpress-v2m.dtsi), but there is a strong
18 * CHANGES TO vexpress-v2m.dtsi!
20 #include <dt-bindings/interrupt-controller/arm-gic.h>
23 v2m_fixed_3v3: fixed-regulator-0 {
24 compatible = "regulator-fixed";
[all …]
/openbmc/linux/drivers/firmware/efi/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "EFI (Extensible Firmware Interface) Support"
42 resource, and set aside for direct-access (device-dax) by
45 device-dax kmem facility. Say N to have the kernel treat this
77 depends on EFI_GENERIC_STUB && !ARM
88 calls. For compatibility with non-EFI loaders, the payload can be
90 loader implements the decompression algorithm and that non-EFI boot
130 capsule support in the firmware, which many OEMs do not provide.
135 bool "Add support for Quark capsules with non-standard headers"
151 interfaces which are provided by the firmware. This driver is used
[all …]
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/
H A Drelease-notes.rst2 # Copyright (c) 2022-2024, Arm Limited.
4 # SPDX-License-Identifier: MIT
16 of Your Software and Your Hardware designed or modified using the Arm Tools,
18 intended for safety-critical applications. Should Your Software or Your Hardware
23 Release notes - 2024.11
29 Release notes - 2024.06
33 ---------------------------
35 - Use Ethernet over VirtIO due to lan91c111 Ethernet driver support dropped from U-Boot.
36 …- Due to the performance uplimit of MPS3 FPGA and FVP, some Linux distros like Fedora Rawhide can …
37 - Corstone-1000 SoC on FVP doesn't have a secure debug peripheral. It does on the MPS3.
[all …]
H A Duser-guide.rst2 # Copyright (c) 2022-2024, Arm Limited.
4 # SPDX-License-Identifier: MIT
11 ------
12 The Corstone-1000 software stack uses the `Yocto Project <https://www.yoctoproject.org/>`__ to build
13 a tiny Linux distribution suitable for the Corstone-1000 platform (kernel and initramfs filesystem …
14 The Yocto Project relies on the `BitBake <https://docs.yoctoproject.org/bitbake.html#bitbake-docume…
19 -------------
26 - Git 1.8.3.1 or greater.
27 - Python 3.8.0 or greater.
28 - GNU Tar 1.28 or greater.
[all …]
/openbmc/openbmc/meta-arm/meta-arm-bsp/dynamic-layers/meta-arm-systemready/recipes-test/arm-systemready-acs/files/fvp-base/
H A D0001-check-sr-results-Change-the-expected-SR-result-confi.patch2 From: Debbie Martin <Debbie.Martin@arm.com>
4 Subject: [PATCH] [PATCH] check-sr-results: Change the expected SR result
7 Update the check-sr-results.yaml and format-sr-results.yaml files for the
8 Systemready IR suite. These changes are required because of the
9 following known differences of fvp-base outputs to those expected by the
12 Changes to check-sr-results.yaml:
13 1. acs-console.log:
14 a. must-have-esp: EFI partition/variable persistence not supported due to
16 b. warn-once-if-contains "-dirty": BL1, BL2, and BL31 have dirty versions.
17 c. must-contain "efi: ESRT=0x" and "'esrt: Reserving ESRT space from 0x'":
[all …]
/openbmc/u-boot/doc/
H A DREADME.uefi1 <!--
2 SPDX-License-Identifier: GPL-2.0+
5 -->
7 # UEFI on U-Boot
9 The Unified Extensible Firmware Interface Specification (UEFI) [1] has become
11 the interaction of drivers and applications with the firmware. The API comprises
17 The implementation of UEFI in U-Boot strives to reach the minimum requirements
18 described in "Server Base Boot Requirements System Software on ARM Platforms -
21 A full blown UEFI implementation would contradict the U-Boot design principle
26 The UEFI standard supports only little-endian systems. The UEFI support can be
[all …]
/openbmc/linux/arch/arm64/boot/dts/arm/
H A Djuno-motherboard.dtsi2 * ARM Juno Platform motherboard peripherals
4 * Copyright (c) 2013-2014 ARM Ltd
12 compatible = "fixed-clock";
13 #clock-cells = <0>;
14 clock-frequency = <24000000>;
15 clock-output-names = "juno_mb:clk24mhz";
19 compatible = "fixed-clock";
20 #clock-cells = <0>;
21 clock-frequency = <25000000>;
22 clock-output-names = "juno_mb:clk25mhz";
[all …]
/openbmc/docs/designs/
H A Ddevice-tree-gpio-naming.md12 subsystem. The replacement is a "descriptor-based" character device interface.
14 [libgpiod][1] is a suite of tools and library implemented in C and C++ which
25 specific field used to name the GPIOs in the DTS is `gpio-line-names`. This
29 scheme in the face of a universe of potential use-cases.
37 - Ensure common function GPIOs within OpenBMC use the same naming convention
52 Pattern: `*-button`
55 BMC-less machines use a button to trigger system behavior and in a BMC-managed
59 #### power-button
68 - `host*-ready`: Host ready, active high
69 - `host*-ready-n`: Host ready, active low
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/packagegroups/
H A Dpackagegroup-meta-oe.bb1 SUMMARY = "Meta-oe ptest packagegroups"
8 packagegroup-meta-oe \
9 packagegroup-meta-oe-benchmarks \
10 packagegroup-meta-oe-bsp \
11 packagegroup-meta-oe-connectivity \
12 packagegroup-meta-oe-core \
13 packagegroup-meta-oe-crypto \
14 packagegroup-meta-oe-dbs \
15 packagegroup-meta-oe-devtools \
16 packagegroup-meta-oe-extended \
[all …]
/openbmc/linux/drivers/net/usb/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
5 comment "Host-side USB support is needed for USB Network Adapter support"
16 tristate "USB CATC NetMate-based Ethernet device support"
35 tristate "USB KLSI KL5USB101-based ethernet device support"
40 ADS USB-10BT
45 D-Link DSB-650C and DU-E10
47 I-O DATA USB-ET/T
51 Mobility USB-Ethernet Adapter
52 NetGear EA-101
61 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
[all …]

12