Searched refs:these (Results 1 – 25 of 881) sorted by relevance
12345678910>>...36
| /linux-3.4.99/Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
40 some of these interfaces, giving a schedule for when they will
47 Every file in these directories will contain the following information:
59 important to get feedback for these interfaces to make
|
| /linux-3.4.99/fs/jffs2/ |
| D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /linux-3.4.99/drivers/scsi/arm/ |
| D | Kconfig | 10 Acorn system with one of these, say Y. If unsure, say N.
50 Acorn system with one of these, say Y. If unsure, say N.
57 system with one of these, say Y, otherwise say N.
64 you have one of these, say Y. If unsure, say N.
75 Acorn system with one of these, say Y. If unsure, say N.
83 system with one of these, say Y. If unsure, say N.
|
| /linux-3.4.99/Documentation/ |
| D | Intel-IOMMU.txt | 29 PS2 emulation. The regions of memory used for these devices are marked
31 regions will fail. Hence BIOS uses RMRR to specify these regions along with
32 devices that need to access these regions. OS is expected to setup
33 unity mappings for these regions for these devices to access these regions.
48 but these are not global address spaces, but separate for each domain.
|
| D | sgi-ioc4.txt | 8 standpoint is that all these functions share a single IRQ, and
11 themselves) present in IOC4 are mixed-purpose between these several
28 by the core driver at appropriate times. The interface of these
|
| D | memory.txt | 5 a certain quantity of memory. If you have one of these
10 All of these problems can be addressed with the "mem=XXXM" boot option
|
| /linux-3.4.99/Documentation/arm/OMAP/ |
| D | omap_pm | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
66 As the 'pdata' in the above examples indicates, these functions are
72 not support these functions should leave these function pointers set
78 The most common usage of these functions will probably be to specify
114 frequency. The OMAP PM interface contains functions for these
141 in these cases, the board file needs to do additional steps as follows:
|
| /linux-3.4.99/arch/mips/jazz/ |
| D | Kconfig | 8 kernel that runs on these, say Y here. For details about Linux on
20 kernel that runs on these, say Y here. For details about Linux on
31 kernel that runs on these, say Y here. For details about Linux on
|
| /linux-3.4.99/tools/perf/Documentation/ |
| D | perf-diff.txt | 36 Only consider symbols in these dsos. CSV that understands
41 Only consider symbols in these comms. CSV that understands
46 Only consider these symbols. CSV that understands
|
| /linux-3.4.99/Documentation/sh/ |
| D | register-banks.txt | 18 in mind when writing code that utilizes these banked registers, for obvious
19 reasons. Userspace is also not able to poke at the bank1 values, so these can
22 Presently the kernel uses several of these registers.
|
| /linux-3.4.99/arch/m68k/ifpsp060/src/ |
| D | README-SRC | 9 You don't need to actually assemble these files in order to compile a
11 are sufficient and were generated from these source files by
|
| /linux-3.4.99/fs/nls/ |
| D | Kconfig | 45 codepage if you want to be able to read/write these filenames on
57 codepage if you want to be able to read/write these filenames on
69 codepage if you want to be able to read/write these filenames on
82 codepage if you want to be able to read/write these filenames on
98 codepage if you want to be able to read/write these filenames on
103 characters for these languages: Albanian, Croatian, Czech, English,
113 codepage if you want to be able to read/write these filenames on
124 codepage if you want to be able to read/write these filenames on
135 codepage if you want to be able to read/write these filenames on
146 codepage if you want to be able to read/write these filenames on
[all …]
|
| /linux-3.4.99/Documentation/video4linux/bttv/ |
| D | README.quirks | 7 stability problems you can try if one of these options makes your box
10 drivers/pci/quirks.c knows about these issues, this way these bits are
74 compliant. To ensure compatibility when using PCs with these PCI
81 query for these non-compliant devices, and set the EN_VSFX bit only if
|
| D | Sound-FAQ | 45 these pins. One register is the output enable register
48 you can get/set the status if these pins. They can be used for input
51 Most grabber board vendors use these pins to control an external chip
59 line for your board. The important fields are these two:
70 (BT848_GPIO_OUT_EN) will be set as these pins must be driven by the
81 card installed, you might to check out if you can read these registers
|
| /linux-3.4.99/Documentation/hwmon/ |
| D | asb100 | 17 supply a datasheet for these chips. Thanks go to many people who helped
26 these, the ASB100-A also implements a single PWM controller for fans 2 and
64 (2) The min and max registers for these values appear to
|
| D | abituguru | 27 this doesnot always work. For these uGuru's the autodection can
31 You may also need to specify the fan_sensors option for these boards
33 2) There is a separate abituguru3 driver for these motherboards,
34 the abituguru (without the 3 !) driver will not work on these
|
| D | ucd9000 | 31 interrupts, cascading, or other system functions. Twelve of these pins offer PWM
32 functionality. Using these pins, the UCD90124 offers support for fan control,
39 functions. Ten of these pins offer PWM functionality. Using these pins, the
|
| /linux-3.4.99/Documentation/RCU/ |
| D | rcu.txt | 22 barriers. The fact that these operations are quite expensive
32 Therefore, as soon as a CPU is seen passing through any of these
45 by sampling these counters.
76 Of these, one was allowed to lapse by the assignee, and the
94 o What are all these files in this directory?
|
| /linux-3.4.99/Documentation/arm/Samsung/ |
| D | GPIO.txt | 15 about these devices. Their implementation is being brought into line
40 on these functions.
|
| /linux-3.4.99/Documentation/i2c/busses/ |
| D | i2c-sis96x | 7 Any combination of these host bridges:
9 and these south bridges:
24 The command "lspci" as root should produce something like these lines:
|
| D | i2c-sis5595 | 17 Note: these chips contain a 0008 device which is incompatible with the
18 5595. We recognize these by the presence of the listed
|
| /linux-3.4.99/Documentation/power/regulator/ |
| D | design.txt | 18 specific knowledge that these changes are safe to do perform on
31 => The consumer API should be structured so that these use cases are
|
| /linux-3.4.99/drivers/staging/wlags49_h2/ |
| D | hcfdef.h | 248 err: these values should match;
252 err: these values should match;
655 err: someone redefined these macros while the implemenation assumes they are equal;
659 err: someone redefined these macros while the implemenation assumes they are equal;
663 err: someone redefined these macros while the implemenation assumes they are equal;
|
| /linux-3.4.99/Documentation/video4linux/ |
| D | cpia2_overview.txt | 14 mappings for the two chips. In these cases, the symbols defined in the
20 try to make note of all of these cases.
31 of these registers and the possible values for most of them.
|
| /linux-3.4.99/arch/arm/mach-vexpress/ |
| D | Kconfig | 48 You must boot using a Flattened Device Tree in order to use these
50 these boards with this option.
|
12345678910>>...36