| /linux-2.6.39/kernel/ |
| D | latencytop.c | 104 int q, same = 1; in account_global_scheduler_latency() local
116 same = 0; in account_global_scheduler_latency()
124 if (same) { in account_global_scheduler_latency()
199 int same = 1; in __account_scheduler_latency() local
206 same = 0; in __account_scheduler_latency()
214 if (same) { in __account_scheduler_latency()
|
| /linux-2.6.39/arch/cris/arch-v10/ |
| D | Kconfig | 76 set this to same as CONFIG_ETRAX_LED1G (normally 2).
86 set this to same as CONFIG_ETRAX_LED1G (normally 2).
96 set this to same as CONFIG_ETRAX_LED1G (normally 2).
105 set this to same as CONFIG_ETRAX_LED1G (normally 2).
114 set this to same as CONFIG_ETRAX_LED1G (normally 2).
123 set this to same as CONFIG_ETRAX_LED1G (normally 2).
132 set this to same as CONFIG_ETRAX_LED1G (normally 2).
141 set this to same as CONFIG_ETRAX_LED1G (normally 2).
150 set this to same as CONFIG_ETRAX_LED1G (normally 2).
159 set this to same as CONFIG_ETRAX_LED1G (normally 2).
[all …]
|
| /linux-2.6.39/Documentation/usb/ |
| D | persist.txt | 19 has no way to know what has actually happened. Perhaps the same
32 system woke up, who cares? It'll still work the same when you type on
36 devices. The effect is exactly the same as if the device really had
44 interrupts a power session will have the same effect. For example,
79 same thing that happens whenever a USB device is reset.) If the
81 same descriptors as before, including the Vendor and Product IDs, then
82 the kernel continues to use the same device structure. In effect, the
86 The same thing happens if the host controller is in the expected state
120 have the same persistent volume associated with the device. As such
136 to make sure the USB device hasn't been changed; that is, the same
[all …]
|
| /linux-2.6.39/Documentation/namespaces/ |
| D | compatibility-list.txt | 30 words, user 10 in one user namespace shouldn't have the same
34 The same is true for the IPC namespaces being shared - two users
35 from different user namespaces should not access the same IPC objects
|
| /linux-2.6.39/drivers/staging/bcm/ |
| D | TODO | 5 Is it possible to use same API as Intel Wimax stack and
6 have same user level components.
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 8 namespace active multiple devices with the same name can show up in
9 the same directory, ouch!
12 namespaces to see the same interface that is currently presented in
|
| D | isofs.txt | 1 Mount options that are the same as for msdos and vfat partitions.
7 Mount options that are the same as vfat partitions. These are only useful
21 check=strict Matches only filenames with the exact same case
|
| /linux-2.6.39/Documentation/power/ |
| D | swsusp-and-swap-files.txt | 4 The Linux kernel handles swap files almost in the same way as it handles swap
42 by the same application that determines the swap file's header offset using the
53 Now, swsusp will use the swap file in the same way in which it would use a swap
58 the location of its header need not be the same as before. Thus every time
|
| /linux-2.6.39/Documentation/video4linux/bttv/ |
| D | README.quirks | 6 The vsfx insmod option does the same for EN_VSFX bit. If you have
43 (1) Deassert REQ at the same time as asserting FRAME.
61 responsibility to remove its request at the same time. It is the
73 during the same cycle that GNT is de-asserted. This is non PCI 2.1
78 transaction from starting the same cycle as GNT is de-asserted. This
|
| /linux-2.6.39/scripts/coccinelle/tests/ |
| D | doublebitand.cocci | 1 /// Find bit operations that include the same argument more than once
5 //# same structure as other similar expressions
|
| /linux-2.6.39/Documentation/ |
| D | sgi-ioc4.txt | 9 they can't all register to own the same PCI device ID. To make
29 IOC4 function probe and remove operations isn't precisely the same
31 same operation.
|
| D | bus-virt-phys-mapping.txt | 33 external hardware sees the memory the same way.
35 Now, on normal PCs the bus address is exactly the same as the physical
37 because the memory and the devices share the same address space, and that is
47 Now, that looks simple enough. However, when you look at the same thing from
61 where all the addresses actually point to the same thing. It's just seen
71 are the same).
139 conceptually in the same memory space as "real memory" at all, so you cannot
140 just dereference a pointer. (Sadly, on x86 it _is_ in the same memory space,
|
| D | prio_tree.txt | 22 to handle many vmas with the same vm_pgoff. Such vmas are handled in
23 2 different ways: 1) All vmas with the same radix _and_ heap indices are
24 linked using vm_set.list, 2) if there are many vmas with the same radix
31 the same vm_pgoff (radix_index) and if necessary we build different
94 same start_vm_pgoff but different end_vm_pgoffs. Therefore, we normally
|
| D | devices.txt | 60 Second, please include a description of the device *in the same format
288 Partitions are handled in the same way as for IDE
501 Partitions are handled in the same way as IDE disks
593 Partitions are handled the same way as for IDE disks
604 Partitions are handled the same way as for the first
712 Partitions are handled in the same way as for IDE
800 Partitions are handled the same way as for the first
818 Partitions are handled the same way as for the first
851 Partitions are handled in the same way as IDE disks
951 Partitions are handled in the same way as for IDE
[all …]
|
| D | spinlocks.txt | 17 essentially is just the same as doing
52 at the same time on two different CPU's. That's fine per se, but the
80 readers to be in the same critical region at once, but if somebody wants
87 The routines look the same as above:
139 guarantee the same kind of exclusive access, and it will be much faster.
153 interrupt happens on the same CPU that already holds the lock, because the
|
| /linux-2.6.39/drivers/gpu/vga/ |
| D | Kconfig | 6 Some "legacy" VGA devices implemented on PCI typically have the same
8 are accessed at same time they need some kind of coordination. Please
|
| /linux-2.6.39/Documentation/sparc/ |
| D | README-2.5 | 9 part, too). It allows to boot the same kernel at different
26 in the same way as other architectures do bootstraps.
30 1. Hackers must type "make image" now, instead of just "make", in the same
|
| /linux-2.6.39/arch/m68k/fpsp040/ |
| D | sacos.S | 5 | an input argument; sAcosd does the same except for denormalized
42 | file, README, in this same directory.
|
| /linux-2.6.39/Documentation/ia64/ |
| D | README | 10 - IA-64 kernel installation is the same as the other platforms, see
23 Configuration is the same, see original README for details.
|
| /linux-2.6.39/Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi | 26 Multiple entries of the same type are allowed. In order
30 to say, if there are 'N' multiple entries with the same type
68 type : The type of the entry. This value is the same
73 given type. This value is the same as found
|
| /linux-2.6.39/Documentation/i2c/busses/ |
| D | i2c-parport | 11 * video/i2c-parport (NOT the same as this one, dedicated to home brew
83 all connected lines MUST BE driven at the same state, else you'll short
129 If possible, you should use the same pinout configuration as existing
136 This driver is NOT the same as the i2c-pport driver found in the i2c
141 This driver is also NOT the same as the i2c-pcf-epp driver found in the
|
| /linux-2.6.39/Documentation/isdn/ |
| D | README.icn | 22 all cards are mapped to the same window and activated as needed.
88 maps all cards into the same address-space.
105 where p, m, idstring1 and idstring2 have the same meanings as the
113 Using the "icnctrl"-utility, the same features apply to the modularized
139 To load a 4B-card, the same command is used, except a second firmware
|
| /linux-2.6.39/arch/x86/kernel/ |
| D | trampoline_64.S | 43 mov %cs, %ax # Code and data in the same place
132 # Careful these need to be in the same 64K segment as the above;
|
| /linux-2.6.39/Documentation/scsi/ |
| D | g_NCR5380.txt | 11 modes at a time but it does support both of these chips at the same time.
13 the same time. It should be able to handle multiple different cards in the
14 same machine.
|
| /linux-2.6.39/Documentation/vm/ |
| D | numa | 31 attached to the same cell will experience faster access times and higher
39 [cache misses] to be to "local" memory--memory on the same cell, if any--or
57 a given node will see the same local memory access times and bandwidth.
79 fall back to the same zone type on a different node, or to a different zone
80 type on the same node. This is an important consideration because some zones,
124 closest available memory. This is a consequence of the same mechanism that
148 specified CPU. Again, this is the same node from which default, local page
|