Searched refs:information (Results 1 – 25 of 1585) sorted by relevance
12345678910>>...64
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 19 device descriptor parameters. The full information about
27 device descriptor parameters. The full information about
35 the UFS device descriptor parameters. The full information
44 The full information about the descriptor could be found
52 the UFS device descriptor parameters. The full information
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
89 the UFS device descriptor parameters. The full information
97 the UFS device descriptor parameters. The full information
[all …]
|
| /Linux-v5.4/fs/fscache/ |
| D | Kconfig | 11 See Documentation/filesystems/caching/fscache.txt for more information.
14 bool "Gather statistical information on local caching"
17 This option causes statistical information to be gathered on local
28 See Documentation/filesystems/caching/fscache.txt for more information.
31 bool "Gather latency information on local caching"
34 This option causes latency information to be gathered on local
45 See Documentation/filesystems/caching/fscache.txt for more information.
55 See Documentation/filesystems/caching/fscache.txt for more information.
|
| /Linux-v5.4/drivers/net/ethernet/intel/ |
| D | Kconfig | 29 Use the above information and the Adapter & Driver ID Guide that
36 More specific information on configuring the driver is in
47 adapters. For more information on how to identify your adapter, go
52 More specific information on configuring the driver is in
66 use the regular e1000 driver For more information on how to
72 More specific information on configuring the driver is in
95 adapters. For more information on how to identify your adapter, go
100 More specific information on configuring the driver is in
131 information on how to identify your adapter, go to the Adapter &
136 More specific information on configuring the driver is in
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 64 :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` for more information.
69 information on the linux-kernel mailing list see
88 Gather information
91 The most important information in a bug report is how to reproduce the
92 bug. This includes system information, and (most importantly)
98 bug report. This explains what you should do with the "Oops" information
104 information they're really interested in. If some information is not
111 Use that information to fill in all fields of the bug report form, and
118 [4.] Kernel information
122 [6.] Output of Oops.. message (if applicable) with symbolic information
[all …]
|
| D | security-bugs.rst | 22 As it is with any bug, the more information provided the easier it
25 information is helpful. Any exploit code is very helpful and will not
29 Disclosure and embargoed information
47 While embargoed information may be shared with trusted individuals in
48 order to develop a fix, such information will not be published alongside
51 and followup discussions (if any), exploits, CVE information or the
55 information submitted to the security list and any followup discussions
|
| /Linux-v5.4/Documentation/fb/ |
| D | internals.rst | 25 Device independent unchangeable information about a frame buffer device and
31 Device independent changeable information about a frame buffer device and a
38 Device independent colormap information. You can get and set the colormap
46 Generic information, API and low level information about a specific frame
51 Device dependent information that uniquely defines the video mode for this
|
| D | api.rst | 24 Device and driver capabilities are reported in the fixed screen information
51 additional information, which are stored in the variable screen information
54 Visuals describe how color information is encoded and assembled to create
65 screen information line_length field.
83 belonging to different planes, is stored in the fixed screen information
89 stored in the variable screen information grayscale field.
94 specified by the variable screen information bpp field.
105 specified by the variable screen information bpp field.
120 information red, green, blue and transp fields.
129 screen information bits_per_pixel field.
[all …]
|
| /Linux-v5.4/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 27 NSLU2 NAS device. For more information on this platform,
35 Avila Network Platform. For more information on this platform,
52 information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
59 7001 Access Point. For more information on this platform,
67 WG302 v2 or WAG302 v2 Access Points. For more information
75 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
82 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
89 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
102 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
118 PrPCM1100 Processor Mezanine Module. For more information on
[all …]
|
| /Linux-v5.4/Documentation/vm/ |
| D | page_owner.rst | 12 When allocation happens, information about allocation such as call stack
15 this information.
25 fragmentation statistics can be obtained through gfp flag information of
33 doesn't require memory to store owner information, so there is no runtime
59 stores information into the memory from struct page extension. This memory
62 they would have no owner information. To fix it up, these early allocated
64 Although it doesn't mean that they have the right owner information,
83 4) Analyze information from page owner::
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | yuv-formats.rst | 17 separates the brightness information (Y) from the color information (U
18 and V or Cb and Cr). The color information consists of red and blue
22 early television would only transmit brightness information. To add
28 to brightness information.
|
| /Linux-v5.4/Documentation/networking/device_drivers/intel/ |
| D | igbvf.rst | 27 Driver information can be obtained using ethtool, lspci, and ifconfig.
36 For information on how to identify your adapter, and for the latest Intel
47 diagnostics, as well as displaying statistical information. The latest ethtool
55 For general information, go to the Intel support website at:
64 with a supported adapter, email the specific information related to the issue
|
| D | ice.rst | 17 more information, visit Intel's support page at https://support.intel.com.
36 For general information, go to the Intel support website at:
45 with a supported adapter, email the specific information related to the issue
|
| /Linux-v5.4/drivers/block/zram/ |
| D | Kconfig | 15 See Documentation/admin-guide/blockdev/zram.rst for more information.
29 See Documentation/admin-guide/blockdev/zram.rst for more information.
36 of zRAM. Admin could see the information via
39 See Documentation/admin-guide/blockdev/zram.rst for more information.
|
| /Linux-v5.4/fs/cachefiles/ |
| D | Kconfig | 12 information.
24 bool "Gather latency information on CacheFiles"
28 This option causes latency information to be gathered on CacheFiles
40 information.
|
| /Linux-v5.4/drivers/thermal/intel/int340x_thermal/ |
| D | Kconfig | 19 Enable this to expose the temperature information and cooling ability
22 the information to the user or use this information for making
24 information to allow the user to select his laptop to run without
|
| /Linux-v5.4/Documentation/arm/samsung-s3c24xx/ |
| D | cpufreq.rst | 54 The core code exports extra information via sysfs in the directory
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
|
| /Linux-v5.4/Documentation/x86/ |
| D | zero-page.rst | 16 000/040 ALL screen_info Text mode or frame buffer information
18 040/014 ALL apm_bios_info APM BIOS information (struct apm_bios_info)
20 060/010 ALL ist_info Intel SpeedStep (IST) BIOS support information
31 1C0/020 ALL efi_info EFI 32 information (struct efi_info)
|
| /Linux-v5.4/net/9p/ |
| D | Kconfig | 13 See <http://v9fs.sf.net> for more information.
42 bool "Debug information"
44 Say Y if you want the 9P subsystem to log debug information.
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-event_print.txt | 6 tep_print_event - Writes event information into a trace sequence.
21 The _tep_print_event()_ function parses the event information of the given
23 string _fmt_. The desired information is specified after the format string.
38 information
69 TEP_PRINT_INFO, "%s" - event information.
70 TEP_PRINT_INFO_RAW, "%s" - event information, in raw format.
|
| /Linux-v5.4/Documentation/arm/samsung/ |
| D | gpio.rst | 15 See Documentation/arm/samsung-s3c24xx/gpio.rst for more information
34 registering the necessary information for the core gpio configuration
40 See arch/arm/plat-samsung/include/plat/gpio-cfg.h for more information
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | max98373.txt | 13 - maxim,vmon-slot-no : slot number used to send voltage information
18 - maxim,imon-slot-no : slot number used to send current information
21 - maxim,spkfb-slot-no : slot number used to send speaker feedback information
|
| /Linux-v5.4/fs/f2fs/ |
| D | Kconfig | 27 /sys/kernel/debug/f2fs/ contains information about all the partitions
28 mounted as f2fs. Each file shows the whole f2fs information.
31 - major filesystem information managed by f2fs currently
32 - average SIT information about whole segments
84 information and block IO patterns in the filesystem level.
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | jitdump-specification.txt | 17 …a information about the generated code, such as address, size, and name of generated functions, th…
63 * Value 2 : JIT_CODE_DEBUG_INFO: record describing the debug information for a jitted function
65 * Value 4 : JIT_CODE_UNWINDING_INFO: record describing a function unwinding information
119 …cord contains source lines debug information, i.e., a way to map a code address back to a source l…
122 * uint64_t code_addr: address of function for which the debug information is generated
126 The debug_entry describes the source line information. It is defined as follows in order:
127 * uint64_t code_addr: address of function for which the debug information is generated
146 …SE record does not have any specific fields, the record header contains all the information needed.
154 The record is used to describe the unwinding information for a jitted function.
170 …can be used to specify FP based unwinding for a function which does not have unwinding information.
|
| /Linux-v5.4/fs/afs/ |
| D | Kconfig | 11 See <file:Documentation/filesystems/afs.txt> for more information.
21 See <file:Documentation/filesystems/afs.txt> for more information.
40 See <file:Documentation/filesystems/afs.txt> for more information.
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ab8500/ |
| D | btemp.txt | 7 - battery = Shall be battery specific information
15 For information on battery specific node, Ref:
|
12345678910>>...64
