/openbmc/u-boot/arch/ |
H A D | Kconfig | 8 prompt "Architecture select" 12 bool "ARC architecture" 21 bool "ARM architecture" 27 bool "M68000 architecture" 33 bool "MicroBlaze architecture" 38 bool "MIPS architecture" 44 bool "NDS32 architecture" 48 bool "Nios II architecture" 56 bool "PowerPC architecture" 63 bool "RISC-V architecture" [all …]
|
/openbmc/qemu/docs/system/openrisc/ |
H A D | emulation.rst | 1 OpenRISC 1000 CPU architecture support 5 the OpenRISC 1000 cpu architecture. 16 architecture manual available on the OpenRISC website in the 17 `OpenRISC Architecture <https://openrisc.io/architecture>`_ section.
|
/openbmc/u-boot/drivers/crypto/fsl/ |
H A D | Kconfig | 13 Enable Freescale Secure Boot and Trusted Architecture 18 Secure boot and trust architecture compatible version 2 23 Secure boot and trust architecture compatible version 4 28 Secure boot and trust architecture compatible version 5 33 Secure boot and trust architecture compatible version 6
|
/openbmc/openbmc/poky/meta/conf/machine/include/ |
H A D | README | 55 TUNE_ARCH - The GNU canonical arch for a specific architecture. i.e. 57 configure. TUNE_ARCH definitions are specific to a given architecture. 59 See each architecture's README for details for that CPU family. 61 TUNE_PKGARCH - The package architecture used by the packaging systems to 62 define the architecture, abi and tuning of a particular package. 64 each architecture. See each architectures README for details for that 69 PACKAGE_EXTRA_ARCHS:tune-<tune>. If an architecture deviates from the 70 default it will be listed in the architecture README. 78 architecture specific floating point. This is synchronized with the 90 new tune file for a "fast-forward" CPU architecture (one that supports
|
/openbmc/openbmc/poky/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/ |
H A D | 0001-Add-riscv32-support.patch | 6 Add missing definitions for the RISC-V 32-bit architecture. 12 src/architecture.h | 4 ++++ 27 diff --git a/src/architecture.h b/src/architecture.h 29 --- a/src/architecture.h 30 +++ b/src/architecture.h
|
/openbmc/qemu/scripts/ci/setup/ubuntu/ |
H A D | build-environment.yml | 22 - name: Add armhf foreign architecture to aarch64 hosts 23 command: dpkg --add-architecture armhf 26 - ansible_facts['architecture'] == 'aarch64' 36 - name: Include package lists based on OS and architecture 38 file: "ubuntu-2204-{{ ansible_facts['architecture'] }}.yaml" 66 - ansible_facts['architecture'] == 'aarch64'
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/debootstrap/debootstrap/ |
H A D | 0003-do-not-hardcode-the-full-path-of-dpkg.patch | 25 dpkg --print-architecture >/dev/null 2>&1; then 26 - HOST_ARCH=$(/usr/bin/dpkg --print-architecture) 27 + HOST_ARCH=$(dpkg --print-architecture) 29 udpkg --print-architecture >/dev/null 2>&1; then 30 HOST_ARCH=$(/usr/bin/udpkg --print-architecture)
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/mozjs/mozjs-128/ |
H A D | armv5.patch | 10 js/src/jit/arm/Architecture-arm.cpp | 2 ++ 13 diff --git a/js/src/jit/arm/Architecture-arm.cpp b/js/src/jit/arm/Architecture-arm.cpp 15 --- a/js/src/jit/arm/Architecture-arm.cpp 16 +++ b/js/src/jit/arm/Architecture-arm.cpp
|
/openbmc/openbmc/poky/meta/conf/machine/include/x86/ |
H A D | README | 11 X86ARCH32 - This is the 32-bit architecture GNU canonical arch, TUNE_ARCH. 13 X86ARCH64 - This is the 64-bit architecture GNU canonical arch, TUNE_ARCH. 19 The package architecture for 32-bit targets is historical and generally 22 For 64-bit architectures, the architecture is expected to end in '_64'.
|
/openbmc/libcper/specification/json/sections/ |
H A D | cper-vtd-dmar.json | 28 "description": "Value of version register as defined in VT-d architecture" 40 "description": "Value of capability register in VT-d architecture" 44 "description": "Value of extended capability register in VT-d architecture" 48 …"description": "Value of Global Command register in VT-d architecture programmed by the operating … 52 "description": "Value of Global Status register in VT-d architecture" 56 "description": "Value of Fault Status register in VT-d architecture"
|
/openbmc/openbmc/poky/meta/recipes-core/ifupdown/files/ |
H A D | defn2-c-man-don-t-rely-on-dpkg-architecture-to-set-a.patch | 4 Subject: [PATCH] defn2[c|man]: don't rely on dpkg-architecture to set arch 29 -my $DEB_HOST_ARCH_OS = `dpkg-architecture -qDEB_HOST_ARCH_OS`; 32 +#my $DEB_HOST_ARCH_OS = `dpkg-architecture -qDEB_HOST_ARCH_OS`; 46 -my $DEB_HOST_ARCH_OS = `dpkg-architecture -qDEB_HOST_ARCH_OS`; 49 +#my $DEB_HOST_ARCH_OS = `dpkg-architecture -qDEB_HOST_ARCH_OS`;
|
/openbmc/intel-ipmi-oem/ |
H A D | README.md | 5 Intel architecture. 28 1. [OpenBMC IPMI Architecture](https://github.com/openbmc/docs/blob/master/architecture/ipmi-archit…
|
/openbmc/docs/ |
H A D | features.md | 52 https://github.com/openbmc/docs/blob/master/architecture/object-mapper.md 58 https://github.com/openbmc/docs/blob/master/architecture/code-update/code-update.md 64 https://github.com/openbmc/docs/blob/master/architecture/ipmi-architecture.md 69 https://github.com/openbmc/docs/blob/master/architecture/LED-architecture.md 86 https://github.com/openbmc/docs/blob/master/architecture/user-management.md 91 https://github.com/openbmc/docs/blob/master/architecture/sensor-architecture.md
|
/openbmc/phosphor-objmgr/ |
H A D | README.md | 4 There is documentation about it in the [docs repository][architecture]. 28 [architecture]: 29 https://github.com/openbmc/docs/blob/master/architecture/object-mapper.md
|
/openbmc/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
H A D | README.soc | 24 - Data Path Acceleration Architecture (DPAA) incorporating acceleration the 48 - QorIQ platform's trust architecture 2.1 53 architecture combining eight ARM A53 processor cores 67 - Data path acceleration architecture 2.0 (DPAA2) 78 - QorIQ platform's trust architecture 3.0 96 - Data path acceleration architecture (DPAA2) incorporating acceleration for 122 - QorIQ platform's trust architecture 3.0 166 - QorIQ platform's trust architecture 2.1 180 - Data Path Acceleration Architecture (DPAA) incorporating acceleration the 207 - QorIQ platform's trust architecture 2.1 [all …]
|
/openbmc/u-boot/doc/ |
H A D | README.generic-board | 9 U-Boot traditionally had a board.c file for each architecture. This introduced 10 quite a lot of duplication, with each architecture tending to do 26 fields which are common to all architectures. Architecture-specific fields 56 a new architecture fully functional and running with U-Boot. 65 for a particular architecture. It also makes it easier to adopt Graeme's 80 Instead of moving over a whole architecture, this series takes the approach 81 of simply enabling generic board support for an architecture. It is then up 100 way to put architecture-specific fields into a separate header file, but
|
/openbmc/qemu/scripts/ci/setup/ |
H A D | gitlab-runner.yml | 46 - name: Set the architecture for gitlab-runner 48 gitlab_runner_arch: "{{ ansible_to_gitlab_arch[ansible_facts[\"architecture\"]] }}" 98 …architecture\"] }},{{ ansible_facts[\"distribution\"]|lower }}_{{ ansible_facts[\"distribution_ver… 102 …] }} {{ ansible_facts[\"distribution_version\"] }} {{ ansible_facts[\"architecture\"] }} ({{ ansib… 105 - ansible_facts['architecture'] == 'aarch64'
|
/openbmc/phosphor-hwmon/ |
H A D | README.md | 4 [Sensor Architecture](https://github.com/openbmc/docs/blob/master/architecture/sensor-architecture.…
|
/openbmc/sdbusplus/example/ |
H A D | coroutine-example.cpp | 24 // Get the Architecture property. in startup() 25 std::cout << co_await systemd.get_property<std::string>(ctx, "Architecture") in startup() 61 // Try to set the Architecture property (which won't work). in startup() 64 co_await systemd.set_property(ctx, "Architecture", "arm64"); in startup() 68 std::cout << "Caught exception because you cannot set Architecture: " in startup()
|
/openbmc/u-boot/tools/buildman/ |
H A D | toolchain.py | 27 the one for the given architecture (or None if not found). 30 arch: Architecture to search for 54 arch: Architecture of toolchain as determined from the first 81 # The architecture is the first part of the name 199 We select one toolchain for each architecture type 202 toolchains: Dict of Toolchain objects, keyed by architecture name 203 prefixes: Dict of prefixes to check, keyed by architecture. This can 258 architecture if it is a higher priority than the others. 264 arch: Toolchain architecture, or None if not known 318 architecture for each, and whether it works. Then we select the [all …]
|
/openbmc/openbmc/poky/meta/conf/machine/include/microblaze/ |
H A D | arch-microblaze.inc | 1 # MicroBlaze architecture tune feature configuration 3 # Architecture feature and override 43 # Feature package architecture formatting 54 # Architecture name, either 'microblaze' or 'microblazeel' depending on endianess 60 # Package Architecture formatting
|
/openbmc/qemu/docs/system/arm/ |
H A D | emulation.rst | 3 A-profile CPU architecture support 7 Armv8 and Armv9 versions of the A-profile architecture. It also has support for 8 the following architecture extensions: 168 to the `Arm Architecture Reference Manual for A-profile architecture 176 R-profile CPU architecture support 182 M-profile CPU architecture support 187 for the following architecture extensions: 201 to the `Armv8-M Arm Architecture Reference Manual
|
/openbmc/openbmc/poky/meta/recipes-support/boost/boost/ |
H A D | 0001-dont-setup-compiler-flags-m32-m64.patch | 32 - compile-link-flags <target-os>$(generic-os)/<architecture>s390x/<address-model>32 : -m31 ; 33 - compile-link-flags <target-os>$(generic-os)/<architecture>s390x/<address-model>64 : -m64 ; 35 - compile-link-flags <target-os>$(generic-os)/<architecture>$(arch)/<address-model>32 : -m32 ; 36 - compile-link-flags <target-os>$(generic-os)/<architecture>$(arch)/<address-model>64 : -m64 ;
|
/openbmc/openbmc/poky/meta/conf/machine/include/m68k/ |
H A D | arch-m68k.inc | 1 # m68k Architecture definitions 5 # Architecture name
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | arch.rst | 4 Overall Architecture of the Linux Tracing and Profiling Tools 7 Architecture of the Tracing and Profiling Tools 11 architecture' for what seems to be a random collection of tracing tools
|