Home
last modified time | relevance | path

Searched refs:architecture (Results 1 – 25 of 350) sorted by relevance

12345678910>>...14

/Linux-v4.19/Documentation/features/
Darch-support.txt2 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
/Linux-v4.19/Documentation/devicetree/bindings/arm/ti/
Dk3.txt1 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:
/Linux-v4.19/Documentation/admin-guide/
Dkernel-parameters.rst90 ARM ARM architecture is enabled.
104 IA-64 IA-64 architecture is enabled.
105 IMA Integrity measurement architecture is enabled.
118 M68k M68k architecture is enabled.
122 MIPS MIPS architecture is enabled.
132 PARISC The PA-RISC architecture is enabled.
137 PPC PowerPC architecture is enabled.
142 S390 S390 architecture is enabled.
150 SH SuperH architecture is enabled.
152 SPARC Sparc architecture is enabled.
[all …]
/Linux-v4.19/arch/mips/jazz/
DKconfig10 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
22 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
33 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
/Linux-v4.19/Documentation/
Dirqflags-tracing.txt15 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
Dcputopology.txt11 socket number, but the actual value is architecture and platform
18 architecture and platform dependent.
24 architecture and platform dependent.
30 architecture and platform dependent.
72 To implement it in an architecture-neutral way, a new source file,
80 For an architecture to support this feature, it must define some of
D00-INDEX60 - directory with info about Linux on the ARM architecture.
62 - directory with info about Linux on the 64 bit ARM architecture.
184 - directory with info about Linux on Intel 32 bit architecture.
186 - directory with info about Linux on Intel 64 bit architecture.
248 - directory with info about Linux on Motorola 68k architecture.
264 - Intel Many Integrated Core (MIC) architecture device driver.
266 - directory with info about Linux on MIPS architecture.
282 - Linux on the Nios II architecture.
298 - directory with info on using Linux on PA-RISC architecture.
366 - directory with info on porting Linux to a new architecture.
/Linux-v4.19/Documentation/ABI/stable/
Dsyscalls7 Note that this interface is different for every architecture
8 that Linux supports. Please see the architecture-specific
/Linux-v4.19/Documentation/usb/
Dlinux.inf19 ; Decoration for x86 architecture
23 ; Decoration for x64 architecture
27 ; Decoration for ia64 architecture
/Linux-v4.19/tools/perf/pmu-events/
DREADME19 - To reduce JSON event duplication per architecture, platform JSONs may
21 events", defined in architecture standard JSONs.
22 Architecture standard JSONs must be located in the architecture root
44 - Set of 'PMU events tables' for all known CPUs in the architecture,
61 - A 'mapping table' that maps each CPU of the architecture, to its
86 3. _All_ known CPU tables for architecture are included in the perf
/Linux-v4.19/arch/
DKconfig3 # General architecture dependent options
12 menu "General architecture-dependent options"
139 This symbol should be selected by an architecture if 64 bit
141 though it is not a 64 bit architecture.
155 This symbol should be selected by an architecture if it can
170 inline assembler that the architecture code provides in the
175 store-and-swap instructions if the architecture has them. It
180 Any architecture with load-and-swap or store-and-swap
244 An architecture should select this when it can successfully
263 An architecture should select this to provide hardened usercopy
[all …]
/Linux-v4.19/Documentation/arm64/
Dlegacy_instructions.txt3 the architecture. The infrastructure code uses undefined instruction
14 have been obsoleted in the architecture, e.g., SWP
32 architecture. Deprecated instructions should default to emulation
/Linux-v4.19/Documentation/nios2/
DREADME1 Linux on the Nios II architecture
16 Nios II is a 32-bit embedded-processor architecture designed specifically for the
/Linux-v4.19/Documentation/arm/Samsung/
DGPIO.txt7 This outlines the Samsung GPIO implementation and the architecture
32 Pin configuration is specific to the Samsung architecture, with each SoC
/Linux-v4.19/Documentation/kbuild/
Dheaders_install.txt29 ARCH indicates which architecture to produce headers for, and defaults to the
30 current architecture. The linux/asm directory of the exported kernel headers
44 who create an architecture-independent tarball from the resulting include
/Linux-v4.19/Documentation/timers/
Dhighres.txt46 code out of the architecture-specific areas into a generic management
47 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
73 for various event driven functionalities is hardwired into the architecture
77 architecture. Another implication of the current design is that it is necessary
78 to touch all the architecture-specific implementations in order to provide new
84 to minimize the clock event related architecture dependent code to the pure
90 Clock event devices are registered either by the architecture dependent boot
112 architecture specific timer interrupt handlers and hands the control over the
127 The conversion of an architecture has no functional impact, but allows to
131 adding the kernel/time/Kconfig file to the architecture specific Kconfig and
/Linux-v4.19/Documentation/devicetree/bindings/powerpc/fsl/
Dcpus.txt17 Freescale Power Architecture) defines the architecture for Freescale
18 Power CPUs. The EREF defines some architecture categories not defined
/Linux-v4.19/Documentation/core-api/
Dgenericirq.rst22 interrupt subsystem based for their architecture, with the help of the
67 Analysing a couple of architecture's IRQ subsystem implementations
81 and extensible. For example, an (sub)architecture can use a generic
83 (sub)architecture specific 'edge type' implementation.
118 Whenever an interrupt triggers, the low-level architecture code calls
171 The interrupt flow handlers (either pre-defined or architecture
172 specific) are assigned to specific interrupts by the architecture either
319 which have no platform-specific IRQ handling quirks. If an architecture
383 The locking of chip registers is up to the architecture that defines the
/Linux-v4.19/drivers/clk/bcm/
DKconfig8 based on the ARM architecture
23 based on the iProc architecture
/Linux-v4.19/tools/testing/selftests/x86/
Dtrivial_32bit_program.c8 # error wrong architecture
Dtrivial_64bit_program.c8 # error wrong architecture
/Linux-v4.19/include/asm-generic/
Dspinlock.h9 #error need an architecture specific asm/spinlock.h
Dpgalloc.h8 #error need to implement an architecture specific asm/pgalloc.h
Dtlbflush.h10 #error need to implement an architecture specific asm/tlbflush.h
/Linux-v4.19/Documentation/x86/x86_64/
Dmachinecheck79 For more details about the x86 machine check architecture
80 see the Intel and AMD architecture manuals from their developer websites.
82 For more details about the architecture see

12345678910>>...14