Searched full:interpret (Results 1 – 25 of 511) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-5.10/include/crypto/ |
| D | akcipher.h | 71 * function, which knows how to decode and interpret
74 * function, which knows how to decode and interpret
379 * how to decode and interpret the encoded key and parameters
401 * how to decode and interpret the encoded key and parameters
|
| /kernel/linux/linux-6.6/include/crypto/ |
| D | sig.h | 113 * how to decode and interpret the encoded key and parameters
129 * how to decode and interpret the encoded key and parameters
|
| D | akcipher.h | 96 * function, which knows how to decode and interpret
99 * function, which knows how to decode and interpret
462 * how to decode and interpret the encoded key and parameters
484 * how to decode and interpret the encoded key and parameters
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-camera.rst | 53 is limited by the frame interval. Drivers should interpret the
67 terms of EV, drivers should interpret the values as 0.001 EV units,
131 interpret the values as arc seconds, with valid values between -180
137 should interpret the values as arc seconds, with valid values
337 Applications should interpret the values as standard ISO values
|
| D | pixfmt-intro.rst | 9 interpret the same way. V4L2 includes several such formats, and this
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 10 community will interpret it. We also do not expect this interpretation
156 Because how we interpret and enforce the Code of Conduct will evolve over
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-camera.rst | 54 is limited by the frame interval. Drivers should interpret the
68 terms of EV, drivers should interpret the values as 0.001 EV units,
132 interpret the values as arc seconds, with valid values between -180
138 should interpret the values as arc seconds, with valid values
338 Applications should interpret the values as standard ISO values
|
| D | pixfmt-intro.rst | 9 interpret the same way. V4L2 includes several such formats, and this
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/vboxvideo/ |
| D | vboxvideo.h | 106 /* The value for port IO to let the adapter to interpret the adapter memory. */
109 /* The value for port IO to let the adapter to interpret the adapter memory. */
113 * The value for port IO to let the adapter to interpret the display memory.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/vboxvideo/ |
| D | vboxvideo.h | 106 /* The value for port IO to let the adapter to interpret the adapter memory. */
109 /* The value for port IO to let the adapter to interpret the adapter memory. */
113 * The value for port IO to let the adapter to interpret the display memory.
|
| /kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/runtime/isys/interface/ |
| D | ia_css_isys_comm.h | 35 * communication channel to interpret that opaque handle(this handle is
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/runtime/isys/interface/ |
| D | ia_css_isys_comm.h | 35 * communication channel to interpret that opaque handle(this handle is
|
| /kernel/linux/linux-5.10/arch/x86/platform/olpc/ |
| D | olpc_dt.c | 189 if (olpc_ofw("interpret", args, res)) { in olpc_dt_interpret()
190 pr_err("olpc_dt: interpret failed!\n"); in olpc_dt_interpret()
|
| /kernel/linux/linux-6.6/arch/x86/platform/olpc/ |
| D | olpc_dt.c | 189 if (olpc_ofw("interpret", args, res)) { in olpc_dt_interpret()
190 pr_err("olpc_dt: interpret failed!\n"); in olpc_dt_interpret()
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | fsi.h | 14 * HW status information and interpret it themselves, so this
|
| /kernel/linux/linux-5.10/Documentation/security/tpm/ |
| D | tpm_event_log.rst | 24 to a challenger. However, PCR contents are difficult to interpret;
|
| /kernel/linux/linux-6.6/Documentation/security/tpm/ |
| D | tpm_event_log.rst | 24 to a challenger. However, PCR contents are difficult to interpret;
|
| /kernel/linux/linux-6.6/arch/x86/include/asm/ |
| D | user.h | 40 * xstate_hdr bytes and interpret what states the processor/OS supports
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | user.h | 40 * xstate_hdr bytes and interpret what states the processor/OS supports
|
| /kernel/linux/linux-6.6/arch/arm/include/asm/ |
| D | kgdb.h | 69 * otherwise gdb will not be able to correctly interpret stepping over
|
| /kernel/linux/linux-5.10/arch/x86/include/uapi/asm/ |
| D | kvm_para.h | 39 /* The last 8 bits are used to indicate how to interpret the flags field
|
| /kernel/linux/linux-6.6/arch/arm64/include/asm/ |
| D | traps.h | 86 /* Not a RAS error, we can't interpret the ESR. */ in arm64_ras_serror_get_severity()
|
| /kernel/linux/linux-6.6/fs/smb/client/ |
| D | dns_resolve.c | 59 /* Try to interpret hostname as an IPv4 or IPv6 address */ in dns_resolve_server_name_to_ip()
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/embedded6xx/ |
| D | storcenter.c | 59 /* Interpret the "ranges" property */ in storcenter_add_bridge()
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | kgdb.h | 69 * otherwise gdb will not be able to correctly interpret stepping over
|
12345678910>>...21