| /openbmc/u-boot/arch/ |
| H A D | Kconfig | 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"
124 bool "SuperH architecture"
[all …]
|
| /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/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/linux/Documentation/features/ |
| H A D | arch-support.txt | 2 For generic kernel features that need architecture support, the
8 | ok | # feature supported by the architecture
9 |TODO| # feature not yet supported by the architecture
11 | N/A| # feature doesn't apply to the architecture
|
| /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/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/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/linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.rst | 104 ARM ARM architecture is enabled.
105 ARM64 ARM64 architecture is enabled.
120 IA-64 IA-64 architecture is enabled.
121 IMA Integrity measurement architecture is enabled.
131 LOONGARCH LoongArch architecture is enabled.
134 M68k M68k architecture is enabled.
138 MIPS MIPS architecture is enabled.
146 PARISC The PA-RISC architecture is enabled.
151 PPC PowerPC architecture is enabled.
157 RISCV RISCV architecture is enabled.
[all …]
|
| /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
66 https://github.com/openbmc/docs/blob/master/architecture/ipmi-architecture.md
71 https://github.com/openbmc/docs/blob/master/architecture/LED-architecture.md
88 https://github.com/openbmc/docs/blob/master/architecture/user-management.md
93 https://github.com/openbmc/docs/blob/master/architecture/sensor-architecture.md
|
| /openbmc/u-boot/drivers/crypto/fsl/ |
| H A D | Kconfig | 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-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/linux/arch/ |
| H A D | Kconfig | 3 # General architecture dependent options
20 menu "General architecture-dependent options"
25 Select if the architecture can check permissions at sub-page
39 # Basic CPU dead synchronization selected by architecture
44 # Full CPU synchronization with alive state selected by architecture
149 This symbol should be selected by an architecture if 64 bit
151 though it is not a 64 bit architecture.
165 This symbol should be selected by an architecture if it can
180 inline assembler that the architecture code provides in the
185 store-and-swap instructions if the architecture has them. It
[all …]
|
| /openbmc/linux/arch/mips/jazz/ |
| H A D | Kconfig | 9 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
20 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
30 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
|
| /openbmc/intel-ipmi-oem/ |
| H A D | README.md | 5 Intel architecture.
28 …C IPMI Architecture](https://github.com/openbmc/docs/blob/master/architecture/ipmi-architecture.md)
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | machinecheck.rst | 29 For more details about the x86 machine check architecture
30 see the Intel and AMD architecture manuals from their developer websites.
32 For more details about the architecture
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | multilib_header.bbclass | 9 # If applicable on the architecture, this routine will rename the header and
11 # A wrapper will be generated for the architecture that knows how to call
12 # all of the ABI variants for that given architecture.
|
| /openbmc/linux/Documentation/mm/ |
| H A D | memory-model.rst | 16 FLATMEM and SPARSEMEM. Each architecture defines what
43 To allocate the `mem_map` array, architecture specific setup code should
48 An architecture may free parts of the `mem_map` array that do not cover the
49 actual physical pages. In such case, the architecture specific
75 `MAX_PHYSMEM_BITS` constants defined by each architecture that
77 physical address that an architecture supports, the
100 The architecture setup code should call sparse_init() to
119 To use vmemmap, an architecture has to reserve a range of virtual
122 the architecture should implement :c:func:`vmemmap_populate` method
124 virtual memory map. If an architecture does not have any special
|
| H A D | page_tables.rst | 17 height. The architecture code for each supported architecture will then
90 The architecture defines the size and contents of `pteval_t`.
94 architecture-specific bits such as memory protection.
127 pointers on each level is architecture-defined.::
146 If the architecture does not use all the page table levels, they can be *folded*
151 Page table handling code that wishes to be architecture-neutral, such as the
154 architecture-specific code, so as to be robust to future changes.
|
| /openbmc/linux/Documentation/core-api/irq/ |
| H A D | irqflags-tracing.rst | 15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
21 state changes. But an architecture can be irq-flags-tracing enabled in a
42 - if the architecture has non-maskable interrupts then those need to be
47 implementation in an architecture: lockdep will detect that and will
|
| /openbmc/openbmc/poky/meta/recipes-devtools/dpkg/dpkg/ |
| H A D | add_armeb_triplet_entry.patch | 20 configure:23183: checking dpkg architecture name
21 configure:23189: error: cannot determine host dpkg architecture
28 Upstream-Status: Inappropriate [not a debian architecture]
|
| /openbmc/linux/drivers/perf/arm_cspmu/ |
| H A D | Kconfig | 10 based on ARM CoreSight PMU architecture. Note that this PMU
11 architecture does not have relationship with the ARM CoreSight
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | syscalls | 7 Note that this interface is different for every architecture
8 that Linux supports. Please see the architecture-specific
|
| /openbmc/linux/drivers/clk/bcm/ |
| H A D | Kconfig | 30 based on the ARM architecture
38 based on the MIPS architecture
47 based on the MIPS architecture.
62 based on the iProc architecture
|
| /openbmc/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
| H A D | README.soc | 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
207 - QorIQ platform's trust architecture 2.1
223 - Data path acceleration architecture (DPAA2) incorporating acceleration for
249 - QorIQ platform's trust architecture 3.0
[all …]
|