Searched full:about (Results 1 – 25 of 918) sorted by relevance
12345678910>>...37
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 19 device descriptor parameters. The full information about
27 device descriptor parameters. The full information about
36 about the descriptor could be found at UFS specifications 2.1.
44 The full information about the descriptor could be found
53 about the descriptor could be found at UFS specifications 2.1.
61 The full information about the descriptor could be found
70 parameters. The full information about the descriptor could
80 parameters. The full information about the descriptor could
90 about the descriptor could be found at UFS specifications 2.1.
98 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| D | debugfs-driver-habanalabs | 15 Description: Displays a list with information about the currently allocated
22 Description: Displays a list with information about the currently active
29 Description: Displays a list with detailed information about each JOB (CB) of
115 e.g. to display info about VA 0x1000 for ASID 1 you need to do:
129 Description: Displays a list with information about the currently user
137 Description: Displays a list with information about all the active virtual
|
| /Documentation/arm/sunxi/ |
| D | clocks.rst | 2 Frequently asked questions about the sunxi clock system
6 about the sunxi clock system, as well as accompanying ASCII art when adequate.
26 When you are about to suspend, you switch the CPU Mux to the 32kHz
47 Q: Were can I learn more about the sunxi clocks?
|
| /Documentation/vm/ |
| D | page_owner.rst | 4 page owner: Tracking about who allocated each page
10 page owner is for the tracking about who allocated each page.
12 When allocation happens, information about allocation such as call stack
14 When we need to know about status of all pages, we can get and analyze
89 See the result about who allocated each page
|
| /Documentation/process/ |
| D | management-style.rst | 17 Btw, when talking about "kernel manager", it's all about the technical
19 companies. If you sign purchase orders or you have any clue about the
112 actually do the work also think twice about whether it's worth doing or
118 Remember: they'd better know more about the details than you do, and
165 you can call just about **anybody** a d*ckhead, and you often **will** be
180 scan nearly as well. But I'm sure he thought about it.
198 which is what the game is all about.
202 good idea - go wild", or "That sounds good, but what about xxx?". The
204 new about "xxx" or seem **extra** managerial by pointing out something the
205 smarter person hadn't thought about. In either case, you win.
[all …]
|
| D | index.rst | 12 to be learned about the kernel in a technical sense, it is also important
13 to learn about how our community works. Reading these documents will make
|
| D | 1.Intro.rst | 27 :ref:`development_coding` is about the coding process; several pitfalls which
32 :ref:`development_posting` talks about the process of posting patches for
50 What this document is about
96 who will not listen or who do not care about the development process.
183 thinking about doing so), you clearly have an interest in the continued
197 license (about which more will be said below). Your author is not a
215 - Everything that was said above about code review applies doubly to
262 Questions about copyright-related issues are common on Linux development
|
| /Documentation/filesystems/ |
| D | quota.txt | 18 For more details about quota design, see the documentation in quota-tools package
27 Thus quota netlink interface has been designed to pass information about
33 details about this layer). The name of the quota generic netlink interface
39 This command is used to send a notification about any of the above mentioned
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | ti,bq24735.txt | 18 about the ChargeCurrent (0x14h) register.
22 about the ChargeVoltage (0x15h) register.
26 more information about the InputCurrent (0x3fh) register.
|
| /Documentation/arm/samsung-s3c24xx/ |
| D | cpufreq.rst | 62 information with the core driver to provide information about what the
65 The board needs to supply information about whether it needs the IO bank
66 timings changing, any maximum frequency limits and information about the
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 5 This document explains the thinking about the revamped and streamlined
17 much stronger than they were before in 2.4 (and people were happy about
54 and we never got a single complaint about nice +19 being too _weak_ in
55 terms of CPU utilization, we only got complaints about it (still) being
63 about Linux's nice level support was its assymetry around the origo
|
| /Documentation/fb/ |
| D | internals.rst | 5 This is a first start for some documentation about frame buffer device
25 Device independent unchangeable information about a frame buffer device and
31 Device independent changeable information about a frame buffer device and a
46 Generic information, API and low level information about a specific frame
|
| /Documentation/devicetree/bindings/sound/ |
| D | tlv320aic32x4.txt | 16 See regulator/regulator.txt for more information about the detailed binding
22 See clock/clock-bindings.txt for information about the detailed format.
|
| /Documentation/scsi/ |
| D | scsi_eh.txt | 139 assumed to forget about the scmd at that point. However, if a scmd
141 about the scmd, which currently no LLDD does, the command is still
146 We'll talk about how SCSI EH takes actions to abort - make LLDD
147 forget about - timed out scmds later.
186 device forget about timed out scmds and make them ready for new
221 timed-out scmds, SCSI EH ensures that LLDD forgets about a scmd
324 all related hardware forget about the scmd.
355 that lower layers have forgotten about the scmd and we can
364 and STU doesn't make lower layers forget about those
418 On completion, the handler should have made lower layers forget about
[all …]
|
| /Documentation/input/ |
| D | uinput.rst | 31 For examples and more information about libevdev:
70 * The ioctls below will enable the device that is about to be
89 * the event, otherwise it will not notice the event we are about
152 * the event, otherwise it will not notice the event we are about
207 * The ioctls below will enable the device that is about to be
223 * the event, otherwise it will not notice the event we are about
|
| /Documentation/media/uapi/dvb/ |
| D | dvb-fe-read-status.rst | 18 tuner lock status and provide statistics about the quality of the
21 The information about the frontend tuner locking status can be queried
|
| D | fe-get-info.rst | 20 about the - front-end. This call only requires read-only access to the device.
46 obtain information about driver and hardware capabilities. The ioctl
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 18 Statistics about the state of all the tasks in the cgroup is returned to
22 about tasks blocked on I/O. If CONFIG_TASK_DELAY_ACCT is disabled, this
|
| /Documentation/admin-guide/sysctl/ |
| D | index.rst | 30 this document, and if you come to me complaining about how you
61 several (arch-dependent?) subdirs. Each subdir is mainly about
65 This documentation is about:
87 really like to hear about it :-)
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-g-enc-index.rst | 19 VIDIOC_G_ENC_INDEX - Get meta data about a compressed video stream
42 The :ref:`VIDIOC_G_ENC_INDEX <VIDIOC_G_ENC_INDEX>` ioctl provides meta data about a compressed
53 Each element of the ``entry`` array contains meta data about one
88 - Meta data about a compressed video stream. Each element of the
|
| /Documentation/arm/ |
| D | mem_alignment.rst | 22 mode isn't recommended for performance reasons (just think about the
23 floating point emulation that works about the same way). Fix your code
43 slow (think about the floating point emulator) and
|
| /Documentation/networking/ |
| D | 6pack.txt | 35 More details about 6pack are described in the file 6pack.ps that is located
60 with PC/FlexNet. Please do not ask me about the internals of this file as I
61 don't know anything about it. I used a textual description of the 6pack
74 and the status LED are lit for about a second if the firmware initialises
127 6 of this file about known problems.
134 so the 6pack driver doesn't know anything about connects or data that
|
| /Documentation/filesystems/ext4/ |
| D | about.rst | 3 About this Book
43 information about ext2/3. Here's another old reference:
|
| /Documentation/ |
| D | bus-virt-phys-mapping.txt | 29 that is, normal RAM--see later about other details):
129 So why do we care about the physical address at all? We do need the physical
134 management layer doesn't know about devices outside the CPU, so it
135 shouldn't need to know about "bus addresses" etc).
140 only talks about "real memory", that is, CPU memory (RAM).
191 OK, that just about covers the basics of accessing IO portably. Questions?
|
| /Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 39 including soft dirty bits. To notify user space application about such
44 can find more details about it on http://criu.org
|
12345678910>>...37