Home
last modified time | relevance | path

Searched full:separate (Results 1 – 25 of 1170) sorted by relevance

12345678910>>...47

/linux-3.3/scripts/
Dcheckkconfigsymbols.sh24 split(combIdx, separate, SUBSEP);
26 if (! ( (separate[1], separate[2]) in map ) )
28 symb=separate[1];
/linux-3.3/firmware/
DREADME.AddingFirmware13 place to add those is the separate linux-firmware repository:
20 been permitted to redistribute under separate cover.
30 permitted to include it in a separate file and refer to it from the
/linux-3.3/Documentation/kbuild/
Dmodules.txt12 --- 2.4 Building Separate Files
15 --- 3.2 Separate Kbuild file and Makefile
133 --- 2.4 Building Separate Files
204 The check for KERNELRELEASE is used to separate the two parts
212 --- 3.2 Separate Kbuild File and Makefile
237 off to separate the kbuild part from the rest.
267 split into separate files.
330 External modules tend to place header files in a separate
417 locate modules for a specific functionality in a separate
/linux-3.3/Documentation/timers/
Dhrtimers.txt61 (e.g. multimedia) can benefit from the availability of a separate
69 separate the "timeout" and "precise timer" subsystems.
96 a separate list is used to give the expiry code fast access to the
99 (This separate list is also useful for later when we'll introduce
100 high-resolution clocks, where we need separate pending and expired
/linux-3.3/Documentation/devicetree/bindings/arm/
Dl2cc.txt3 ARM cores often have a separate level 2 cache controller. There are various
25 should use 0. Controllers without separate read and write Tag RAM latency
/linux-3.3/fs/jffs2/
DTODO23 - Split writes so they go to two separate blocks rather than just c->nextblock.
25 nodes to a different one, we can separate clean nodes from those which
/linux-3.3/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars11 into separate namespaces through the use of a vendor
16 creates a separate directory for each one found. Each
/linux-3.3/sound/usb/6fire/
Dpcm.h32 /* BEGIN DO NOT SEPARATE */
35 /* END DO NOT SEPARATE */
/linux-3.3/arch/powerpc/include/asm/
Dpte-hash64.h14 * We could create separate kernel read-only if we used the 3 PP bits
30 /* No separate kernel read-only */
/linux-3.3/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt17 newer version where there is a separate PLL and clock divider for the
18 ARM core is available as a separate driver.
/linux-3.3/Documentation/ia64/
Dmca.txt85 [1] My (Keith Owens) original design called for ia64 to separate its
90 Mosberger vetoed that approach. Which meant that separate kernel
91 stacks meant separate "tasks" for the MCA/INIT handlers.
131 * x86 has a separate struct task which points to one of multiple kernel
/linux-3.3/arch/sh/
DKconfig.debug42 bool "Use separate kernel stacks when processing interrupts"
45 If you say Y here the kernel will use separate kernel stacks
/linux-3.3/kernel/irq/
Dgeneric-chip.c36 * Chip has separate enable/disable registers instead of a single mask
90 * Chip has separate enable/disable registers instead of a single mask
166 * configured in a separate register and the wakeup active state is
218 * Separate lockdep class for interrupt chip which can nest irq_desc
/linux-3.3/fs/xfs/
DKconfig59 separate area of disk space where only file data is stored. It was
63 separated. Regular file I/Os are isolated to a separate device
/linux-3.3/arch/ia64/include/asm/
Dpci.h33 * Platforms with separate bus address spaces _must_ turn this off and provide
37 * For now, the ia64 platforms which may have separate/multiple bus address
/linux-3.3/Documentation/i2c/busses/
Di2c-ali15x366 The M1533/M1543C devices appear as FOUR separate devices on the PCI bus. An
87 just enable the SMB alone. The SMB and the ACPI have separate I/O spaces.
/linux-3.3/drivers/mtd/maps/
Dscb2_flash.c33 * another separate (*.bbo) binary file. The 10 files are 64k of data + a
36 * separate .bbo file also has a small header. It is the 'Boot Block'
43 * Intel's BIOS update program flashes the BIOS and Boot Block in separate
/linux-3.3/Documentation/input/
Devent-codes.txt7 used to separate input events into packets of input data changes occurring at
27 - Used as markers to separate events. Events may be separated in time or in
76 - Used to synchronize and separate events into packets of input data changes
85 - Used to synchronize and separate touch events. See the
/linux-3.3/Documentation/RCU/
Dlockdep.txt23 In addition, a separate kernel config parameter CONFIG_PROVE_RCU enables
106 being in an RCU read-side critical section. In the future, separate
/linux-3.3/arch/sh/include/asm/
Dpgtable.h101 * not only supporting separate execute, read, and write bits, but having
102 * completely separate permission bits for user and kernel space.
/linux-3.3/arch/powerpc/kernel/
De500-pmu.c54 * does not have separate read/write events (but it does have
55 * separate instruction/data events).
/linux-3.3/drivers/ata/
Dpata_optidma.c234 * The libata core provides separate functions for handling PIO and
249 * The libata core provides separate functions for handling PIO and
264 * The libata core provides separate functions for handling PIO and
279 * The libata core provides separate functions for handling PIO and
/linux-3.3/arch/m68k/include/asm/
Dm54xxacr.h29 #define CACR_EUSP 0x00000020 /* Enable separate user a7 */
69 * Version 4 cores have a true harvard style separate instruction
/linux-3.3/Documentation/filesystems/
Dubifs.txt8 Ext2, XFS, JFS, etc. UBIFS represents a separate class of file-systems
35 UBIFS works on top of UBI. UBI is a separate software layer which may be
/linux-3.3/fs/befs/
DTODO12 * See if we really need separate types for on-disk and in-memory

12345678910>>...47