Searched full:blob (Results 1 – 25 of 58) sorted by relevance
123
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 30 The only legacy blob displayed is the fw_cfg device revision:
49 blob's 'file name' in the fw_cfg directory.
50 size : The length of the blob, as given in the fw_cfg
52 key : The value of the blob's selector key as given in the
55 raw : The raw bytes of the blob, obtained by selecting the
57 of bytes equal to the blob size from the data
65 to give each blob a descriptive name. For example:
82 blob names, ending in symlinks to the by_key entry for each
93 of fw_cfg blob names are always "well behaved". I.e., there is
95 a dirname component of another fw_cfg blob, in which case the
|
| D | sysfs-firmware-ofw | 35 Exports the FDT blob that was passed to the kernel by
37 as kexec to access the raw binary. This blob is also
39 made to the blob by the bootloader.
48 blob, and verified at late_initcall time. The sysfs
50 i.e., if the FDT blob has not been modified in the mean
|
| D | sysfs-firmware-gsmi | 29 This file takes a binary blob and passes it onto
34 requirement is that the blob be prefixed with a
|
| D | configfs-usb-gadget-hid | 8 report_desc - blob corresponding to HID report descriptors
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 15 (integrity measurement) values, and only unsealed by the TPM, if PCRs and blob
64 pcrlock= pcr number to be extended to "lock" blob
137 $ keyctl pipe 440502848 > kmk.blob
139 Load a trusted key from the saved blob::
141 $ keyctl add trusted kmk "load `cat kmk.blob`" @u
156 $ keyctl update 268728824 "update pcrinfo=`cat pcr.blob`"
190 $ keyctl pipe 159771175 > evm.blob
192 Load an encrypted key "evm" from saved blob::
194 $ keyctl add encrypted evm "load `cat evm.blob`" @u
|
| D | core.rst | 70 blob of data.
76 called with a blob of data, and that then creates the key's payload in
81 attached payload back into a blob of data.
131 blob of data. It is intended as a place to store secrets which are
943 ``max_*_size`` indicate the maximum sizes in bytes of a blob of data to be
944 signed, a signature blob, a blob to be encrypted and a blob to be
954 * Encrypt, decrypt, sign or verify a blob using an asymmetric key::
981 blob of data. For encryption and verification, the asymmetric key may
1010 ``enc=<encoding>`` The encoding of the encrypted/signature blob. This
1129 callout_info is a blob of length callout_len, if given (the length may be
[all …]
|
| D | ecryptfs.rst | 67 $ keyctl pipe 19184530 > ecryptfs.blob
|
| /Documentation/powerpc/ |
| D | bootwrapper.rst | 29 tree). This image embeds a device tree blob inside
47 dtbImage.%: Similar to zImage, except device tree blob is embedded
67 a device tree blob. This image is a flat binary that
97 tree blob inside the image.
115 Image types which embed a device tree blob (simpleImage, dtbImage, treeImage,
116 and cuImage) all generate the device tree blob from a file in the
|
| D | qe_firmware.rst | 47 The term 'firmware' refers to a binary blob that contains the microcode as
176 embedded into a binary blob. This blob is passed to the qe_upload_firmware()
177 function, which parses the blob and performs everything necessary to upload
|
| /Documentation/devicetree/ |
| D | of_unittest.txt | 40 is used to compile the DT source file (testcases.dts) into a binary blob
43 After that, using the following rule the binary blob above is wrapped as an
106 __dtb_testcases_begin - address marking the start of test data blob
107 __dtb_testcases_end - address marking the end of test data blob
110 blob. And finally, if the machine's device tree (i.e live tree) is present,
|
| /Documentation/crypto/ |
| D | asymmetric-keys.txt | 37 function. The first data parser that recognises the blob gets to set the
40 A data parser may interpret the data blob as containing the bits representing a
237 blob of data that holds the key data. It would have to parse it and error
238 check it each time it wanted to use it. Further, the contents of the blob may
242 Also, the blob may represent a pointer to some hardware containing the key
245 Examples of blob formats for which parsers could be implemented include:
295 The instantiation data is in a blob pointed to by data and is datalen in
298 recognise the blob format and will not return -EBADMSG to indicate it is
301 If the parser is happy with the blob, it should propose a description for
|
| /Documentation/devicetree/bindings/mips/pic32/ |
| D | microchip,pic32mzda.txt | 31 - $a1: KSEG0 address of the flattened device-tree blob.
|
| /Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 20 blob in both cases.
|
| /Documentation/driver-api/mei/ |
| D | hdcp.rst | 11 according the HDCP 2.2 spec. The Intel graphics sends the created blob
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-omap.txt | 25 blob so that, all the required data will be used from device tree dts
|
| /Documentation/devicetree/bindings/net/ |
| D | davinci-mdio.txt | 19 blob so that, all the required data will be used from device tree dts
|
| /Documentation/arm/sa1100/ |
| D | assabet.rst | 29 BLOB (http://www.lartmaker.nl/lartware/blob/)
31 BLOB is a bootloader used within the LART project. Some contributed
32 patches were merged into BLOB to add support for Assabet.
|
| /Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 39 - r3: address of a flattened device-tree blob or 0x0.
|
| /Documentation/devicetree/bindings/mips/img/ |
| D | pistachio.txt | 40 - $a1: KSEG0 address of the flattened device-tree blob.
|
| /Documentation/filesystems/ext4/ |
| D | verity.rst | 27 with optionally appended signature blob.
|
| /Documentation/arm64/ |
| D | booting.rst | 50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
161 - x0 = physical address of device tree blob (dtb) in system RAM.
256 kernel image. The device tree blob passed by this CPU must contain
261 properties and insert them into the blob prior to kernel entry.
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 14 https://github.com/sifive/sifive-blocks/blob/v1.0/src/main/scala/devices/uart/UART.scala#L43
|
| /Documentation/devicetree/bindings/net/can/ |
| D | c_can.txt | 35 blob so that, all the required data will be used from device tree dts
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra20-host1x.txt | 134 - nvidia,edid: supplies a binary EDID blob
160 - nvidia,edid: supplies a binary EDID blob
196 - nvidia,edid: supplies a binary EDID blob
239 - nvidia,edid: supplies a binary EDID blob
|
| /Documentation/bpf/ |
| D | btf.rst | 38 The beginning of data blob must be::
56 ``hdr_len`` equal to ``sizeof(struct btf_header)`` when a data blob is
459 * BPF_BTF_LOAD: load a blob of BTF data into kernel
501 Load a blob of BTF data into kernel. A blob of data, described in
612 command BPF_OBJ_GET_INFO_BY_FD, the btf blob, originally loaded into the
615 With the btf blob, ``bpf_map_info``, and ``bpf_prog_info``, an introspection
|
123