| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ti/ |
| H A D | k3.txt | 1 Texas Instruments K3 Multicore SoC architecture device tree bindings
4 Platforms based on Texas Instruments K3 Multicore SoC architecture
11 architecture it uses, using one of the following compatible values:
|
| /f-stack/dpdk/doc/guides/vdpadevs/ |
| H A D | features_overview.rst | 112 Support armv7 architecture.
115 Support armv8a (64bit) architecture.
118 Support PowerPC architecture.
121 Support 32bits x86 architecture.
124 Support 64bits x86 architecture.
|
| /f-stack/freebsd/arm/arm/ |
| H A D | cpuinfo.c | 109 cpuinfo.architecture = 1; in cpuinfo_init()
113 cpuinfo.architecture = (cpuinfo.midr >> 16) & 0x0F; in cpuinfo_init()
118 cpuinfo.architecture = (cpuinfo.midr >> 16) & 0x0F; in cpuinfo_init()
134 if (cpuinfo.architecture != 0xF) in cpuinfo_init()
|
| /f-stack/freebsd/contrib/openzfs/config/ |
| H A D | deb.am | 23 debarch=`$(DPKG) --print-architecture`; \
33 debarch=`$(DPKG) --print-architecture`; \
42 debarch=`$(DPKG) --print-architecture`; \
|
| H A D | kernel-in-compat-syscall.m4 | 4 dnl # architecture basis. Prior to this is_compat_task() was the
|
| H A D | always-arch.m4 | 2 dnl # Set the target cpu architecture. This allows the
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | cpus.txt | 17 Freescale Power Architecture) defines the architecture for Freescale
18 Power CPUs. The EREF defines some architecture categories not defined
|
| /f-stack/dpdk/doc/guides/regexdevs/ |
| H A D | features_overview.rst | 73 Support armv8 (64bit) architecture.
76 Support x86 architecture.
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | design.rst | 10 In DPDK and DPDK applications, some code is specific to an architecture (i686, x86_64) or to an exe…
11 As far as is possible, all such instances of architecture or env-specific code should be provided v…
14 For instance, a file located in a subdir of "x86_64" directory is specific to this architecture.
20 The correct location for architecture or executive environment specific code is in the EAL.
36 …In this case, the code is split into two separate files that are architecture or environment speci…
44 * ``RTE_ARCH`` is a string that contains the name of the architecture.
|
| /f-stack/dpdk/lib/librte_lpm/ |
| H A D | meson.build | 7 # without worrying about which architecture we actually need
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | intro.rst | 7 This document provides software architecture information,
33 * The software architecture and how to use it (through examples),
|
| H A D | overview.rst | 9 This section gives a global overview of the architecture of Data Plane Development Kit (DPDK).
19 which may be specific to a mode of the Intel® architecture (32-bit or 64-bit),
44 Once these libraries are created for the specific environment and architecture,
92 .. figure:: img/architecture-overview.*
|
| H A D | glossary.rst | 45 In contrast to the control plane, the data plane in a network architecture
209 In the DPDK, the target is a combination of architecture, machine,
|
| /f-stack/freebsd/arm/include/ |
| H A D | cpuinfo.h | 92 int architecture; member
|
| H A D | acle-compat.h | 182 # error Unable to determine architecture version.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/bcm/ |
| H A D | brcm,hr2.yaml | 11 are based on Broadcom's iProc SoC architecture and feature a single core Cortex
|
| /f-stack/dpdk/examples/performance-thread/l3fwd-thread/ |
| H A D | meson.build | 17 # get the performance thread (pt) architecture subdir
|
| /f-stack/dpdk/examples/performance-thread/pthread_shim/ |
| H A D | meson.build | 17 # get the performance thread (pt) architecture subdir
|
| /f-stack/freebsd/contrib/device-tree/Bindings/timer/ |
| H A D | ti,keystone-timer.txt | 4 architecture devices. The timer can be configured as a general-purpose 64-bit
|
| H A D | ti,davinci-timer.txt | 4 architecture devices. The timer can be configured as a general-purpose 64-bit
|
| /f-stack/freebsd/contrib/device-tree/Bindings/openrisc/opencores/ |
| H A D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/hisilicon/ |
| H A D | hisilicon-low-pin-count.txt | 4 Hip06 is based on arm64 architecture where there is no I/O space. So, the
|
| /f-stack/freebsd/sys/ |
| H A D | kerneldump.h | 83 char architecture[12]; member
|
| /f-stack/freebsd/contrib/device-tree/Bindings/hwlock/ |
| H A D | omap-hwspinlock.txt | 13 (for OMAP architecture based SoCs only)
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | nvidia,tegra194-ccplex.yaml | 15 Tegra194 SOC has homogeneous architecture where each cluster has two
|