Searched refs:architecture (Results 1 – 25 of 199) sorted by relevance
12345678
| /linux-3.4.99/Documentation/ |
| D | irqflags-tracing.txt | 13 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
17 architecture support for this is certainly not in the "trivial"
19 state changes. But an architecture can be irq-flags-tracing enabled in a
47 - if the architecture has non-maskable interrupts then those need to be
52 implementation in an architecture: lockdep will detect that and will
|
| D | cputopology.txt | 8 socket number, but the actual value is architecture and platform
15 architecture and platform dependent.
21 architecture and platform dependent.
38 To implement it in an architecture-neutral way, a new source file,
42 For an architecture to support this feature, it must define some of
|
| D | 00-INDEX | 68 - directory with info about Linux on the ARM architecture.
110 - directory with info about Linux on CRIS architecture.
162 - directory with info about Linux on Intel 32 bit architecture.
164 - directory with info about Linux on Intel 64 bit architecture.
218 - directory with info about Linux on Motorola 68k architecture.
232 - directory with info about Linux on MIPS architecture.
256 - directory with info on using Linux on PA-RISC architecture.
308 - directory with info on porting Linux to a new architecture.
312 - directory with info on using Linux on Sparc architecture.
|
| D | local_ops.txt | 7 to implement them for any given architecture and shows how they can be used
33 * Implementation for a given architecture
37 i386 and x86_64) and any SMP synchronization barrier. If the architecture does
39 in your architecture's local.h is sufficient.
|
| /linux-3.4.99/Documentation/frv/ |
| D | README.txt | 5 This directory contains documentation for the Fujitsu FR-V CPU architecture
12 A description of the basic features inherent in this architecture port.
17 A summary of the configuration options particular to this architecture.
|
| /linux-3.4.99/arch/mips/jazz/ |
| D | Kconfig | 9 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
21 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
32 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
|
| /linux-3.4.99/Documentation/ABI/stable/ |
| D | syscalls | 7 Note that this interface is different for every architecture
8 that Linux supports. Please see the architecture-specific
|
| /linux-3.4.99/Documentation/usb/ |
| D | linux.inf | 19 ; Decoration for x86 architecture
23 ; Decoration for x64 architecture
27 ; Decoration for ia64 architecture
|
| /linux-3.4.99/Documentation/make/ |
| D | headers_install.txt | 29 ARCH indicates which architecture to produce headers for, and defaults to the
30 current architecture. The linux/asm directory of the exported kernel headers
41 who create an architecture-independent tarball from the resulting include
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 26 itself architecture dependent.
29 is itself architecture dependent.
75 architecture specific.
79 is architecture specific.
127 The actual value is architecture and platform dependent.
137 is architecture and platform dependent.
|
| /linux-3.4.99/Documentation/timers/ |
| D | highres.txt | 46 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-3.4.99/arch/arm/mach-mmp/ |
| D | Kconfig | 59 ARMv7 architecture.
70 ARMv7 architecture.
81 ARMv7 architecture.
|
| /linux-3.4.99/include/asm-generic/ |
| D | spinlock.h | 8 #error need an architecture specific asm/spinlock.h
|
| D | pgalloc.h | 7 #error need to implement an architecture specific asm/pgalloc.h
|
| D | tlbflush.h | 9 #error need to implement an architecture specific asm/tlbflush.h
|
| /linux-3.4.99/Documentation/kbuild/ |
| D | kbuild.txt | 79 deb-pkg. Normally deb-pkg attempts to guess the right architecture based on
82 architecture.
86 Set ARCH to the architecture to be built.
87 In most cases the name of the architecture is the same as the
123 The implementation of "make install" is architecture specific
|
| /linux-3.4.99/Documentation/x86/x86_64/ |
| D | machinecheck | 79 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
|
| /linux-3.4.99/Documentation/networking/ |
| D | packet_mmap.txt | 236 the PACKET_MMAP buffer could hold only 32768 frames in a 32 bit architecture or
237 16384 in a 64 bit architecture. For information on these kernel versions
254 In a i386 architecture PAGE_SIZE is 4096 bytes
259 respectively, with an i386 architecture.
293 In a 2.4/2.6 kernel and the i386 architecture, the limit is 131072 bytes. The
297 In a 32 bit architecture, pointers are 4 bytes long, so the total number of
309 <pointer size>: depends on the architecture -- sizeof(void *)
310 <page size> : depends on the architecture -- PAGE_SIZE or getpagesize (2)
328 i386 architecture:
344 Actually, this buffer size is not possible with an i386 architecture.
|
| /linux-3.4.99/arch/xtensa/include/asm/ |
| D | bitops.h | 26 # error SMP not supported on this architecture
|
| /linux-3.4.99/arch/tile/include/arch/ |
| D | abi.h | 40 # error Unrecognized architecture with __need_int_reg_t
|
| /linux-3.4.99/Documentation/isdn/ |
| D | README.mISDN | 2 the old I4L driver architecture for passiv ISDN cards.
|
| /linux-3.4.99/Documentation/scheduler/ |
| D | 00-INDEX | 4 - CPU Scheduler implementation hints for architecture specific code.
|
| /linux-3.4.99/arch/openrisc/ |
| D | README.openrisc | 5 target architecture, specifically, is the 32-bit OpenRISC 1000 family (or1k).
77 initial port of linux to OpenRISC/or32 architecture.
|
| /linux-3.4.99/drivers/staging/usbip/userspace/ |
| D | INSTALL | 92 same time, by placing the object files for each architecture in their
99 architecture at a time in the source code directory. After you have
100 installed the package for one architecture, use `make distclean' before
101 reconfiguring for another architecture.
112 architecture-specific files and architecture-independent files. If you
|
| /linux-3.4.99/Documentation/scsi/ |
| D | ufs.txt | 45 UFS has a layered communication architecture which is based on SCSI
48 UFS communication architecture consists of following layers,
83 UIC is the lowest layer of UFS layered architecture. It handles
|
12345678