| /linux-4.4.14/security/smack/ |
| D | smack_access.c | 93 int may = -ENOENT; in smk_access_entry() local
99 may = srp->smk_access; in smk_access_entry()
107 if ((may & MAY_WRITE) == MAY_WRITE) in smk_access_entry()
108 may |= MAY_LOCK; in smk_access_entry()
109 return may; in smk_access_entry()
128 int may = MAY_NOT; in smk_access() local
178 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access()
182 if (may <= 0 || (request & may) != request) { in smk_access()
192 if (may & MAY_BRINGUP) in smk_access()
232 int may; in smk_tskacc() local
[all …]
|
| D | smack_lsm.c | 1025 int may; in smack_inode_init_security() local
1032 may = smk_access_entry(skp->smk_known, dsp->smk_known, in smack_inode_init_security()
1042 if (may > 0 && ((may & MAY_TRANSMUTE) != 0) && in smack_inode_init_security()
1717 int may; in smack_mmap_file() local
1751 may = smk_access_entry(srp->smk_subject->smk_known, in smack_mmap_file()
1754 if (may == -ENOENT) in smack_mmap_file()
1755 may = srp->smk_access; in smack_mmap_file()
1757 may &= srp->smk_access; in smack_mmap_file()
1762 if (may == 0) in smack_mmap_file()
1790 if ((may | mmay) != mmay) { in smack_mmap_file()
[all …]
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | fpsp.doc | 206 may exit through _060_real_inex <---|
208 may exit through _060_real_ovfl <---|
210 may exit through _060_fpsp_done <---|
218 may exit through _060_real_inex <---|
220 may exit through _060_real_unfl <---|
222 may exit through _060_fpsp_done <---|
253 |----> may exit through _060_real_trace
255 |----> may exit through _060_real_trap
257 |----> may exit through _060_real_bsun
259 |----> may exit through _060_fpsp_done
[all …]
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 27 timekeeping which may be difficult to find elsewhere, specifically,
267 the APIC CPU-local memory-mapped hardware. Beware that CPU errata may affect
268 the use of the APIC and that workarounds may be required. In addition, some of
271 functionality that may be more computationally expensive to implement.
284 systems designated as legacy free may support only the HPET as a hardware timer
303 timing chips built into the cards which may have registers which are accessible
346 platforms, the TSCs of different CPUs may start at different times depending
350 The BIOS may attempt to resynchronize the TSCs during the poweron process and
351 the operating system or other system software may attempt to do this as well.
353 write the full 64-bits of the TSC, it may be impossible to match the TSC in
[all …]
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.diversion | 5 document. The diversion services may be used with all cards supported by
45 only supported by isdn phones. Incoming calls may be diverted
48 The diversions may be invoked statically in the providers exchange
51 forwarding reason is met. Activated static services may also be
56 In this case all incoming calls are checked by rules that may be
64 Actions that may be invoked by a rule are ignore, proceed, reject,
77 driver for passive isdn cards. All HiSax supported cards may be used for
80 CFU, CFNR, CFB activated on an MSN-line. The static services may not be
84 not supported but may use the tty devices for this purpose.
85 The dynamic diversion services may be used in all countries if the provider
[all …]
|
| D | README.hfc-pci | 1 The driver for the HFC-PCI and HFC-PCI-A chips from CCD may be used
5 may be logged.
23 If more than one HFC-PCI cards are installed, a specific card may be selected
32 0xd000 you may give the parameters type=35,35,35 io=0xdc00,0xd400,0xd00
36 invoked which may not give the wanted result.
|
| D | README.hysdn | 46 the active cards submenu. The driver may only be compiled and used if
53 and firmware may be fetched from Hypercopes WWW-Site www.hypercope.de.
88 This file may be read to get by everyone to get info about the cards type,
121 config lines may be copied to this file.
138 Additional info about error reasons may be fetched from the log output.
142 The cardlogX file entry may be opened multiple for reading by everyone to
145 The driver log data may be redirected to the syslog by selecting the
149 A root user may write a decimal or hex (with 0x) value t this file to select
|
| D | INTERFACE.CAPI | 44 From then on, Kernel CAPI may call the registered callback functions for the
62 application may be passed to the driver for the device via calls to the
63 send_message() callback function. Conversely, the driver may call Kernel
70 messages for that application may be passed to or from the device anymore.
87 a callback function pointer (may be NULL)
116 The function may return before the operation has completed.
124 The function may return before the operation has completed.
141 of the skb and the caller may no longer access it. If it returns a
143 who may reuse or free it.
190 parameter may be omitted by setting the length field of the CAPI message to 22
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 7 MSIs were originally specified by PCI (and are used with PCIe), but may also be
16 Devices may be configured by software to write to arbitrary doorbells which
17 they can address. An MSI controller may feature a number of doorbells.
21 Devices may be configured to write an arbitrary payload chosen by software.
22 MSI controllers may have restrictions on permitted payloads.
35 address by some master. An MSI controller may feature a number of doorbells.
58 generate, the doorbell and payload may be configured, though sideband
59 information may not be configurable.
67 This property is unordered, and MSIs may be allocated from any combination of
|
| D | cdns,xtensa-pic.txt | 7 It may be either 1 or 2.
12 core variants it may be mapped to different internal IRQ.
13 IRQ sensitivity and priority are fixed for each core variant and may not be
|
| /linux-4.4.14/Documentation/security/ |
| D | credentials.txt | 37 Objects are things in the system that may be acted upon directly by
63 indicates the 'objective context' of that object. This may or may not be
78 Objects other than tasks may under some circumstances also be subjects.
79 For instance an open file may send SIGIO to a task using the UID and EUID
97 Linux has a number of actions available that a subject may perform upon an
118 file may supply more than one ACL.
122 'group' and 'other'), each of which may be granted certain privileges
132 The system as a whole may have one or more sets of rules that get
187 The inheritable capabilities are the ones that may get passed across
190 The bounding set limits the capabilities that may be inherited across
[all …]
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 13 Log entries may be purged by the service processor
20 the only remaining copy of a log message may be in
26 The service processor may be able to store more log
28 an event from Linux you may instantly get another one
33 user space to solve the problem. In future, we may
47 In the future there may be additional types.
|
| D | sysfs-class-ubi | 31 device may have many UBI volumes)
38 Amount of available logical eraseblock. For example, one may
70 Maximum logical eraseblock size this UBI device may provide. UBI
71 volumes may have smaller logical eraseblock size because of their
86 Maximum number of volumes which this UBI device may have.
93 Minimum input/output unit size. All the I/O may only be done
202 at the moment of the update was interrupted. The later may be
|
| /linux-4.4.14/drivers/atm/ |
| D | Kconfig | 60 Note that extended debugging may create certain race conditions
72 chipsets. However, in some cases, large bursts may overrun buffers
79 may increase the cost of setting up a transfer such that the
91 Burst sixteen words at once in the send direction. This may work
105 Burst four words at once in the send direction. You may want to try
107 may or may not improve throughput.
113 Burst two words at once in the send direction. You may want to try
115 are also set may or may not improve throughput.
121 Burst sixteen words at once in the receive direction. This may work
128 Burst eight words at once in the receive direction. This may work
[all …]
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | Introduction | 56 The modular sound drivers may be loaded via insmod or modprobe.
78 The ALSA drivers support some newer hardware that may not
82 2. The commercial OSS driver may be obtained from the site:
83 http://www.opensound.com. This may be used for cards that
84 are unsupported by the kernel driver, or may be used
87 3. The enlightenment sound daemon may be used for playing
91 The "esd" program may be used with the real-player and mpeg
129 If the sound card is an ISA PnP card, isapnp may be used
146 modules may then be loaded (most require parameters). For example,
184 The status of sound may be read/checked by:
[all …]
|
| D | PAS16 | 31 when answering to these questions since answering y to a question may
34 configuration may also be made modular by answering m to configuration
37 Note also that all questions may not be asked. The configuration program
38 may disable some questions depending on the earlier choices. It may also
118 cards may have software (TSR) FM emulation. Enabling FM support with
119 these cards may cause trouble (I don't currently know of any such
154 irq of 10 and dma of 3 may not match your installation. The above
160 If sound is built totally modular, the above options may be
|
| D | oss-parameters.txt | 7 This document may not be entirely up to date and comprehensive. The command
11 parameters may be changed at runtime by the command
|
| /linux-4.4.14/Documentation/thermal/ |
| D | nouveau_thermal | 16 cannot access any of the i2c external monitoring chips it may find. If you
18 interface is likely not to work. This document may then not cover your situation
34 WARNING: Some of these thresholds may not be used by Nouveau depending
59 You may also have the following attribute:
72 [PWM_min, PWM_max] range, the reported fan speed (RPM) may not be accurate
78 Thermal management on Nouveau is new and may not work on all cards. If you have
|
| D | power_allocator.txt | 70 simply an estimate, and may be tuned to affect the aggressiveness of
72 is typically 2000mW, while on a 10" tablet is around 4500mW (may vary
113 whilst temperature is low, and may lead to temperature overshooting.
215 cooling device can set. It is a function because this conversion may
216 depend on external factors that may change so this function should the
227 useful in heterogeneous systems where two cooling devices may perform
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | core_locking.txt | 11 all of the methods in struct ib_device may sleep. The exceptions
25 which may not sleep and must be callable from any context.
61 some serialization may be required to get sensible results. For
62 example, a consumer may safely call ib_poll_cq() on multiple CPUs
94 may be process context, softirq context, or interrupt context.
95 Upper level protocol consumers may not sleep in a callback.
109 An upper level protocol consumer may begin using an IB device as
|
| /linux-4.4.14/Documentation/networking/ |
| D | cxgb.txt | 51 You may set the timer latency after disabling adaptive-rx:
59 You may also provide a timer latency value while disabling adaptive-rx:
100 parameters for "performance tuning" an what value to use. You may or may not
106 Your distribution may have a different way of doing things, or you may prefer
111 your system. You may want to write a script that runs at boot-up which
159 receiver. Due to the variations of RTT, you may want to increase the buffer
170 The receive buffer (RX_WINDOW) size may be calculated the same as single
174 not supported on the machine. Experimentation may be necessary to attain
185 may be found in /var/log/messages.
211 controller may be bound to more than one CPU. This will cause TCP
[all …]
|
| D | ixgb.txt | 149 dropped receives, this value may be set too high, causing the driver to
188 behavior after modifying this register may be undefined (possibly errors of
190 back to 22 (setpci -d 8086:1a48 e6.b=22) may be required to get back to a
211 # some of the defaults may be different for your kernel
214 # several network benchmark tests, your mileage may vary
342 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4
345 The CRC errors may be received either by the Intel(R) PRO/10GbE CX4
347 cable assembly may resolve the issue.
352 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4 Server
354 (1 m or shorter). If this situation occurs, using a longer cable may resolve
[all …]
|
| D | LICENSE.qla3xxx | 4 This program includes a device driver for Linux 2.6 that may be
6 You may modify and redistribute the device driver code under the
10 You may redistribute the hardware specific firmware binary file
22 3. The name of QLogic Corporation may not be used to
|
| D | e1000.txt | 134 and may improve small packet latency, but is generally not suitable
145 greater than 75,000, may hang (stop transmitting) adapters
154 are in use simultaneously, the CPU utilization may increase non-
184 for a higher number of receive descriptors may be denied. In this
197 may be set too high, causing the driver to run out of available receive
200 CAUTION: When setting RxIntDelay to a value other than 0, adapters may
217 along with RxIntDelay, may improve traffic throughput in specific network
242 higher number of transmit descriptors may be denied. In this case,
253 traffic bursts of short packets may result in an improper descriptor
255 the adapter, after which the transmit flow will restart, though data may
[all …]
|
| D | LICENSE.qlcnic | 4 You may modify and redistribute the device driver code under the
73 a notice placed by the copyright holder saying it may be distributed
89 1. You may copy and distribute verbatim copies of the Program's
97 You may charge a fee for the physical act of transferring a copy, and
98 you may at your option offer warranty protection in exchange for a fee.
100 2. You may modify your copy or copies of the Program or any portion
118 a warranty) and that users may redistribute the program under
144 3. You may copy and distribute the Program (or a work based on it,
182 4. You may not copy, modify, sublicense, or distribute the Program
202 these terms and conditions. You may not impose any further
[all …]
|
| D | LICENSE.qlge | 4 You may modify and redistribute the device driver code under the
73 a notice placed by the copyright holder saying it may be distributed
89 1. You may copy and distribute verbatim copies of the Program's
97 You may charge a fee for the physical act of transferring a copy, and
98 you may at your option offer warranty protection in exchange for a fee.
100 2. You may modify your copy or copies of the Program or any portion
118 a warranty) and that users may redistribute the program under
144 3. You may copy and distribute the Program (or a work based on it,
182 4. You may not copy, modify, sublicense, or distribute the Program
202 these terms and conditions. You may not impose any further
[all …]
|
| D | vortex.txt | 69 There are several parameters which may be provided to the driver when
75 If you are using the PCMCIA tools (cardmgr) then the options may be
113 selection values may be OR'ed (or added to) the following:
199 may disable the feature with `hw_checksums=0'.
223 This is mainly for debugging purposes, although it may be advantageous
230 Becker's `ether-wake' application may be used to wake suspended
295 Donald's mii-diag program may be used for inspecting and manipulating
335 If autonegotiation is a problem, you may need to specify "speed
403 o Any additional module parameters which you may be providing to the driver.
420 (The above may vary, depending upon which Linux distribution you use).
[all …]
|
| D | rxrpc.txt | 102 (*) Each connection goes to a particular "service". A connection may not go
103 to multiple services. A service may be considered the RxRPC equivalent of
110 (*) Up to a billion connections may be supported concurrently between one
122 (*) Each RxRPC operation is a "call". A connection may make up to four
123 billion calls, but only up to four calls may be in progress on a
131 flag in the packet. The number of packets of data making up one blob may
152 been received but may yet be discarded and re-requested. The sender may
162 (*) An call may be aborted by either end at any time up to its completion.
175 connections are handled transparently. One client socket may be used to
177 may handle calls from many clients.
[all …]
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Kconfig | 17 support into your kernel, you may answer Y here to build in the
31 support into your kernel, you may answer Y here to build in the
47 support into your kernel, you may answer Y here to build in the
61 support into your kernel, you may answer Y here to build in the
77 If you chose to build PARIDE support into your kernel, you may
102 support into your kernel, you may answer Y here to build in the
120 If you chose to build PARIDE support into your kernel, you may
139 If you chose to build PARIDE support into your kernel, you may
151 into your kernel, you may answer Y here to build in the protocol
162 into your kernel, you may answer Y here to build in the protocol
[all …]
|
| /linux-4.4.14/Documentation/gpio/ |
| D | sysfs.txt | 4 Platforms which use the "gpiolib" implementors framework may choose to
13 may need to temporarily remove that protection, first importing a GPIO,
44 "export" ... Userspace may ask the kernel to export control of
60 "direction" ... reads as either "in" or "out". This value may
63 operation, values "low" and "high" may be written to
72 is configured as an output, this value may be written;
114 or other cards in the stack. In such cases, you may need to use the
134 After a kernel driver requests a GPIO, it may only be made available in
136 signal direction may change. This helps drivers prevent userspace code
|
| D | gpio-legacy.txt | 37 cases (to support bidirectional signaling). GPIO controllers may have
41 sometimes level triggered. Such IRQs may be configurable as system
61 glue logic that may even change between board revisions, and can't ever be
113 may use this predicate:
117 A number that's not valid will be rejected by calls which may request
118 or free GPIOs (see below). Other numbers may also be rejected; for
195 GPIO access that may sleep
217 Accessing such GPIOs requires a context which may sleep, for example
226 from contexts which may sleep, since they may need to access the GPIO
248 * non-null labels may be useful for diagnostics.
[all …]
|
| /linux-4.4.14/Documentation/timers/ |
| D | timers-howto.txt | 8 deal with hardware delays and who may not be the most intimately
30 precision may not actually exist on many non-PC devices.
39 There are a few more options here, while any of them may
63 for usleep *may* not be worth it. Such an evaluation
73 msleep(1~20) may not do what the caller intends, and
86 that may have happened for other reasons, or at the
|
| D | timekeeping.txt | 6 drivers/clocksource in the kernel tree, but the code may be spread out
32 may stop during system suspend.
55 Since this operation may be invoked very often, doing this in a strict
92 and register range may be used for the clock event, but it is essentially
112 number of nanoseconds since the system was started. An architecture may or
113 may not provide an implementation of sched_clock() on its own. If a local
124 between accuracy compared to the clock source, you may sacrifice accuracy
128 The sched_clock() function may wrap only on unsigned long long boundaries,
137 The clock driving sched_clock() may stop or reset to zero during system
139 events on the system. However it may result in interesting timestamps in
[all …]
|
| /linux-4.4.14/Documentation/i2c/ |
| D | fault-codes | 9 faults. There may be fancier recovery schemes that are appropriate in
17 In short, your I2C driver code may need to know these codes in order
18 to respond correctly. Other code may need to rely on YOUR code reporting
30 codes that may be returned, and other cases where these codes should
52 may have a way to report PEC mismatches on writes from the
76 may verify the device returns *correct* responses, and
91 found no device to bind to. (ENODEV may also be used.)
119 SMBus adapters may return it when an operation took more
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | operations.txt | 66 FSCACHE_OP_WAITING may be set in op->flags prior to each submission of the
78 (1) The operation may be done synchronously (FSCACHE_OP_MYTHREAD). A thread
79 may decide it wants to handle an operation itself without deferring it to
96 (2) The operation may be fast asynchronous (FSCACHE_OP_FAST), in which case it
109 (3) The operation may be slow asynchronous (FSCACHE_OP_SLOW), in which case it
122 Furthermore, operations may be one of two types:
124 (1) Exclusive (FSCACHE_OP_EXCLUSIVE). Operations of this type may not run in
128 being written to may need truncation.
130 (2) Shareable. Operations of this type may be running simultaneously. It's
|
| D | object.txt | 35 There is a 1:N relationship between cookies and objects. A cookie may be
36 represented by multiple objects - an index may exist in more than one cache -
37 or even by no objects (it may not be cached).
83 and DObject represent data storage objects. Indices may have representation in
84 multiple caches, but currently, non-index objects may not. Objects of any type
85 may also be entirely unrepresented.
98 object->state. A cookie may point to a set of objects that are in different
134 (1) Threads may be completely occupied for very long periods of time by a
135 particular work item. These state actions may be doing sequences of
139 (2) Threads may do little actual work, but may rather spend a lot of time
[all …]
|
| D | netfs-api.txt | 14 may or may not have anything associated with it, but the netfs doesn't
184 in the hierarchy may be stored in multiple caches. This function does not
195 cookie acquisition function and the maximum length of key data that it may
203 this is a data file. The size may be used to govern how much cache must
212 it may provide. It should write the auxiliary data into the given buffer
217 The length of the auxiliary data buffer may be dependent on the key
245 valid until after the I/O completion is called, two functions may be
251 required for indices as indices may not contain data. These functions may
252 be called in interrupt context and so may not sleep.
259 or not. Note that several pages at once may be presented for marking.
[all …]
|
| D | backend-api.txt | 57 This function may return -ENOMEM if it ran out of memory or -EEXIST if the tag
84 In either case, this may not be an appropriate context in which to access the
87 The calling process's fsuid, fsgid and SELinux security identities may need to
96 The cache may present data to the outside world through FS-Cache's interfaces
187 backend to do the operation. The backend may get extra refs to it by
188 calling fscache_get_retrieval() and refs may be discarded by calling
241 This function may also be used to parse the index key to be used for
279 may fail (for instance if the cache is being withdrawn) by returning NULL.
309 may also be returned.
348 This method is used to discard a reference to an object. The object may
[all …]
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-gpio | 7 As a Kconfig option, individual GPIO signals may be accessed from
10 kernel code, it may be exported by userspace (and unexported later).
11 Kernel code may export it for complete or partial access.
|
| D | sysfs-block | 83 Storage devices may report a physical block size that is
94 Storage devices may report a physical block size that is
114 block size but may be bigger. One example is SATA
124 Storage devices may report a granularity or preferred
138 Storage devices may report an optimal I/O size, which is
165 Devices that support discard functionality may
176 Devices that support discard functionality may
187 Devices that support discard functionality may
200 Devices that support discard functionality may have
216 Devices that support discard functionality may return
|
| D | sysfs-bus-platform | 11 driver_override) and may be cleared with an empty string
19 name such as "none". Only a single driver may be specified in
|
| D | sysfs-bus-amba | 10 driver_override file (echo vfio-amba > driver_override) and may
19 Only a single driver may be specified in the override, there is
|
| D | sysfs-class-scsi_host | 24 '1' indicates the feature is enabled, and the controller may
26 means the feature is disabled and the controller may not use
|
| D | sysfs-class-rc | 47 This value may be reset to 0 if the current protocol is altered.
62 This value may be reset to 0 if the current protocol is altered.
96 This value may be reset to 0 if the wakeup protocol is altered.
111 This value may be reset to 0 if the wakeup protocol is altered.
|
| D | sysfs-platform-asus-laptop | 42 This may control the led, the device or both.
51 This may control the led, the device or both.
|
| D | sysfs-class-extcon | 11 port. An external connector may have multiple cables
15 may have both HDMI and Charger attached, or analog audio,
19 such binary relations may be expressed with extcon_dev's
|
| D | sysfs-class-cxl | 36 userspace must request on a CXL_START_WORK ioctl. Userspace may
45 Decimal value of the size of the MMIO space that may be mmaped
106 An AFU may optionally export one or more PCIe like configuration records, known
151 Decimal value of the size of the MMIO space that may be mmaped
223 Writing 1 will issue a PERST to card which may cause the card
233 0 = don't trust, the image may be different (default)
|
| /linux-4.4.14/arch/powerpc/boot/dts/ |
| D | iss4xx.dts | 38 i-cache-line-size = <32>; // may need fixup in sim
39 d-cache-line-size = <32>; // may need fixup in sim
40 i-cache-size = <32768>; /* may need fixup in sim */
41 d-cache-size = <32768>; /* may need fixup in sim */
|
| /linux-4.4.14/fs/fscache/ |
| D | Kconfig | 23 multi-CPU system these may be on cachelines that keep bouncing
40 and on a multi-CPU system these may be on cachelines that keep
41 bouncing between CPUs. On the other hand, the histogram may be
51 management module. If this is set, the debugging output may be
|
| /linux-4.4.14/fs/cachefiles/ |
| D | Kconfig | 18 caching on files module. If this is set, the debugging output may be
34 and on a multi-CPU system these may be on cachelines that keep
35 bouncing between CPUs. On the other hand, the histogram may be
|
| /linux-4.4.14/firmware/keyspan/ |
| D | usa19.HEX | 90 derived. Except as noted below this firmware image may not be
98 This firmware may not be modified and may only be used with
|
| D | usa19qi.HEX | 90 derived. Except as noted below this firmware image may not be
98 This firmware may not be modified and may only be used with
|
| D | mpr.HEX | 89 derived. Except as noted below this firmware image may not be
97 This firmware may not be modified and may only be used with
|
| D | usa28x.HEX | 130 derived. Except as noted below this firmware image may not be
138 This firmware may not be modified and may only be used with
|
| D | usa19w.HEX | 130 derived. Except as noted below this firmware image may not be
138 This firmware may not be modified and may only be used with
|
| D | usa28xb.HEX | 131 derived. Except as noted below this firmware image may not be
139 This firmware may not be modified and may only be used with
|
| D | usa18x.HEX | 130 derived. Except as noted below this firmware image may not be
138 This firmware may not be modified and may only be used with
|
| D | usa19qw.HEX | 131 derived. Except as noted below this firmware image may not be
139 This firmware may not be modified and may only be used with
|
| D | usa28xa.HEX | 130 derived. Except as noted below this firmware image may not be
138 This firmware may not be modified and may only be used with
|
| D | usa49w.HEX | 134 derived. Except as noted below this firmware image may not be
142 This firmware may not be modified and may only be used with
|
| D | usa28.HEX | 137 derived. Except as noted below this firmware image may not be
145 This firmware may not be modified and may only be used with
|
| D | usa49wlc.HEX | 135 derived. Except as noted below this firmware image may not be
143 This firmware may not be modified and may only be used with
|
| /linux-4.4.14/firmware/emi26/ |
| D | loader.HEX | 109 * and which may not be reproduced, used, sold or transferred to
112 * This firmware may not be modified and may only be used with the
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 16 (actually, the carrier driver may choose whether or not to return it -
21 Please note that all the machinery is in place but some details may
37 int eeprom_len; /* Usually 8kB, may be less */
68 * irq: number for the mezzanine; may be zero.
80 * fpga_base: the I/O memory address (may be NULL).
118 Note: mezzanine_data may be redundant, because Linux offers the drvdata
119 approach, so the field may be removed in later versions of this bus
156 carrier provides a fpga_base pointer, the driver may use direct
197 but fmc-specific flags may be added in the future. You'll most
211 reserved to fit bigger I2C devices in the future. Carriers may
[all …]
|
| /linux-4.4.14/Documentation/fb/ |
| D | deferred_io.txt | 6 IO. The following example may be a useful explanation of how one such setup
33 It may be the case that this is useful in other scenarios as well. Paul Mundt
37 Another one may be if one has a device framebuffer that is in an usual format,
38 say diagonally shifting RGB, this may then be a mechanism for you to allow
48 The following example may be helpful.
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.cx88 | 21 - Most tuner chips do provide mono sound, which may or may not
29 TV norms may or may not work.
|
| /linux-4.4.14/Documentation/usb/ |
| D | mass-storage.txt | 18 there may be some with hardware restrictions that prevent a buffer
35 backing storage for each logical unit. There may be at most
39 *BEWARE* that if a file is used as a backing storage, it may not
41 assumes the data does not change without its knowledge. It may be
111 Note that this may mean that if the device is powered from USB and
113 least some Windows users do), the data may be lost.
162 not specified as removable (but that may look strange to the
163 host). It may fail, however, if host disallowed medium removal
183 mass storage protocol. As a composite function, MSF may be used by
188 module parameters may be missing, or the parameters may have
[all …]
|
| D | functionfs.txt | 4 unique behaviour. It may be added to an USB configuration only after
11 may not be in init section (ie. may not use the __init tag).
27 "ep1" file may be really mapped to (say) endpoint 3 (and when
|
| D | proc_usb_info.txt | 36 "usbfs", to reduce confusion with "devfs". You may
65 These files may also be used to write user-level drivers for the USB
78 usbfs mount options such as "devmode=0666" may be helpful.
110 d = decimal number (may have leading spaces or 0's)
111 x = hexadecimal number (may have leading spaces or 0's)
128 Speed may be:
185 | For USB host controller drivers (virtual root hubs) this may
216 USB devices may have multiple configurations, each of which act
243 A given interface may have one or more "alternate" settings.
244 For example, default settings may not use more than a small
[all …]
|
| D | callbacks.txt | 48 context. You may sleep. However, it is important that all sleeps have a
71 particular interface. The device will not be suspended and you may do IO
82 callback. You also may not do any other operation that may interfere
101 restore. No more URBs may be submitted until the post_reset method
|
| D | power-management.txt | 73 device is enabled for remote wakeup and it is suspended, it may resume
135 autosuspend_delay_ms. (There may also be a file named "level"; this
308 operation. URBs may once more be submitted.
365 then the interface is considered to be idle, and the kernel may
456 driver may call the usb_autopm_get_interface_async() routine at a time
495 Firstly, a device may already be autosuspended when a system suspend
498 resume. But this theory may not work out well in practice; over time
503 Secondly, a dynamic power-management event may occur as a system
506 For example, a suspended device may send a remote-wakeup signal while
507 the system is suspending. The remote wakeup may succeed, which would
[all …]
|
| D | gadget_multi.txt | 13 A CDC ECM (Ethernet) function may be turned on via a Kconfig option
18 CDC ECM) you may need to change vendor and/or product ID.
95 Failing to comply may cause brain damage after wondering for hours why
97 some drivers information (changing USB port may sometimes help plus
145 [7] You may find [[http://www.cygnal.org/ubb/Forum9/HTML/001050.html]]
|
| D | error-codes.txt | 72 USB device drivers may only test urb status values in completion handlers.
76 A transfer's actual_length may be positive even when an error has been
85 Individual frame descriptor status fields may report more status codes.
112 bus turn-around time. This error may instead be
160 processing, devices may receive such fault reports for every request.
|
| /linux-4.4.14/Documentation/ia64/ |
| D | aliasing.txt | 21 like UC is, but writes may be delayed and combined to increase
90 mappings may be either WB or UC. If the region being mapped
91 happens to be in kern_memmap, meaning that it may also be mapped
106 physical address space, but it may be different on machines with
117 This is an MMIO mmap of PCI functions, which additionally may or
118 may not be requested as using the WC attribute.
133 There may be corner cases of things that are not in kern_memmap,
162 The EFI memory map may not report these MMIO regions.
166 succeed. It may create either WB or UC user mappings, depending
179 The kernel VGA driver may ioremap the VGA frame buffer at 0xA0000,
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 24 Note that pin controllers themselves may also be client devices of themselves.
25 For example, a pin controller may set up its own "active" state when the
37 property exists to define the pin configuration. Each state may also be
50 entries may exist in this list so that multiple pin
51 controllers may be configured, or so that a state may be built
57 In some cases, it may be useful to define a state, but for it
58 to be empty. This may be required when a common IP block is
62 exist, they must still be defined, but may be left empty.
125 device; they may be grandchildren, for example. Whether this is legal, and
|
| /linux-4.4.14/drivers/ras/ |
| D | Kconfig | 26 measures how often it is available for use, even though it may not
27 be functioning correctly. For example, a server may run forever and
28 so have ideal availability, but may be unreliable, with frequent
|
| /linux-4.4.14/Documentation/ptp/ |
| D | ptp.txt | 44 the character device as a POSIX clock id and may call
48 User space programs may control the clock using standardized
49 ioctls. A program may query, enable, configure, and disable the
52 signals may be configured via the POSIX timer_settime() system
69 class driver, since the lock may also be needed by the clock
|
| /linux-4.4.14/drivers/devfreq/ |
| D | Kconfig | 5 A device may have a list of frequencies and voltages available.
10 Each device may have its own governor and policy. Devfreq can
14 Like some CPUs with CPUfreq, a device may have multiple clocks.
26 used with the devfreq device, you may use OPP helper
39 values that imply the usage rate. A device may provide tuned
|
| /linux-4.4.14/Documentation/input/ |
| D | event-codes.txt | 3 may be used.
13 input subsystem; drivers do not need to maintain the state and may attempt to
14 emit unchanged values without harm. Userspace may obtain the current state of
27 - Used as markers to separate events. Events may be separated in time or in
77 occurring at the same moment in time. For example, motion of a mouse may set
107 touchscreens. These devices may be used with fingers, pens, or other tools.
117 to 1. Meaningful physical contact may mean any contact, or it may mean
119 touchpad may set the value to 1 only when the touch pressure rises above a
120 certain value. BTN_TOUCH may be combined with BTN_TOOL_<name> codes. For
121 example, a pen tablet may set BTN_TOOL_PEN to 1 and BTN_TOUCH to 0 while the
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | phy.txt | 16 - compatible: Compatible list, may contain
20 assume clause 22. The compatible list may also contain other
23 If the phy's identifier is known then the list may contain an entry
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.hz | 10 to have the timer interrupt run at 1000 Hz but 100 Hz may be more
12 a fast response for user interaction and that may experience bus
23 with lots of processors that may show reduced performance if
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-summary | 22 device, so those three signal wires may be connected to several chips
31 - SPI may be used for request/response style device protocols, as with
34 - It may also be used to stream data in either direction (half duplex),
37 - Some devices may use eight bit words. Others may use different word
60 course they won't handle full duplex transfers. You may find such
109 clock edge. The chipselect may have made it become available.
142 Controller drivers ... controllers may be built into System-On-Chip
144 These drivers touch hardware registers and may use DMA.
200 devices, and the controller may need some platform_data in order to
247 * production boards may already have done this, but
[all …]
|
| /linux-4.4.14/Documentation/ |
| D | memory-barriers.txt | 18 - What may not be assumed about memory barriers?
102 abstract CPU, memory operation ordering is very relaxed, and a CPU may actually
104 appears to be maintained. Similarly, the compiler may also arrange the
142 Furthermore, the stores committed by a CPU to the memory system may not be
192 There are some minimal guarantees that may be expected of a CPU:
242 we may get any of the following sequences:
251 (*) It _must_ be assumed that overlapping memory accesses may be merged or
256 we may get any one of the following sequences:
266 we may get any of:
436 Memory operations that occur before an ACQUIRE operation may appear to
[all …]
|
| D | parport-lowlevel.txt | 81 registers: data, status, and control. The hardware may not actually
83 modelled after common PC implementations. Other low-level drivers may
91 Hardware assistance for EPP and/or ECP transfers may or may not be
92 available, and if it is available it may or may not be used. If
148 hardware. It consists of flags which may be bitwise-ored together:
155 PARPORT_MODE_TRISTATE The data drivers may be turned off.
173 There may be other flags in 'modes' as well.
347 'preempt', 'wakeup' and 'irq'. Each of these may be NULL in order to
369 'flags' may be a bitwise combination of the following flags:
487 'parport_claim_or_block' may do. (Put something here about blocking
[all …]
|
| D | nommu-mmap.txt | 82 (such as ramfs or tmpfs) may choose to honour an open, truncate, mmap
101 In the no-MMU case: The character device driver may choose to honour
112 (*) A request for a private mapping of a file may return a buffer that is not
113 page-aligned. This is because XIP may take place, and the data may not be
118 of the space may be wasted as the kernel must allocate a power-of-2
187 The mremap() function is partially supported. It may change the size of a
188 mapping, and may move it[*] if MREMAP_MAYMOVE is specified and if the new size
195 Shared mappings may not be moved. Shareable mappings may not be moved either,
199 a previously mapped object. It may not be used to create holes in existing
212 to get a proposed address for the mapping. This may return an error if it
[all …]
|
| D | SM501.txt | 7 which may provide numerous interfaces including USB host controller USB gadget,
9 The device may be connected by PCI or local bus with varying functions enabled.
22 On detection of a device, the core initialises the chip (which may
69 be divided down individually. If this is not set, then SM501 may
|
| D | preempt-locking.txt | 29 First, since the data is per-CPU, it may not have explicit SMP locking, but
31 the previous value of smp_processor_id may not equal the current. You must
128 These may be used to protect from preemption, however, on exit, if preemption
129 may be enabled, a test to see if preemption is required should be done. If
131 is done. They may also be called within a spin-lock protected region, however,
134 are also protected by preemption locks and so may use the versions which do
|
| D | io-mapping.txt | 16 This _wc variant provides a mapping which may only be used
33 page and may only be used with mappings created by
36 Note that the task may not sleep while holding this page
46 variant, although they may be significantly slower.
|
| D | iostats.txt | 15 is mounted on /sys, although of course it may be mounted anywhere.
37 if you are watching a known, small set of disks. /proc/diskstats may
53 may wrap. Applications should be prepared to deal with that; unless
63 Reads and writes which are adjacent to each other may be merged for
64 efficiency. Thus two 4K reads may become one 8K read before it is
91 I/O completion time and the backlog that may be accumulating.
95 modifying these counters. This implies that minor inaccuracies may be
98 but due to the lack of locking it may only be very close.
|
| D | circular-buffers.txt | 60 be careful, however, as a region more than one unit in size may wrap the end of
117 but the consumer may still be depleting the buffer on another CPU and
120 To the consumer it will show an upper bound as the producer may be busy
125 producer may still be filling the buffer on another CPU and moving the
128 To the producer it will show an upper bound as the consumer may be busy
133 independent and may be made on different CPUs - so the result in such a
134 situation will merely be a guess, and may even be negative.
|
| D | kref.txt | 40 refcount cannot go to zero) you may do this without a lock.
117 First of all, you may not know what you are doing. Second, you may
119 involved where the above may be legal) but someone else who doesn't
120 know what they are doing may change the code or copy the code. It's
251 otherwise kref_get_unless_zero may reference already freed memory.
299 before using kfree, but note that synchronize_rcu() may sleep for a
|
| D | DMA-API.txt | 23 a dma_addr_t directly because there may be translation between its physical
35 without having to worry about caching effects. (You may however need
44 It also returns a <dma_handle> which may be cast to an unsigned integer the
49 minimum allocation length may be as big as a page, so you should
55 implementation may choose to ignore flags that affect the location of
75 may only be called with IRQs enabled.
192 The direction for both APIs may be converted freely by casting.
202 Further, contiguous kernel virtual space may not be contiguous as
215 the driver may specify various platform-dependent flags to restrict
221 dma_mask may not apply if the platform has an IOMMU (a device which
[all …]
|
| D | pinctrl.txt | 20 can control PINs. It may be able to multiplex, bias, set load capacitance,
28 there may be several such number spaces in a system. This pin space may
29 be sparse - i.e. there may be gaps in the space with numbers where no
98 and such things in your driver, or the code may become complicated. You must
99 also consider matching of offsets to the GPIO ranges that may be handled by
190 may need more entries in your group structure, for example specific register
199 may be able to make an output pin high impedance, or "tristate" meaning it is
200 effectively disconnected. You may be able to connect an input pin to VDD or GND
281 The GPIO drivers may want to perform operations of various types on the same
292 pin controller may be muxing several GPIO ranges (typically SoCs that have
[all …]
|
| D | ManagementStyle | 10 simple coding style rules, so this document may or may not have anything
18 These suggestions may or may not apply to you.
67 you cannot escape. A cornered rat may be dangerous - a cornered manager
89 deleting it, you may have irrevocably lost the trust of that
120 answer may end up being that both teams get so frustrated by the
123 That may sound like a failure, but it's usually a sign that there was
239 somebody else puts on airs, it _really_ rubs us the wrong way. You may
269 First off, while you may or may not get screaming teenage girls (or
|
| /linux-4.4.14/Documentation/power/ |
| D | devices.txt | 36 leave the low-power state. This feature may be enabled or disabled
38 drivers the ioctl interface used by ethtool may also be used for this
39 purpose); enabling it may cost some power usage, but let the whole
43 Devices may also be put into low-power states while the system is
48 device is on, it may be necessary to carry out some bus-specific
50 states at run time may require special handling during system-wide power
62 have been put into low-power states (at runtime), the effect may be very similar
69 drivers are no longer accepted. A given bus or platform may have different
195 wakeup" used by runtime power management, although it may be supported by the
198 they should be put into the full-power state. Those interrupts may or may not
[all …]
|
| D | notifiers.txt | 4 There are some operations that subsystems or drivers may want to carry out
8 For example, device drivers may want to upload firmware to their devices after
11 points). The solution may be to load the firmware into memory before processes
13 A suspend/hibernation notifier may be used for this purpose.
|
| D | basic-pm-debugging.txt | 108 or resume its device (in the latter case the system may hang or become unstable
122 unloaded all modules. In that case, you may want to look in your kernel
124 with these drivers compiled as modules). You may also try to use some special
133 work (of course, this only may be an issue on SMP systems) and the problem
143 A failure of any of the "platform", "processors" or "core" tests may cause your
145 indicates a serious problem that very well may be related to the hardware, but
174 kernel messages using the serial console. This may provide you with some
176 it may be possible to use a FireWire port for debugging with firescope
195 Among other things, the testing with the help of /sys/power/pm_test may allow
200 it does not work "out of the box", you may need to boot it with
[all …]
|
| D | charger-manager.txt | 6 and where each battery may have multiple chargers attached and the userland
13 the system may need multiple instances of Charger Manager.
21 A system may have multiple chargers (or power sources) and some of
22 they may be activated at the same time. Each charger may have its
30 we may need to monitor the battery health by looking at the ambient or
42 requires tasks other than cm_suspend_again, it may implement its own
101 feature, the platform_suspend_ops may directly refer to cm_suspend_again
|
| D | freezing-of-tasks.txt | 43 calling try_to_freeze(). The main loop of a freezable kernel thread may look
90 Kernel threads are not freezable by default. However, a kernel thread may clear
111 may cause something like this to happen, they have to be freezable.
124 process running on a second CPU while we are suspending devices may, for
141 So in practice, the 'at all' may become a 'why freeze kernel threads?' and
144 Still, there are kernel threads that may want to be freezable. For example, if
160 may notice that the number of CPUs has changed and may start to work incorrectly
167 First of all, the freezing of kernel threads may be tricky if they depend one
171 may be undesirable. That's why kernel threads are not freezable by default.
198 A driver must have all firmwares it may need in RAM before suspend() is called.
|
| D | states.txt | 10 /sys/power/state file. Those strings may be "mem", "standby", "freeze" and
67 Additional operations may take place depending on the platform capabilities. In
79 system from it. This may be the case on other platforms too.
105 Once memory state is written to disk, the system may either enter a
106 low-power state (like ACPI S4), or it may simply power down. Powering
|
| /linux-4.4.14/Documentation/scsi/ |
| D | qlogicfas.txt | 32 may take a while.
42 It may be a good idea to enable RESET_AT_START, especially if the
43 devices may not have been just powered up, or if you are restarting
44 after a crash, since they may be busy trying to complete the last
46 if you have reliable hardware and connections it may be more useful to
|
| D | osst.txt | 35 devices. If those are not present, you may create them by calling
58 depending on your choice during kernel config. You may still need to create
61 To load your module, you may use the command
66 If you want to have the module autoloaded on access to /dev/osst, you may
71 You may find it convenient to create a symbolic link
82 You may use the OnStream tape driver with your standard backup software,
83 which may be tar, cpio, amanda, arkeia, BRU, Lone Tar, ...
86 supported and you may try the mt (or mt_st) program to jump between
106 guarantees the block size of 32k. (Otherwise you may pass the -b64 option to
110 On a fast machine, you may profit from software data compression (z flag for
[all …]
|
| D | LICENSE.qla4xxx | 5 You may modify and redistribute the device driver code under the
74 a notice placed by the copyright holder saying it may be distributed
90 1. You may copy and distribute verbatim copies of the Program's
98 You may charge a fee for the physical act of transferring a copy, and
99 you may at your option offer warranty protection in exchange for a fee.
101 2. You may modify your copy or copies of the Program or any portion
119 a warranty) and that users may redistribute the program under
145 3. You may copy and distribute the Program (or a work based on it,
183 4. You may not copy, modify, sublicense, or distribute the Program
203 these terms and conditions. You may not impose any further
[all …]
|
| D | LICENSE.qla2xxx | 5 You may modify and redistribute the device driver code under the
75 a notice placed by the copyright holder saying it may be distributed
91 1. You may copy and distribute verbatim copies of the Program's
99 You may charge a fee for the physical act of transferring a copy, and
100 you may at your option offer warranty protection in exchange for a fee.
102 2. You may modify your copy or copies of the Program or any portion
120 a warranty) and that users may redistribute the program under
146 3. You may copy and distribute the Program (or a work based on it,
184 4. You may not copy, modify, sublicense, or distribute the Program
204 these terms and conditions. You may not impose any further
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/mips/cavium/ |
| D | ciu2.txt | 13 the CIU and may have a value between 0 and 63. The second cell is
14 the bit within the bank and may also have a value between 0 and 63.
|
| D | ciu.txt | 13 the CIU and may have a value of 0 or 1. The second cell is the bit
14 within the bank and may have a value between 0 and 63.
|
| /linux-4.4.14/lib/ |
| D | Kconfig.kmemcheck | 23 The kernel may be started with kmemcheck=0 or kmemcheck=1 to disable
60 other faults. The queue will be emptied as soon as a tasklet may
82 thrown away afterwards. This may of course also hide some real
92 This may also hide some real bugs.
|
| /linux-4.4.14/drivers/ntb/test/ |
| D | Kconfig | 5 doorbells of the ntb hardware. This driver may be used to test that
16 This driver may be used to test that your ntb hardware and drivers are
|
| /linux-4.4.14/drivers/net/ |
| D | LICENSE.SRC | 5 Director, National Security Agency. This software may be used
15 expected. Although updates may occur, no commitment exists.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | gpmi-nand.txt | 26 the software may chooses an implementation-defined
36 turned on may not be accessible by the BootROM
39 The device tree may optionally contain sub-nodes describing partitions of the
|
| D | brcm,brcmnand.txt | 16 to account for any SoC-specific hardware bits that may be
66 - compatible: Can be one of several SoC-specific strings. Each SoC may have
85 Each controller (compatible: "brcm,brcmnand") may contain one or more subnodes
86 to represent enabled chip-selects which (may) contain NAND flash chips. Their
113 Each nandcs device node may optionally contain sub-nodes describing the flash
|
| D | fsl-upm-nand.txt | 15 - gpios : may specify optional GPIOs connected to the Ready-Not-Busy pins
22 Each flash chip described may optionally contain additional sub-nodes
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | ring.txt | 4 a buffer may supply and how it is specified within IIO. For more
35 The primary buffer reading function. Note that it may well not return
46 Set the number of complete scans that may be held by the buffer.
|
| /linux-4.4.14/Documentation/arm/ |
| D | memory.txt | 16 this document may reserve more VM space over time.
81 Please note that mappings which collide with the above areas may result
82 in a non-bootable kernel, or may cause the kernel to (eventually) panic
85 Since future CPUs may impact the kernel mapping layout, user programs
|
| D | Booting | 33 this in a machine dependent manner. (It may use internal algorithms
34 to automatically locate and size all RAM, or it may use knowledge of
89 The ATAG_CORE tag may or may not be empty. An empty ATAG_CORE tag
160 The zImage may also be placed in system RAM and called there. The
199 Instruction cache may be on or off.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | dax.txt | 22 size equal to your kernel's PAGE_SIZE, so you may need to specify a block
38 of bytes that can be contiguously accessed at that offset. It may also
48 These block devices may be used for inspiration:
72 The get_block() callback passed to the DAX functions may return
77 These filesystems may be used for inspiration:
|
| D | Locking | 25 rename_lock ->d_lock may block rcu-walk
73 all may block
89 permission: no (may not block if called in rcu-walk mode)
131 All may block [not true, see below]
171 may block
208 All except set_page_dirty and freepage may block
232 may be called from the request handler (/dev/loop).
241 "sync". These are quite different operations and the behaviour may differ
257 This may also be done to avoid internal deadlocks, but rarely.
296 written. The address_space implementation may write more (or less) pages
[all …]
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 18 Groups. Note that other groups may also distribute working documents as
22 Internet Drafts may be updated, replaced, or obsoleted by other documents
82 mapping to hosts within the authority's domain. These mappings may be
124 corresponding ASCII representations. Non-related groups of systems may
136 have their own unique mappings. For example, one group of systems may
137 use the number 5 to represent Unclassified while another group may use the
158 identifiers are greater than 127 are defined by the DOI authority and may
182 restrictions specified in this document may increase to use the full area
348 octets. Up to 15 categories may be represented by this tag. Valid values
413 label. This tag may contain a maximum of 7 category pairs. The bottom
[all …]
|
| /linux-4.4.14/Documentation/vm/ |
| D | slub.txt | 8 an impact on overall system performance which may make a bug more
30 Parameters may be given to slub_debug. If none is specified then full
60 Red zoning and tracking may realign the slab. We can just apply sanity checks
65 Debugging options may require the minimum possible slab order to increase as
82 and tracing may only be enabled. The other options may cause the realignment
85 Careful with tracing: It may spew out lots of information and never stop if
91 If no debug options are specified then SLUB may merge similar slabs together
126 contention may occur.
237 of the corruption is may be more likely found by looking at the function that
264 keep corrupting objects. This may be important for production systems.
[all …]
|
| D | numa | 9 comprises multiple components or assemblies each of which may contain 0
15 Each of the 'cells' may be viewed as an SMP [symmetric multi-processor] subset
17 may not be populated on any given cell. The cells of the NUMA system are
47 architectures. As with physical cells, software nodes may contain 0 or more
84 default zonelist order may be overridden using the numa_zonelist_order kernel
137 may revert to its own fallback path. The slab kernel memory allocator is an
138 example of this. Or, the subsystem may choose to disable or not to enable
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 12 driver implementation may support the following properties:
19 may be assigned to root buses behind different host bridges. The domain
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 15 - thermal sensors: devices which may be used to take temperature
17 - cooling devices: devices which may be used to dissipate heat.
29 nodes providing temperature data to thermal zones. Thermal sensor devices may
188 device in temperature ranges that may damage the silicon structures and
322 case on SoC designs with several internal IPs that may need different thermal
323 requirements, and thus may have their own sensor to monitor or detect internal
348 /* each zone within the SoC may have its own trips */
362 /* each zone within the SoC may have its own cooling */
375 /* each zone within the SoC may have its own trips */
389 /* each zone within the SoC may have its own cooling */
[all …]
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | compress_offload.txt | 34 - separation between byte counts and time. Compressed formats may have
36 may vary from frame-to-frame. As a result, it is not possible to
45 may also provide support for a limited number of audio encoders and
46 decoders embedded in firmware, or may support more choices through
55 AAC, some implementations may support AAC multichannel but HE-AAC
56 stereo. Likewise WMA10 level M3 may require too much memory and cpu
107 the number of channels supported may depend on a specific profile. If
108 the capabilities were exposed with a single descriptor, it may happen
109 that a specific combination of profiles/channels/formats may not be
202 are lost during transmission. This may be added in the future.
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | driver.txt | 10 Device drivers are statically allocated structures. Though there may
19 also initialize the devclass field (when it arrives), so it may obtain
74 Some may find the syntax of embedded struct initialization awkward or
93 lock. These fields are assumed to be valid at all times and may be
115 Once the object has been registered, it may access the common fields of
163 A driver's probe() may return a negative errno value to indicate that
169 remove is called to unbind a driver from a device. This may be
|
| D | porting.txt | 57 The bus type may be unregistered (if the bus driver may be compiled
65 Other code may wish to reference the bus type, so declare it in a
151 Optionally, the bus driver may set the device's name and release
178 (There may be other code that is currently referencing the device
229 of operations that the driver model core may call.
338 Instead, a bus may supply a method in struct bus_type that does the
386 A bus driver may also supply additional parameters for userspace to
405 An internal list that the bus uses may be removed, in favor of using
417 it. An internal list of drivers that the bus driver maintains may
420 The drivers may be iterated over, like devices:
|
| /linux-4.4.14/tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 9 that scripts may want to use. Context.pm contains the Perl->C
54 at your option, any later version of Perl 5 you may have available.
56 Alternatively, this software may be distributed under the terms of the
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | memchr.S | 104 # searched. $16 may not be aligned.
121 # last quad may or may not be partial).
|
| D | ev6-memchr.S | 123 # searched. $16 may not be aligned.
139 # last quad may or may not be partial).
|
| /linux-4.4.14/drivers/staging/ |
| D | Kconfig | 9 development, may or may not work, and may contain userspace
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 25 call interposition frameworks. BPF programs may not dereference
47 CONFIG_HAVE_ARCH_SECCOMP_FILTER, then filters may be added as below:
76 additional filters may be layered on which will increase evaluation
84 A seccomp filter may return any of the following values. If multiple
158 the system call numbers may vary based on the specific invocation. If
160 the filters may be abused. Always check the arch value!
204 but the syscall may not be changed to another system call using the
205 orig_rax register. It may only be changed to -1 order to skip the
217 condition: future kernels may improve vsyscall emulation and current
|
| /linux-4.4.14/Documentation/s390/ |
| D | 3270.txt | 17 You may have 3270s in-house and not know it. If you're using the
54 You may generate both 3270 and 3215 console support, or one or the
200 and more output will appear. You may hit ENTER with nothing typed in
205 You may change the scrolling timeout value. For example, the following
211 Other things you may do when the log area fills up are: hit PA2 to
219 PA1 causes a SIGINT to the currently running application. You may do
225 PF3 causes an EOF to be received as input by the application. You may
228 No PF key is preassigned to cause a job suspension, but you may cause a
229 job suspension by typing "^Z" and hitting ENTER. You may wish to
241 may hit PF10 again for the next-most-recent command, and so on. A
[all …]
|
| D | DASD | 8 below. Thus you may have up to 64 DASD devices in your system.
10 The kernel parameter 'dasd=from-to,...' may be issued arbitrary times
43 labels, VTOCs etc. The ioctl may take a 'struct format_data *' or
63 but may be sure that you can reuse your data after introduction of a
|
| /linux-4.4.14/drivers/isdn/mISDN/ |
| D | Kconfig | 18 This module may be used for special applications that require
21 decryption. It may use hardware features if available.
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | cavium-octeon-gpio.txt | 15 controller, many of its pins may be configured as an interrupt
20 triggering protocol and may have one of four values:
|
| /linux-4.4.14/Documentation/mn10300/ |
| D | ABI.txt | 64 in which the callee may store the first two arguments.
85 The values in certain registers may be clobbered by the callee, and other
99 Certain ordinary registers may carry special usage for the compiler:
109 The kernel may use a slightly different ABI internally.
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-async-req.txt | 26 preparation may cost even more. As long as these slower preparations are run
48 post_req() -- that the host driver may implement in order to move work
50 In the DMA case pre_req() may do dma_map_sg() and prepare the DMA
59 request. The host driver may optimize for this scenario to minimize
|
| /linux-4.4.14/net/l2tp/ |
| D | Kconfig | 20 tunnels. One IP tunnel may carry thousands of individual PPP
40 Support for l2tp directory in debugfs filesystem. This may be
79 userspace L2TPv3 daemons may create L2TP/IP tunnel sockets
101 L2TP ethernet pseudowire instance. Standard Linux tools may
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | regulator.txt | 5 - regulator-min-microvolt: smallest voltage consumers may set
6 - regulator-max-microvolt: largest voltage consumers may set
8 - regulator-min-microamp: smallest current consumers may set
9 - regulator-max-microamp: largest current consumers may set
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | adm9240 | 58 each two seconds. User-space may read sysfs interface faster than the
109 - resolution of the low speed limit may be reduced
113 * fan speed may be displayed as zero until the auto fan clock divider
155 The ADM9240 provides an internal open drain on this line, and may output
176 that alarm bits may be cleared on read, user-space may latch alarms and
|
| D | pmbus-core | 24 set a status error flag, and some devices may simply hang up.
98 negative error code if not. The chip driver may return -ENODATA or any other
115 - Supported chip functionality can be provided to the core driver. This may be
131 specific command, but that a standard PMBus command may exist. Any other
151 Chip drivers may provide pointers to the following functions in struct
157 <page> may be -1, which means "current page".
171 <page> may be -1, which means "current page".
184 PMBus registers. Chip drivers may also use direct I2C commands. If direct I2C
208 selects page first. <page> may be -1, which means "current page".
213 selects page first. <page> may be -1, which means "current page".
|
| D | submitting-patches | 53 through Lindent. Lindent is not perfect, and you may have to do some minor
67 may save a line or so in the source, it obfuscates the code and makes code
68 review more difficult. It may also result in code which is more complicated
112 chip may offer, it should at least support all limits and alarms.
117 a presumably new chip may simply have been relabeled.
|
| D | asc7621 | 32 sheet says 10-bits of resolution, although you may find the lower bits
43 outputs or inputs and may be used as general purpose I/O or as alarm
47 temperature may be mapped to any zone, which has a default assignment
56 Both remote diode temperature readings may be given an offset value such
58 PWM may be offset for system calibration purposes.
70 may be used. These characteristics are in registers 04h to 07h.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 73 - It may well be that the problem is addressed by the kernel in ways which
82 - There may be elements of the proposed solution which will not be
87 problem; they may have ideas for a better solution, and may be willing
128 relevant subsystem and the environment may be more supportive.
133 MAINTAINERS file may, in fact, not be the person who is actually acting in
151 using the more aggressive options as you may end up including developers
192 Some readers may be thinking at this point that their kernel work is
195 mailing list may not be a viable option. In cases like this, it is worth
201 experienced kernel developers may choose to proceed in an open-loop manner
|
| D | 6.Followthrough | 31 Many of the changes you may be asked to make - from coding style tweaks
97 in mind, of course, that he may not agree with you either.
106 things. In particular, there may be more than one tree - one, perhaps,
122 What may also happen at this point, depending on the nature of your patch,
140 may be a new round of comments from developers who had not been aware of
141 the patch before. It may be tempting to ignore them, since there is no
161 After any regressions have been dealt with, there may be other, ordinary
169 And don't forget that there are other milestones which may also create bug
182 One day, you may open your mail client and see that somebody has mailed you
198 On very rare occasion, you may see something completely different: another
|
| /linux-4.4.14/Documentation/crypto/ |
| D | asymmetric-keys.txt | 39 A data parser may interpret the data blob as containing the bits representing a
40 key, or it may interpret it as a reference to a key held somewhere else in the
53 partial match. The key type may also use other criteria to refer to a key.
154 The function may also return -ENOTSUPP if an unsupported public-key algorithm
213 given -ENOTSUPP. The subtype may do anything it likes to implement an
223 check it each time it wanted to use it. Further, the contents of the blob may
225 dates) and may contain useful data about the key (identifiers, capabilities).
227 Also, the blob may represent a pointer to some hardware containing the key
303 The key's fingerprint string may be partially matched upon. For a
312 Parsers may not have the same name. The names are otherwise only used for
|
| /linux-4.4.14/drivers/staging/rtl8192u/ |
| D | copying | 63 a notice placed by the copyright holder saying it may be distributed
79 1. You may copy and distribute verbatim copies of the Program's
87 You may charge a fee for the physical act of transferring a copy, and
88 you may at your option offer warranty protection in exchange for a fee.
90 2. You may modify your copy or copies of the Program or any portion
108 a warranty) and that users may redistribute the program under
134 3. You may copy and distribute the Program (or a work based on it,
172 4. You may not copy, modify, sublicense, or distribute the Program
192 these terms and conditions. You may not impose any further
204 may not distribute the Program at all. For example, if a patent
[all …]
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | COPYING | 63 a notice placed by the copyright holder saying it may be distributed
79 1. You may copy and distribute verbatim copies of the Program's
87 You may charge a fee for the physical act of transferring a copy, and
88 you may at your option offer warranty protection in exchange for a fee.
90 2. You may modify your copy or copies of the Program or any portion
108 a warranty) and that users may redistribute the program under
134 3. You may copy and distribute the Program (or a work based on it,
172 4. You may not copy, modify, sublicense, or distribute the Program
192 these terms and conditions. You may not impose any further
204 may not distribute the Program at all. For example, if a patent
[all …]
|
| /linux-4.4.14/drivers/staging/rtl8192e/ |
| D | license | 67 placed by the copyright holder saying it may be distributed under the
83 1. You may copy and distribute verbatim copies of the Program's source code
90 You may charge a fee for the physical act of transferring a copy, and you
91 may at your option offer warranty protection in exchange for a fee.
93 2. You may modify your copy or copies of the Program or any portion of it,
111 users may redistribute the program under these conditions, and
137 3. You may copy and distribute the Program (or a work based on it, under
175 4. You may not copy, modify, sublicense, or distribute the Program except as
195 these terms and conditions. You may not impose any further restrictions
205 any other pertinent obligations, then as a consequence you may not
[all …]
|
| /linux-4.4.14/ |
| D | COPYING | 79 a notice placed by the copyright holder saying it may be distributed
95 1. You may copy and distribute verbatim copies of the Program's
103 You may charge a fee for the physical act of transferring a copy, and
104 you may at your option offer warranty protection in exchange for a fee.
106 2. You may modify your copy or copies of the Program or any portion
124 a warranty) and that users may redistribute the program under
150 3. You may copy and distribute the Program (or a work based on it,
188 4. You may not copy, modify, sublicense, or distribute the Program
208 these terms and conditions. You may not impose any further
220 may not distribute the Program at all. For example, if a patent
[all …]
|
| D | REPORTING-BUGS | 28 generic linux-kernel mailing list (LKML) may cause your bug report to be
139 bug reports. That may include running new tests, applying patches,
154 they may not be able to address your bug in a day, a week, or two weeks.
155 If they don't answer your email, they may be on vacation, or at a Linux
161 kernel, and they may not work on the weekends. Maintainers are scattered
162 around the world, and they may not work in your time zone. Unless you
|
| /linux-4.4.14/Documentation/devicetree/bindings/reset/ |
| D | st,sti-picophyreset.txt | 9 However, when asserted it may not be possible to access the hardware's
11 may no longer be valid.
|
| D | st,sti-softreset.txt | 10 However, when asserted it may not be possible to access the hardware's
12 may no longer be valid.
|
| D | st,sti-powerdown.txt | 11 However, when asserted it may not be possible to access the hardware's
13 may no longer be valid.
|
| /linux-4.4.14/security/tomoyo/ |
| D | Kconfig | 13 Required userspace tools and further information may be
39 If you don't need audit logs, you may set this value to 0.
75 option. For example, if you pass init=/bin/systemd option, you may
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-arch.txt | 9 locked. This is usually not a problem unless switch_to may need to
29 threads need only ever query need_resched, and may never set or
51 although it may be reasonable to do some background work or enter
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-log.txt | 5 A region (or portion of the address space) of the disk may be
10 the legs of the mirror and may not reach the legs at the same time.
33 will not survive a reboot or crash, but there may be a small boost in
|
| D | thin-provisioning.txt | 17 with depth. Fragmentation may still be an issue, however, in some
79 snapshots which are recording large amounts of change, you may find you
88 You may reload a pool's table, indeed this is how the pool is resized
106 may want to use a value such as 1024 (512KB). People doing lots of
107 snapshotting may want a smaller value such as 128 (64KB). If you are
129 a volatile write cache. If power is lost you may lose some recent
137 Once the pool's metadata device is repaired it may be resized, which
143 completion may have already been acknowledged to upper IO layers
215 Of course, you may write to the thin device and take internal snapshots
315 defaults to 60 seconds but may be disabled using a value of 0.
|
| /linux-4.4.14/arch/xtensa/ |
| D | Kconfig | 249 This syscall is deprecated. It may have issues when called with
262 This syscall is deprecated. It may have issues when called with
369 Device binding to host file may be changed at runtime via proc
379 Kernel/module parameter 'simdisk_count' may be used to change this
380 value at runtime. More file names (but no more than 10) may be
409 blocks of physically contiguous memory, then you may need to
459 There's a 2x16 LCD on most of XTFPGA boards, kernel may output
460 progress messages there during bootup/shutdown. It may be useful
473 the correct address. Wrong address here may lead to hardware lockup.
480 LCD may be connected with 4- or 8-bit interface, 8-bit access may
|
| /linux-4.4.14/Documentation/arm64/ |
| D | booting.txt | 17 is passed to the Linux kernel. This may include secure monitor and
18 hypervisor code, or it may just be a handful of instructions for
37 this in a machine dependent manner. (It may use internal algorithms
38 to automatically locate and size all RAM, or it may use knowledge of
124 image has no special significance to the kernel, and may be used for
154 Instruction cache may be on or off.
160 operations must be configured and may be enabled.
172 domain on entry to the kernel. This may require IMPLEMENTATION DEFINED
220 contained in the reserved region. A wfe instruction may be inserted
|
| /linux-4.4.14/Documentation/serial/ |
| D | moxa-smartio | 79 In Moxa's Web sites, you may always find latest driver at http://www.moxa.com/.
82 or built-in into kernel (Static driver). You may refer to following
123 You may need to adjust IRQ usage in BIOS to avoid from IRQ conflict
136 The driver file may be obtained from ftp, CD-ROM or floppy disk. The
156 You may find all the driver and utilities files in /moxa/mxser.
253 will activate the module driver. You may run "lsmod" to check
260 3.4.4 For the above description, you may manually execute
322 install any ISA boards, you may skip to next portion.
402 If major number 30 and 35 had been occupied, you may have to select
407 In /proc/devices, you may find all the major numbers occupied
[all …]
|
| /linux-4.4.14/arch/avr32/boards/hammerhead/ |
| D | Kconfig | 16 This enables LCD support for the Hammerhead board. You may
26 This enables Sound support for the Hammerhead board. You may
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 7 different subdirectories in this location. Interfaces may change levels
49 Contact: Primary contact for this interface (may be a mailing list)
63 Interfaces in stable may move to obsolete, as long as the proper
66 Interfaces may be removed from obsolete and the kernel as long as the
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.char | 32 lines to host portals. They may be accessed with 'telnet <host>
33 <port number>'. Any number of consoles and serial lines may be
87 It is safe to leave this unchanged, although you may wish to change
99 It is safe to leave this unchanged, although you may wish to change
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | README.quirks | 55 internal arbiter may still logical-or the two requests. However, once
63 not allow the other request to hold REQ asserted. The decision lock may
65 idle (FRAME and IRDY). The arbiter decision may then continue
72 A small percentage of core logic devices may start a bus transaction
|
| /linux-4.4.14/Documentation/block/ |
| D | deadline-iosched.txt | 5 In particular, it will clarify the meaning of the exposed tunables that may be
66 may even know that it is a waste of time to spend any time attempting to
68 Front merges may still occur due to the cached last_merge hint, but since
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 65 "net" may also be helpful since it may someday provide easier mount syntax for
89 2) an entry for the share in /etc/fstab indicating that a user may
111 the utility umount.cifs may be used. It may be invoked directly, or if
152 feature of most Linux filesystems which may require enabling via
162 Some administrators may want to change Samba's smb.conf "map archive" and
165 which may not be what you want, although if the CIFS Unix extensions are
168 may require specifying a mkdev function to Samba if you are not using
197 Before -o the option -v may be specified to make the mount.cifs
220 When using the mount helper mount.cifs, passwords may be specified via alternate
284 may want to restrict at the client as well. For those
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | brcm,bus-axi.txt | 17 The top-level axi bus may contain children representing attached cores
19 detected (e.g. IRQ numbers). Also some of the cores may be responsible
|
| D | renesas,bsc.txt | 9 While the BSC is a fairly simple memory-mapped bus, it may be part of a PM
10 domain, and may have a gateable functional clock.
|
| /linux-4.4.14/Documentation/namespaces/ |
| D | compatibility-list.txt | 4 may have when creating tasks living in different namespaces.
25 within the namespace it was obtained in and may refer to some
|
| /linux-4.4.14/drivers/mtd/spi-nor/ |
| D | Kconfig | 15 on the usage this feature may provide performance gain in comparison
21 Please note that some tools/drivers/filesystems may not work with
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 16 number of clocks may depend of the SoC type.
34 number of clocks may depend of the SoC type.
67 number of clocks may depend of the SoC type.
80 number of clocks may depend of the SoC type.
93 number of clocks may depend of the SoC type.
107 number of clocks may depend of the SoC type.
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | consumer.txt | 41 NOTE: The supply may already be enabled before regulator_enabled() is called.
42 This may happen if the consumer shares the regulator or the regulator has been
56 NOTE: This may not disable the supply if it's shared with other consumers. The
72 voltage along with frequency to save power, SD drivers may need to select the
102 change the current limit to vary the backlight brightness, USB drivers may want
156 Bespoke or tightly coupled drivers may want to directly control regulator
|
| /linux-4.4.14/fs/jffs2/ |
| D | README.Locking | 25 nodes to an inode may obsolete old ones, and by holding the alloc_sem
50 before calling a function which may need to allocate space. The
51 allocation may trigger garbage-collection, which may need to move a
87 may remove _obsolete_ nodes from the list while holding only the
129 been unlinked. Because reading from the flash may sleep, the
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 48 This may also apply to multiple master IOMMU devices that do not allow the
52 - #iommu-cells = <1>: Multiple master IOMMU devices may need to be configured
57 be configured. The first cell of the address in this may contain the master
62 Note that these are merely examples and real-world use-cases may use different
84 not guarantee that the IOMMU is really disabled since the hardware may not
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 14 writing to nfsd/portlist; that write may be:
29 Between startup and shutdown, the number of threads may be adjusted up
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | pl011.txt | 11 and may contain a second name named "sleep". The former
27 When present, may have one or two dma channels.
|
| /linux-4.4.14/arch/arm/include/asm/ |
| D | vfpmacros.h | 28 ldr \tmp, =elf_hwcap @ may not have MVFR regs
52 ldr \tmp, =elf_hwcap @ may not have MVFR regs
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | chosen.txt | 12 Device trees may specify the device to be used for boot console output
53 is being booted by kexec, as the booting environment may differ (e.g.
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | devices.txt | 40 movement as people get some experience with this. We may just want
42 CAP_MKNOD. We may want to just refuse moving to a cgroup which
43 isn't a descendant of the current one. Or we may want to use
49 A cgroup may not be granted more permissions than the cgroup's
|
| D | unified-hierarchy.txt | 64 There's no limit on how many hierarchies there may be, which means
66 The key may contain any varying number of entries and is unlimited in
80 depending on the specific controller. In other words, hierarchy may
112 controller states are destroyed asynchronously and controllers may
113 have lingering references, a controller may not show up immediately on
116 moved out of the unified hierarchy and it may take some time for the
119 may need to be disabled too.
204 extra layer of nesting which may not be necessary, makes the interface
225 Except for the root, only cgroups which don't contain any task may
267 this may in the future be limited explicitly.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 4 - compatible : compatible list, may contain one or two entries
13 - reg : It may contain one or two regions. The first region should contain
42 This property may be used in virtualized environments where the hypervisor
92 In a virtualized environment, the hypervisor may need to create an IOMMU
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 77 root may not be able to log in to recover the system.
126 one of them may be specified at a time. When one sysctl is written it is
147 Note: dirty_bytes is the counterpart of dirty_ratio. Only one of them may be
201 To increase the number of objects freed by this operation, the user may run
211 objects, it may cost a significant amount of I/O and CPU to recreate the
215 You may see informational messages in your kernel log when this file is
374 may have. Memory map areas are used as a side-effect of calling
379 programs, particularly malloc debuggers, may consume lots of them,
454 and may not be fast.
527 you may be able to read ZONE_DMA as ZONE_DMA32...)
[all …]
|
| /linux-4.4.14/Documentation/x86/ |
| D | mtrr.txt | 14 Even if Linux does not use MTRRs directly, some x86 platform firmware may still
16 firmware may still have implemented access to MTRRs which would be controlled
31 the Memory Type Range Registers (MTRRs) may be used to control
51 The CONFIG_MTRR option creates a /proc/mtrr file which may be used
85 typical line that you may get is:
89 Note that you should only use the value from the X server, as it may
148 Richard Gooch may be reached by email at rgooch@atnf.csiro.au
244 Richard Gooch may be reached by email at rgooch@atnf.csiro.au
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 28 this manual, but the user may need to be aware of the module
49 It is possible, however, that Speakup may have been compiled into the
60 the default one, then you may issue the following command at the boot
66 DoubleTalk LT at boot up. You may replace the ltlk synthesizer keyword
209 commands in a specific part of the alphabet, you may press the letter of
236 laptop. So you may choose which set of Speakup keys to use. Some
237 system administrators may have chosen to compile Speakup for a desktop
531 Depending on your situation, you may wish to echo none to the synth
632 Espeakup may already be available as a package for your distribution
683 distribution may also have a precompiled Speech Dispatcher package.
[all …]
|
| /linux-4.4.14/certs/ |
| D | Kconfig | 22 the keyring are considered to be trusted. Keys may be added at will
24 userspace may only add extra keys if those keys can be verified by
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | jack.txt | 22 For example, a system may have a stereo headset jack with two reporting
44 of the endpoint may configured to be the opposite of the jack status if
62 Each jack may have multiple reporting mechanisms, though it will need at
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | Kconfig.aic79xx | 28 a high number of commands per device may result in memory allocation
30 the default is set to 32. Higher values may result in higher performance
55 as the db v1 library. You may have to install additional packages
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | driver-changes.txt | 5 automatically, though the driver may still override the settings
24 are reserved and may be used immediately -- until pcmcia_release_window()
31 are reserved, after calling pcmcia_request_configuration(), they may
43 Instead of the old pcmcia_request_irq() interface, drivers may now
49 - drivers still not capable of IRQF_SHARED (or not telling us so) may
|
| /linux-4.4.14/arch/powerpc/boot/dts/fsl/ |
| D | qoriq-gpio-1.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | qoriq-qman1.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-mpic-timer-B.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | p1010rdb-pa_36b.dts | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-espi-0.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-mpic-message-B.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-esdhc-0.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-sata2-0.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | qoriq-gpio-0.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | qoriq-qman3.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-usb2-dr-1.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|
| D | pq3-sata2-1.dtsi | 14 * names of its contributors may be used to endorse or promote products
18 * ALTERNATIVELY, this software may be distributed under the terms of the
|