| /openbmc/linux/Documentation/mm/ |
| H A D | remap_file_pages.rst | 17 architectures. It would be nice to free up the flag for other usage.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | genericirq.rst | 70 also valuable for (sub)architectures which need specific quirks in the
78 various architectures.)
88 the new model should be used in more and more architectures, as it
320 The generic functions are intended for 'clean' architectures and chips,
|
| H A D | dma-attributes.rst | 32 virtual mapping for the allocated buffer. On some architectures creating
113 On some architectures allocation failures are reported with error messages
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | rapidio.rst | 17 RapidIO on new architectures, write new drivers, or to understand the
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/json-schema-validator/json-schema-validator/ |
| H A D | 0002-Fix-assumed-signed-char.patch | 7 unsigned is implementation defined. On some architectures like PowerPC,
|
| /openbmc/linux/include/asm-generic/ |
| H A D | Kbuild | 3 # asm headers that all architectures except um should have
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | headers_install.rst | 32 is platform-specific, to see a complete list of supported architectures use
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs/ |
| H A D | 0004-v8-don-t-override-ARM-CFLAGS.patch | 19 supported architectures, too.
|
| /openbmc/u-boot/board/keymile/km83xx/ |
| H A D | README.kmeter1 | 24 Mounting options have been foreseen for device architectures from
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/espeak/ |
| H A D | espeak_1.48.04.bb | 7 file://0001-Fix-build-of-shared-library-on-architectures-needing.patch \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/mraa/ |
| H A D | mraa_git.bb | 46 # nodejs isn't available for armv4/armv5 architectures
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/upm/ |
| H A D | upm_git.bb | 40 # nodejs isn't available for armv4/armv5 architectures
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | run_wrapper.rst | 180 Not all architectures currently support this flag, but we can use
182 is ignored), the tests will run via UML. Non-UML architectures,
197 This means that for most architectures, running under qemu is as simple as:
283 For example, i386, x86_64, arm, um, etc. Non-UML architectures run on qemu.
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | concepts.rst | 23 address ranges. Besides, different CPU architectures, and even
42 size of each page is architecture specific. Some architectures allow
75 Many modern CPU architectures allow mapping of the memory pages
112 architectures define all zones, and requirements for DMA are different
|
| /openbmc/openbmc/poky/meta/lib/oe/package_manager/deb/ |
| H A D | __init__.py | 455 architectures = ""
458 architectures += "\"%s\";" % base_arch
459 apt_conf.write(" Architectures {%s};\n" % architectures);
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-memmap | 10 However, on most architectures that firmware-provided memory
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | ubsan.rst | 79 CONFIG_UBSAN_ALIGNMENT. It's off by default on architectures that support
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | x32-psabi.rst | 8 32-bit processor-specific ABI for Intel 64 (x86-64) architectures. An
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/open-vm-tools/open-vm-tools/ |
| H A D | 0014-timeSync-Portable-way-to-print-64bit-time_t.patch | 6 This ensures when 64bit time_t is used on 32bit architectures (
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | vc4.rst | 64 command below, on either arm or arm64 architectures,
|
| /openbmc/linux/fs/verity/ |
| H A D | Kconfig | 10 # some architectures provided optimized implementations of the same
|
| /openbmc/linux/Documentation/process/ |
| H A D | volatile-considered-harmful.rst | 58 architectures. Those accessors are written to prevent unwanted
77 architectures where direct I/O memory access does work. Essentially,
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.kasan | 20 architectures that do not support these instrumentation types.
67 1. Generic KASAN (supported by many architectures, enabled with
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | schedutil.rst | 50 a big CPU, we allow architectures to scale the time delta with two ratios, one
53 For simple DVFS architectures (where software is in full control) we trivially
|
| /openbmc/linux/arch/openrisc/ |
| H A D | Kconfig | 220 On some architectures there is currently no way for the boot loader
221 to pass arguments to the kernel. For these architectures, you should
|