Home
last modified time | relevance | path

Searched full:information (Results 1 – 25 of 4313) sorted by relevance

12345678910>>...173

/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-driver-ufs19 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/drivers/net/ethernet/intel/
DKconfig29 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/
Dreporting-bugs.rst64 :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 …]
Dsecurity-bugs.rst22 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/drivers/scsi/qedf/
Dqedf_hsi.h25 * FCoE CQ element ABTS information
47 * FCoE CMDQ element control information
92 * FCoE CQ element response information
112 * FCoE CQ element Target completion information
136 * FCoE CQ element middle path information
146 * FCoE CQ element unsolicited information
149 /* BD information: Physical address and opaque data */
160 /* BD information: Physical address and opaque data */
169 * FCoE CQ element information
172 struct fcoe_cqe_rsp_info rsp_info /* Response completion information */;
[all …]
/Linux-v5.4/drivers/clk/ingenic/
Dcgu.h18 * struct ingenic_cgu_pll_info - information about a PLL
58 * struct ingenic_cgu_mux_info - information about a clock mux
71 * struct ingenic_cgu_div_info - information about a divider
98 * struct ingenic_cgu_fixdiv_info - information about a fixed divider
106 * struct ingenic_cgu_gate_info - information about a clock gate
120 * struct ingenic_cgu_custom_info - information about a custom (SoC) clock
128 * struct ingenic_cgu_clk_info - information about a clock
134 * @pll: information valid if type includes CGU_CLK_PLL
135 * @gate: information valid if type includes CGU_CLK_GATE
136 * @mux: information valid if type includes CGU_CLK_MUX
[all …]
/Linux-v5.4/arch/arm/mach-ixp4xx/
DKconfig27 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/fb/
Dapi.rst24 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/fs/fscache/
DKconfig11 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/wireless/broadcom/brcm80211/brcmfmac/
Dcfg80211.h99 /* security information with currently associated ap */
114 * struct brcmf_cfg80211_profile - profile information.
117 * @sec: security information.
118 * @key: key information
170 * struct brcmf_cfg80211_vif - virtual interface specific information.
174 * @profile: profile information.
222 * struct brcmf_cfg80211_vif_event - virtual interface event information.
238 * struct brcmf_cfg80211_wowl - wowl related information.
264 * @p2p: peer-to-peer specific information.
265 * @btcoex: Bluetooth coexistence information.
[all …]
/Linux-v5.4/arch/h8300/
DKconfig.cpu37 More Information. (Japanese Only)
40 More Information.
50 More Information. (Japanese Only)
59 More Information. (Japanese Only)
68 More Information.
77 More Information.
87 More Information.
/Linux-v5.4/drivers/scsi/isci/
Dphy.h232 * optional information that can be retrieved for a specific phy.
238 * This PHY information field tracks the number of frames received.
243 * This PHY information field tracks the number of frames transmitted.
248 * This PHY information field tracks the number of DWORDs received.
253 * This PHY information field tracks the number of DWORDs transmitted.
258 * This PHY information field tracks the number of times DWORD
264 * This PHY information field tracks the number of received DWORDs with
270 * This PHY information field tracks the number of received frames with a
276 * This PHY information field tracks the number of DONE (ACK/NAK TIMEOUT)
282 * This PHY information field tracks the number of DONE (ACK/NAK TIMEOUT)
[all …]
/Linux-v5.4/Documentation/sound/designs/
Dprocfile.rst10 ALSA has its own proc tree, /proc/asound. Many useful information are
18 Global Information
67 like pcm0p or pcm1c. They hold the PCM information for each PCM
89 The general information of this PCM device: card #, device #,
124 The general information of this PCM sub-stream.
137 The buffer pre-allocation information.
144 AC97 Codec Information
148 Shows the general information of this AC97 codec chip, such as
168 of the given card. This information is very useful for debugging.
175 Shows the general codec information and the attribute of each
[all …]
/Linux-v5.4/Documentation/vm/
Dpage_owner.rst12 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/tools/perf/Documentation/
Djitdump-specification.txt17 …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/security/
DKconfig.hardening16 information at:
48 and information exposures.
57 uninitialized stack variable exploits and information
70 of uninitialized stack variable exploits and information
88 of uninitialized stack variable exploits and information
97 of uninitialized stack variable exploits and information
122 potential for uninitialized stack variable exploits or information
134 This plugin was ported from grsecurity/PaX. More information at:
158 previous syscalls. Although this information is not precise, it
/Linux-v5.4/fs/f2fs/
DKconfig23 bool "F2FS Status Information"
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/Documentation/admin-guide/auxdisplay/
Dks0108.rst13 1. DRIVER INFORMATION
14 2. DEVICE INFORMATION
18 1. Driver Information
24 2. Device Information
48 your LCD specific wiring information in the same folder.
/Linux-v5.4/drivers/misc/mic/card/
Dmic_device.h35 * struct mic_irq_info - OS specific irq information
45 * struct mic_device - MIC device information.
47 * @mmio: MMIO bar information.
54 * struct mic_driver - MIC card driver information.
60 * @mdev: MIC device information for the host.
62 * @irq_info: The OS specific irq information
63 * @intr_info: H/W specific interrupt information.
/Linux-v5.4/drivers/misc/mic/
DKconfig17 More information about the Intel MIC family as well as the Linux
34 More information about the Intel MIC family as well as the Linux
50 More information about the Intel MIC family as well as the Linux
70 More information about the Intel MIC family as well as the Linux
90 For more information see
109 More information about the Intel MIC family as well as the Linux
127 More information about the Intel MIC family as well as the Linux
148 More information about the Intel MIC family as well as the Linux
/Linux-v5.4/drivers/mtd/ubi/
Dattach.c14 * The attaching information is represented by a &struct ubi_attach_info'
15 * object. Information about volumes is represented by &struct ubi_ainf_volume
88 * @ai: attaching information
152 * ubi_find_or_add_av - search for a volume in the attaching information and
154 * @ai: attaching information
169 * @ai: attaching information
173 * Allocate an aeb object and initialize the pnum and ec information.
197 * @ai: attaching information
210 * @ai: attaching information
259 * @ai: attaching information
[all …]
/Linux-v5.4/drivers/staging/comedi/drivers/ni_routing/
DREADME30 One additional major challenge is that this information does not seem to be
34 information is through the proprietary NI-MAX software, which currently only
35 runs on Windows platforms. A further challenge is that this information
43 information _and_ the knowledge of valid routes per device, a few specific
49 documentation, (b) NI's user-level code, (c) the information as provided by
96 As noted above, the only known consistent source of information for
98 Windows software, NI-MAX. Also, as noted above, this information can
109 ni_device_routes.c to include this information into comedi.
119 As noted above, the only consistent source of information of valid
121 software, NI-MAX. Also, as noted above, this information can only be
[all …]
/Linux-v5.4/arch/arm/mach-s3c24xx/
Diotiming-s3c2410.c205 * s3c2410_calc_bank - calculate bank timing information
207 * @bt: The bank timing information.
210 * setting for the @cfg timing. This updates the timing information
284 * s3c2410_iotiming_getbank - turn BANKCON into cycle time information
289 * in @cfg, update the cycle timing information.
305 * s3c2410_iotiming_debugfs - debugfs show io bank timing information
308 * @iob: The IO bank information to decode.
351 * @iot: The IO timing information to fill out.
354 * frequency information in @cfg. This is then used by s3c2410_iotiming_set()
393 * @iot: The IO timing information to use.
[all …]
/Linux-v5.4/drivers/scsi/megaraid/
Dmbox_defs.h220 * @reqsensearea : Sense information buffer
273 * @reqsensearea : Sense information buffer
304 * mraid_pinfo_t - product info, static information about the controller
321 * This structures holds the information about the controller which is not
424 * mraid_inquiry3_t - enquiry for device information
477 * mraid_adapinfo_t - information about the adapter
526 * mraid_ldrv_info_t - information about the logical drives
543 * mraid_pdrv_info_t - information about the physical drives
554 * @mraid_adapinfo_t : adapter information
555 * @mraid_ldrv_info_t : logical drives information
[all …]
/Linux-v5.4/Documentation/media/uapi/v4l/
Dyuv-formats.rst17 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.

12345678910>>...173