Searched full:too (Results 1 – 25 of 442) sorted by relevance
12345678910>>...18
| /Documentation/ABI/removed/ |
| D | video1394 | 9 to use raw1394 + libraw1394 too because video1394 did not provide
16 libdc1394 (works with firewire-cdev too, transparent to library ABI
|
| D | raw1394 | 15 libraw1394 (works with firewire-cdev too, transparent to library ABI
|
| /Documentation/scsi/ |
| D | cxgb3i.rst | 42 buffer. Otherwise, the payload data will be sent to the host too.
77 The default setting for MaxRecvDataSegmentLength (131072) is too big;
83 too big. A error message in the format of
84 "cxgb3i: ERR! MaxRecvSegmentLength <X> too big. Need to be <= <Y>."
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-driver-turris-omnia | 7 LEDs at once, so that if they are too bright, user can dim them.
24 If the feature is not supported because the MCU firmware is too
|
| D | sysfs-bus-iio-chemical-sunrise-co2 | 30 - 'error_low_voltage': Sensor regulated voltage too low
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 50 write-back mode fixes the 'write hole' issue too, since all write data is
56 overhead too. Write-back cache will aggregate the data and flush the data to
73 Too small cache disk will make the write aggregation less efficient in this
84 checksummed too. The checksum is stored in the meta data ahead of the data. The
110 they are discarded too. MD then loads valid data and writes them to RAID disks
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | xlnx,versal-wwdt.yaml | 17 too soon and a period that is not too late. The WWDT has to be
|
| D | ti,rti-wdt.yaml | 16 time window, meaning either too early or too late. The error signal
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 45 we felt to be a bit excessive. Excessive _not_ because it's too small of
46 a CPU utilization, but because it causes too frequent (once per
54 and we never got a single complaint about nice +19 being too _weak_ in
56 too _strong_ :-)
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 17 # CORE must be 'y' too.
23 # we know CORE_BELL_A_ADVANCED can be 'y' too.
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-pin-error-inj.rst | 59 # <op>[,<mode>] tx-early-eom set the EOM bit one byte too soon
65 # <op>[,<mode>] tx-short-start send a start pulse that's too short
66 # <op>[,<mode>] tx-long-start send a start pulse that's too long
177 protocol since messages that are too short should be ignored.
218 Set the EOM bit one byte too soon. This obviously only works for messages
221 this case. Since the resulting message is likely to be too short for this
238 two bytes long. The receiver should ignore messages that are too short.
253 sees a too-short 0 bit.
271 sees a too-long 0 bit.
|
| /Documentation/sound/designs/ |
| D | midi-2.0.rst | 37 implemented differently (e.g. as a ALSA sequencer client), too.
69 `midi2_enable=0` option to snd-usb-audio driver module, too.
173 supports the new UMP MIDI 2.0 device, too. Now, each ALSA sequencer
232 The proc file above shows the UMP Block information, too. The same
239 between UMP MIDI 1.0 and 2.0 types, too. For example, running
396 those can be used for a real device, instead, too.
468 And on the connected host, a similar card should appear, too, but with
486 the gadget, too.
508 The `block.*` subdirectories can be removed dynamically, too (except
523 too. When MIDI 1.0 interface is selected by the connected host, the
[all …]
|
| D | seq-oss.rst | 68 configuration will be changed via ``/proc`` interface, too.
121 too.
168 to write timing was implemented, too.
265 bit should NOT be included, too. This is necessary to tell it from other
303 done here, too. This callback must not be NULL.
358 ``CAP_SUBS_READ`` or ``CAP_SUBS_WRITE``, must be defined, too. If
|
| /Documentation/process/ |
| D | management-style.rst | 94 too, and while the actual **work** was easy enough to undo by just
149 alienate too many kernel developers. It turns out that alienating people
187 sadly that you are one too, and that while we can all bask in the secure
213 direction, just don't push too hard.
254 don't try to make it too obvious unless you really **intend** to irritate
257 Similarly, don't be too polite or subtle about things. Politeness easily
272 a while, and you'll feel cleansed. Just don't crap too close to home.
|
| D | botching-up-ioctls.rst | 119 still too tricky have a timeout or hangcheck safety net as a last-ditch
123 - it's way too easy to create a deadlock between your hangcheck code and
152 ioctl restartable relative timeouts tend to be too coarse and can
198 as unique identifiers - it's how real files are told apart, too.
225 complain about regressions disappears, too.
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 128 This is returned by drivers when an operation took too much
133 when a slave stretches clocks too far. I2C has no such
135 arbitrary limits (much longer than SMBus!) too.
|
| /Documentation/networking/device_drivers/ethernet/dec/ |
| D | dmfe.rst | 22 10/100 ethernet cards uses Davicom chipset too, so this driver supports CNET cards too ).If you
|
| /Documentation/hwmon/ |
| D | nct6683.rst | 43 Some of the register locations can be reverse engineered; others are too
45 considered too risky with this firmware and has been disabled. All limits
|
| /Documentation/tools/rv/ |
| D | common_ikm.rst | 12 command itself. If the **rv** command itself generates too many events,
|
| /Documentation/arch/x86/ |
| D | tlb.rst | 41 You may be doing too many individual invalidations if you see the
44 called too often, you can lower the tunable::
|
| /Documentation/filesystems/spufs/ |
| D | spu_create.rst | 74 ELOOP Too many symlinks were found while resolving pathname.
79 pathname was too long.
|
| /Documentation/userspace-api/media/drivers/ |
| D | imx-uapi.rst | 33 NTSC/PAL signal re-sync (too little or too many video lines). When
|
| /Documentation/leds/ |
| D | well-known-leds.txt | 13 Legacy names are listed, too; in case you are writing application that
15 but then try the legacy ones, too.
|
| /Documentation/admin-guide/mm/damon/ |
| D | reclaim.rst | 34 duration and page out. To avoid it consuming too much CPU for the paging out
204 But, setting this too high could result in increased monitoring overhead.
214 However, setting this too low could result in bad monitoring quality. Please
282 to be done only up to 1 GiB per second to avoid DAMON_RECLAIM consuming too
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-spi-byte.txt | 13 accelerated blinking) might can be supported too.
|
12345678910>>...18