| /openbmc/openbmc/meta-ampere/meta-mitchell/conf/templates/default/ |
| H A D | local.conf.sample | 91 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | externalsrc.bbclass | 139 # If B=S the same builddir is used even for different architectures.
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | intro.rst | 172 several target architectures and has many pre-built kernel images and
|
| /openbmc/linux/security/integrity/ima/ |
| H A D | Kconfig | 314 This option is selected by architectures to enable secure and/or
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | tainted-kernels.rst | 133 - certain drivers are being used on non supported architectures (such as
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | aliasing.rst | 168 ioremap_page_range() as most other architectures do.
|
| /openbmc/linux/Documentation/process/ |
| H A D | maintainer-soc.rst | 16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
|
| /openbmc/linux/Documentation/power/ |
| H A D | energy-model.rst | 72 domains can have different micro-architectures.
|
| /openbmc/linux/drivers/misc/ |
| H A D | Kconfig | 220 use the cs5535_mfgpt_ API; however, different architectures might
222 architectures to set as necessary.
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | advanced.rst | 235 # greater than 8 on x86 architectures, it should be automatically
762 architectures, a kernel source repository with multiple branches is more
805 When you have multiple machines and architectures to support, or you are
|
| /openbmc/linux/tools/usb/usbip/ |
| H A D | INSTALL | 147 architectures, `configure' can figure that out, but if it prints a
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | x86-fit-boot.txt | 254 6. It makes x86 more like other architectures in the way it boots a kernel.
|
| /openbmc/qemu/linux-user/alpha/ |
| H A D | syscall.tbl | 464 # all other architectures have common numbers for new syscall, alpha
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/conf/templates/default/ |
| H A D | local.conf.sample | 113 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-amd/meta-daytonax/conf/templates/default/ |
| H A D | local.conf.sample | 113 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | libraries.rst | 202 ``qemux86-64`` image. The possible architectures in the system are "all",
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | debugfs.rst | 103 architectures, though, complicating the situation somewhat. There are
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-c2c.txt | 135 granularity. Some architectures have an Adjacent Cacheline Prefetch
|
| /openbmc/linux/fs/ |
| H A D | Kconfig | 263 ramfs. For architectures that support it, say Y here and read
|
| /openbmc/linux/arch/alpha/kernel/syscalls/ |
| H A D | syscall.tbl | 464 # all other architectures have common numbers for new syscall, alpha
|
| /openbmc/linux/Documentation/staging/ |
| H A D | static-keys.rst | 183 There are a few functions and macros that architectures must implement in order
|
| /openbmc/linux/Documentation/locking/ |
| H A D | robust-futexes.rst | 217 All other architectures should build just fine too - but they won't have
|
| /openbmc/openbmc/meta-facebook/meta-bletchley/conf/templates/default/ |
| H A D | local.conf.sample | 93 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-facebook/meta-greatlakes/conf/templates/default/ |
| H A D | local.conf.sample | 93 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-hpe/meta-dl360poc/conf/templates/default/ |
| H A D | local.conf.sample | 93 # you can build the SDK packages for architectures other than the machine you are
|