Searched full:know (Results 1 – 25 of 375) sorted by relevance
12345678910>>...15
| /Documentation/sound/cards/ |
| D | bt87x.rst | 34 The driver is now stable. However, it doesn't know about many TV cards,
35 and it refuses to load for cards it doesn't know.
45 or not, so that future versions of this driver know about your card.
|
| /Documentation/devicetree/bindings/ |
| D | common-properties.txt | 15 know the peripheral always needs to be accessed in big endian (BE) mode.
17 unconditionally (e.g. readl/writel). Use this if you know the
71 by all of its devices. The driver needs to know how many devices the
|
| /Documentation/filesystems/ |
| D | hpfs.txt | 85 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
94 chgrp symlinks but I don't know what is it good for. chmoding symlink results
99 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
133 should work. If you have OS/2 server, use only read-only mode. I don't know how
135 list, I don't know how to delete them when file is deleted and how to not
166 reasons. If you extremely wish to update them, let me know, I'll write it (but
173 anybody know what does it mean?
186 whole created by this driver, it is BUG - let me know about it.
232 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
|
| /Documentation/fb/ |
| D | metronomefb.rst | 30 originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
33 I neither have access to nor know exactly what the waveform does in terms of
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 10 You know how dm-crypt works. If not, visit the following web page:
13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
119 Please don't mind the weird loop above, busybox's msh doesn't know
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 6 level. Instead, the software must know which devices are connected on each
98 main chip by the means of an I2C bus. You won't know the number of the I2C
121 A variant of this is when you don't know for sure if an I2C device is
213 In general, the kernel should know which I2C devices are connected and
244 device is not officially supported yet but you know it is compatible.
253 available, and you don't need to know what driver the device needs.
|
| D | dma-considerations.rst | 25 flag with it. Then, the I2C core and drivers know they can safely operate DMA
36 know their buffers are DMA safe. Users of i2c_transfer() must set the
|
| /Documentation/ |
| D | xz.txt | 99 decompression code. I don't know if it could have any use in the
100 kernel, but I know that it would be useful in some embedded projects
109 it is good to know this if testing the code e.g. with the test files
121 kernel-related mailing lists, so if there's something I should know,
|
| D | DMA-attributes.txt | 113 - You know that the accesses to this memory won't thrash the TLB.
114 You might know that the accesses are likely to be sequential or
118 - You know that the penalty of TLB misses while accessing the
122 - You know that the DMA mapping is fairly transitory. If you expect
|
| D | debugging-modules.txt | 7 want to know if it failed for the fallback code for old aliases in
|
| /Documentation/scsi/ |
| D | 53c700.txt | 31 driver, you need to know three things about the way the chip is wired
38 Optionally, you may also need to know other things, like how to read
61 This will be a standard SCSI driver (I don't know of a good document
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-w1 | 10 Users: any user space application which wants to know bus scanning
|
| /Documentation/ABI/removed/ |
| D | o2cb | 6 removed when new versions of ocfs2-tools which know to look
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 58 to know it.
89 example, the GPU drivers will need to know those details. In case of
90 Thunderbolt alternate mode, the thunderbolt drivers will need to know them, and
|
| /Documentation/media/ |
| D | video.h.rst.exceptions | 6 # This is a deprecated obscure API. Just ignore things we don't know
|
| /Documentation/networking/ |
| D | 6pack.txt | 61 don't know anything about it. I used a textual description of the 6pack
134 so the 6pack driver doesn't know anything about connects or data that
147 with the serial driver of 2.0.3x kernels. I don't know yet if the problem
154 occur when there is a bare AX.25 connection still running. I don't know if
|
| /Documentation/process/ |
| D | management-style.rst | 45 manage had better know the details better than you, so if they come to
49 (Corollary:if the people you manage don't know the details better than
56 makes you look like you know what you're doing, so what a kernel manager
118 Remember: they'd better know more about the details than you do, and
229 Then make the developer who really screwed up (if you can find them) know
231 future, but so that they know they owe you one. And, perhaps even more
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 69 If you don't know the absolute GPIO pin numbers at registration time,
84 assign a dynamic ID to your device. If you do not know the absolute
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 69 to the other processor, in order to let it know about the
70 creation of the channel (this way remote clients know they
|
| D | debugfs-ec | 17 CAUTION: Do not write to the Embedded Controller if you don't know
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | twl-charger.txt | 4 to know when charging is permissible, and when there is a connection
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 44 Here the BIOS should ask exactly what it wants to know:
85 But _OS had fundamental problems. First, the BIOS needed to know the name
86 of every possible version of the OS that would run on it, and needed to know
109 An old OS that doesn't know about those extensions would answer FALSE,
|
| /Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 24 know for example that GPIO #23 controls the write protect line used to
29 and the kernel would have no need to know about it.
33 standard kernels won't know about. And for some tasks, simple userspace
|
| /Documentation/locking/ |
| D | spinlocks.rst | 35 sequences that you **know** need to be split up: avoid it at all cost if you
109 cheaper versions of the spinlocks. IFF you know that the spinlocks are
118 This is useful if you know that the data in question is only ever
|
| /Documentation/media/uapi/dvb/ |
| D | intro.rst | 19 What you need to know
25 you should know what a program/transport stream (PS/TS) is and what is
34 It is also necessary to know how to access Linux devices and how to
|
12345678910>>...15