Home
last modified time | relevance | path

Searched refs:blobs (Results 1 – 27 of 27) sorted by relevance

/linux-4.4.14/drivers/staging/rtl8192e/rtl8192e/
Dr8192E_firmware.c169 if (pfirmware->blobs[i].size == 0) { in rtl92e_init_fw()
181 &pfirmware->blobs[i], in rtl92e_init_fw()
188 mapped_file = pfirmware->blobs[i].data; in rtl92e_init_fw()
189 file_length = pfirmware->blobs[i].size; in rtl92e_init_fw()
Dr8192E_firmware.h56 struct rt_fw_blob blobs[FW_BLOBS]; member
/linux-4.4.14/drivers/gpu/drm/tilcdc/
DKconfig17 bool "Support device tree blobs using TI LCDC Slave binding"
24 with device tree blobs using the obsolete "ti,tilcdc,slave"
/linux-4.4.14/security/keys/
DKconfig62 see encrypted blobs.
80 Userspace only ever sees/stores encrypted blobs.
/linux-4.4.14/Documentation/EDID/
DHOWTO.txt22 1680x1050, 1920x1080) as binary blobs, but the kernel source tree does
24 of the built-in binary EDID blobs and to facilitate the creation of
/linux-4.4.14/Documentation/security/
Dkeys-trusted-encrypted.txt6 stores, and loads only encrypted blobs. Trusted Keys require the availability
8 Keys can be used on any system. All user level blobs, are displayed and loaded
17 blobs under different PCR values, so multiple boots are easily supported.
Dkeys.txt137 blobs of data. These can be created, updated and read by userspace,
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt27 The interface allows guest firmware to download various parameters and blobs
34 the QEMU source code; the structure of the data blobs corresponding to the
/linux-4.4.14/Documentation/ko_KR/
Dstable_api_nonsense.txt56 먼저, 나는 closed 소스, hidden 소스, binary blobs, 소스 wrappers, 또는 GPL로
/linux-4.4.14/drivers/base/
DKconfig89 bool "Include in-kernel firmware blobs in kernel binary"
93 The kernel source tree includes a number of firmware 'blobs'
114 string "External firmware blobs to build into the kernel binary"
141 string "Firmware blobs root directory"
/linux-4.4.14/crypto/asymmetric_keys/
DKconfig36 This option provides support for parsing X.509 format blobs for key
/linux-4.4.14/drivers/input/touchscreen/
Dsur40.c91 struct sur40_blob blobs[]; member
305 struct sur40_blob *inblob = &sur40->bulk_in_buffer->blobs[0]; in sur40_poll()
/linux-4.4.14/drivers/gpu/drm/
Ddrm_fops.c224 INIT_LIST_HEAD(&priv->blobs); in drm_open_helper()
Ddrm_crtc.c4303 list_for_each_entry_safe(blob, bt, &file_priv->blobs, head_file) { in drm_property_destroy_user_blobs()
4539 list_add_tail(&blob->head_file, &file_priv->blobs); in drm_mode_createblob_ioctl()
4581 list_for_each_entry(bt, &file_priv->blobs, head_file) { in drm_mode_destroyblob_ioctl()
/linux-4.4.14/Documentation/kbuild/
Dkbuild.txt157 INSTALL_FW_PATH specifies where to install the firmware blobs.
Dmakefiles.txt1159 into vmlinux. Device tree blobs linked into vmlinux are placed
/linux-4.4.14/include/drm/
DdrmP.h346 struct list_head blobs; member
/linux-4.4.14/drivers/net/wireless/ath/wil6210/
Dwil6210.h625 struct debugfs_blob_wrapper blobs[ARRAY_SIZE(fw_mapping)]; member
Ddebugfs.c1414 struct debugfs_blob_wrapper *blob = &wil->blobs[i]; in wil6210_debugfs_init_blobs()
/linux-4.4.14/Documentation/filesystems/
Ddebugfs.txt135 debugfs_blob_wrapper structure. Some drivers use "blobs" as a simple way
/linux-4.4.14/Documentation/
Dstable_api_nonsense.txt37 source, hidden source, binary blobs, source wrappers, or any other term
/linux-4.4.14/Documentation/networking/
Drxrpc.txt40 layer which renders structured data to binary blobs and back again using XDR
71 left to the application. AF_RXRPC only deals in blobs. Even the operation ID
130 (*) The data blobs are of indefinite size, the end of a phase is marked with a
/linux-4.4.14/Documentation/crypto/
Dasymmetric-keys.txt35 for extracting information from the blobs of data passed to the instantiation
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES996 Began implementing support for SPNEGO encapsulation of NTLMSSP based session authentication blobs
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt1063 resulting device-tree "blobs" have not yet been validated with the
/linux-4.4.14/arch/x86/
DKconfig1141 initrd for microcode blobs.
/linux-4.4.14/Documentation/virtual/kvm/
Dapi.txt747 blobs in userspace. When the guest writes the MSR, kvm copies one