Home
last modified time | relevance | path

Searched refs:architectures (Results 1 – 25 of 440) sorted by relevance

12345678910>>...18

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/espeak/files/
H A D0001-Fix-build-of-shared-library-on-architectures-needing.patch4 Subject: [PATCH] Fix build of shared library on architectures needing -fPIC
6 Certain architectures, like Sparc and Sparc64 require objects to be
8 libraries. On other architectures, -fPIC is the same as -fpic so this
9 patch doesn't affect such architectures.
/openbmc/linux/virt/kvm/
H A DKconfig22 # Only strongly ordered architectures can select this, as it doesn't
30 # Weakly ordered architectures can only select this, advertising
36 # Allow enabling both the dirty bitmap and dirty ring. Only architectures
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/unixodbc/files/
H A DCVE-2024-1013.patch6 These result in out-of-bounds stack writes on 64-bit architectures
8 unnoticed on little-endian architectures (although big-endian
9 architectures must be broken).
/openbmc/linux/Documentation/arch/arm/
H A Dsetup.rst7 for most ARM Linux architectures.
61 based machines. May be used differently by different architectures.
65 different architectures.
69 architectures.
102 then a value of 50 Mhz is the default on 21285 architectures.
/openbmc/linux/Documentation/ABI/stable/
H A Dvdso7 On some architectures, when the kernel loads any userspace program it
29 ABI of those symbols is considered stable. It may vary across architectures,
34 The maintainers of the other vDSO-using architectures should confirm
/openbmc/linux/lib/vdso/
H A DKconfig20 in 32 bit only architectures.
30 Selected by architectures which support time namespaces in the
/openbmc/linux/Documentation/rust/
H A Darch-support.rst7 which limits the supported architectures that can be targeted. In addition,
12 Below is a general summary of architectures that currently work. Level of
/openbmc/linux/Documentation/driver-api/
H A Ddevice-io.rst31 memory, but as accesses to a device. Some architectures define devices
44 space to the kernel. Most architectures allocate new address space each
153 ``void __iomem *reg``. On most architectures it is a regular pointer that
160 While on most architectures, ioremap() creates a page table entry for an
162 architectures require special instructions for MMIO, and the ``__iomem`` pointer
182 On architectures that require an expensive barrier for serializing against
197 for mapping PCI I/O space with pci_iomap() or ioport_map(). On architectures
200 other architectures, these are simply aliases.
211 Note: On some architectures, the normal readl()/writel() functions
223 on 32-bit architectures but allow two consecutive 32-bit accesses instead.
[all …]
/openbmc/linux/Documentation/livepatch/
H A Dreliable-stacktrace.rst20 debugging are unsound for livepatching. Livepatching depends on architectures
30 'arch_stack_walk_reliable', and other architectures must implement
56 architectures may need to verify that code has been compiled in a manner
71 The unwinding process varies across architectures, their respective procedure
73 details that architectures should consider.
89 architectures verify that a stacktrace ends at an expected location, e.g.
116 trace, it is strongly recommended that architectures positively identify code
140 For some architectures this may change at runtime as a result of dynamic
219 It is recommended that architectures unwind cases where return_to_handler has
220 not yet been returned to, but architectures are not required to unwind from the
[all …]
/openbmc/openbmc/poky/meta/conf/machine/include/x86/
H A DREADME4 Most of the items for the X86 architectures are defined in the single
22 For 64-bit architectures, the architecture is expected to end in '_64'.
/openbmc/linux/Documentation/core-api/
H A Dunaligned-memory-access.rst13 Linux runs on a wide variety of architectures which have varying behaviour
46 In reality, only a few architectures require natural alignment on all sizes
47 of memory access. However, we must consider ALL supported architectures;
59 - Some architectures are able to perform unaligned memory accesses
61 - Some architectures raise processor exceptions when unaligned accesses
64 - Some architectures raise processor exceptions when unaligned accesses
67 - Some architectures are not capable of unaligned memory access, but will
246 On architectures that require aligned loads, networking requires that the IP
249 architectures this constant has the value 2 because the normal ethernet
258 unnecessary on architectures that can do unaligned accesses, the code can be
/openbmc/openbmc/poky/meta/recipes-support/lzo/lzo/
H A D0001-Use-memcpy-instead-of-reinventing-it.patch7 constraints for our architectures.
38 + * constant n to be as fast as handwritten code, and knows which architectures
63 + * constant n to be as fast as handwritten code, and knows which architectures
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/flashrom/flashrom/
H A D0001-flashrom-Mark-RISCV-as-non-memory-mapped-I-O-archite.patch20 # architectures with unknown raw access properties.
21 # Right now those architectures are alpha hppa m68k sh s390
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sedutil/files/
H A D0001-Fix-build-on-big-endian-architectures.patch4 Subject: [PATCH] Fix build on big endian architectures
24 -#error This code does not support big endian architectures
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/
H A D0001-selftests-timers-Fix-clock_adjtime-for-newer-32-bit-.patch6 Newer 32-bit architectures e.g. riscv32 are using 64-bit time_t
8 valid-adjtimex testcase fails to compile on such architectures.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mariadb/
H A D0001-innobase-Define-__NR_futex-if-it-does-not-exist.patch6 __NR_futex is not defines by newer architectures e.g. arc, riscv32 as
10 to fail to build for these newer architectures. This patch defines a
/openbmc/openbmc/poky/meta/recipes-devtools/qemu/qemu/
H A D0008-Define-MAP_SYNC-and-MAP_SHARED_VALIDATE-on-needed-li.patch7 linux only wires MAP_SYNC and MAP_SHARED_VALIDATE for architectures
10 architectures on Linux as well. This fixes build on mips/musl/linux
/openbmc/u-boot/doc/
H A DREADME.displaying-bmps4 Some architectures cannot handle unaligned memory accesses, and an attempt to
5 perform one will lead to a data abort. On such architectures it is necessary to
H A DREADME.generic-board15 All boards and architectures have moved to this as of mid 2016.
26 fields which are common to all architectures. Architecture-specific fields
50 3. As time goes by the architectures naturally diverge since there is limited
54 4. New architectures must implement all the features all over again, and
97 architectures include and need it, most global_data.h files already have
H A DREADME.unaligned-memory-access.txt7 Linux runs on a wide variety of architectures which have varying behaviour
40 In reality, only a few architectures require natural alignment on all sizes
41 of memory access. However, we must consider ALL supported architectures;
53 - Some architectures are able to perform unaligned memory accesses
55 - Some architectures raise processor exceptions when unaligned accesses
58 - Some architectures raise processor exceptions when unaligned accesses
61 - Some architectures are not capable of unaligned memory access, but will
/openbmc/linux/Documentation/
H A Datomic_t.txt152 are time critical and can, (typically) on LL/SC architectures, be more
201 These helper barriers exist because architectures have varying implicit
202 ordering on their SMP atomic primitives. For example our TSO architectures
326 indefinitely. However, this is not evident on LL/SC architectures, because
357 to fail on some architectures, let alone whatever the compiler makes of the C
361 Even native CAS architectures can fail to provide forward progress for their
365 to a failed CAS in order to ensure some progress. Affected architectures are
/openbmc/linux/Documentation/powerpc/
H A Delf_hwcaps.rst147 supporting later architectures DO NOT set this feature.
160 supporting later architectures also set this feature.
182 supporting later architectures also set this feature.
209 supporting later architectures also set this feature.
228 supporting later architectures also set this feature.
/openbmc/openbmc/poky/meta/conf/machine/include/
H A DREADME46 need to be defined in the architectures base arch file, i.e.
64 each architecture. See each architectures README for details for that
68 architectures. By default this is equal to
72 PACKAGE_EXTRA_ARCHS:tune-<tune> - List all of the package architectures
/openbmc/openbmc/meta-arm/meta-arm-systemready/
H A DREADME.md136 [Arm SystemReady]: https://www.arm.com/architecture/system-architectures/systemready-certification-…
138 [Arm SystemReady SR]: https://www.arm.com/architecture/system-architectures/systemready-certificati…
139 [Arm SystemReady ES]: https://www.arm.com/architecture/system-architectures/systemready-certificati…
140 [Arm SystemReady IR]: https://www.arm.com/architecture/system-architectures/systemready-certificati…
141 [Arm SystemReady LS]: https://www.arm.com/architecture/system-architectures/systemready-certificati…
/openbmc/openbmc/poky/meta/recipes-core/glib-2.0/files/meson.cross.d/
H A Dcommon2 # On all known supported architectures the stack grows down

12345678910>>...18