Searched full:blob (Results 1 – 25 of 130) sorted by relevance
123456
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 31 The only legacy blob displayed is the fw_cfg device revision:
51 blob's 'file name' in the fw_cfg directory.
52 size The length of the blob, as given in the fw_cfg
54 key The value of the blob's selector key as given in the
57 raw The raw bytes of the blob, obtained by selecting the
59 of bytes equal to the blob size from the data
68 to give each blob a descriptive name. For example::
85 blob names, ending in symlinks to the by_key entry for each
96 of fw_cfg blob names are always "well behaved". I.e., there is
98 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 | 9 report_desc blob corresponding to HID report descriptors
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | brcm,bcm4377-bluetooth.yaml | 39 brcm,taurus-cal-blob:
41 description: A per-device calibration blob for the Bluetooth radio. This
44 This blob is used if the chip stepping of the Bluetooth module does not
47 brcm,taurus-bf-cal-blob:
49 description: A per-device calibration blob for the Bluetooth radio. This
52 This blob is used if the chip stepping of the Bluetooth module supports
|
| /Documentation/devicetree/bindings/iio/chemical/ |
| D | senseair,sunrise.yaml | 17 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/PSP11704.pdf
18 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/PSH11649.pdf
19 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/TDE5531.pdf
20 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Market/publicerat/TDE7318.pdf
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 71 environment. Only basic blob key encryption is executed there.
79 values, and only unsealed by the TPM, if PCRs and blob integrity
221 pcrlock= pcr number to be extended to "lock" blob
275 specific to this DCP key-blob implementation. The key length for new keys is
329 $ keyctl pipe 440502848 > kmk.blob
331 Load a trusted key from the saved blob::
333 $ keyctl add trusted kmk "load `cat kmk.blob`" @u
348 $ keyctl update 268728824 "update pcrinfo=`cat pcr.blob`"
383 $ keyctl pipe 159771175 > evm.blob
385 Load an encrypted key "evm" from saved blob::
[all …]
|
| 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
947 ``max_*_size`` indicate the maximum sizes in bytes of a blob of data to be
948 signed, a signature blob, a blob to be encrypted and a blob to be
958 * Encrypt, decrypt, sign or verify a blob using an asymmetric key::
985 blob of data. For encryption and verification, the asymmetric key may
1014 ``enc=<encoding>`` The encoding of the encrypted/signature blob. This
1190 callout_info is a blob of length callout_len, if given (the length may be
[all …]
|
| /Documentation/arch/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
75 tree blob inside the image.
93 Image types which embed a device tree blob (simpleImage, dtbImage, treeImage,
94 and cuImage) all generate the device tree blob from a file in the
|
| /Documentation/gpu/xe/ |
| D | xe_firmware.rst | 22 GuC CTB Blob
26 :doc: GuC CTB Blob
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 38 function. The first data parser that recognises the blob gets to set the
41 A data parser may interpret the data blob as containing the bits representing a
233 blob of data that holds the key data. It would have to parse it and error
234 check it each time it wanted to use it. Further, the contents of the blob may
238 Also, the blob may represent a pointer to some hardware containing the key
241 Examples of blob formats for which parsers could be implemented include:
291 The instantiation data is in a blob pointed to by data and is datalen in
294 recognise the blob format and will not return -EBADMSG to indicate it is
297 If the parser is happy with the blob, it should propose a description for
|
| /Documentation/devicetree/bindings/clock/ |
| D | clock-bindings.txt | 2 https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
| D | thead,th1520-clk-ap.yaml | 14 …https://openbeagle.org/beaglev-ahead/beaglev-ahead/-/blob/main/docs/TH1520%20System%20User%20Manua…
|
| /Documentation/iio/ |
| D | bno055.rst | 28 the IMU has successfully autocalibrated) and to the calibration data blob.
30 The user can save this blob in a firmware file (i.e. in /lib/firmware) that
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 67 is used to compile the DT source file (testcases.dts) into a binary blob
70 After that, using the following rule the binary blob above is wrapped as an
134 __dtb_testcases_begin - address marking the start of test data blob
135 __dtb_testcases_end - address marking the end of test data blob
138 blob. And finally, if the machine's device tree (i.e live tree) is present,
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | cw2015_battery.yaml | 30 of this binary blob is kept secret by CellWise. The only way to obtain
32 back a test report with the binary blob.
|
| /Documentation/arch/sh/ |
| D | booting.rst | 7 address of the device tree blob in r4. Since legacy bootloaders did not
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | brcm,bcm4329-fmac.yaml | 93 the CLM blob firmware uses ISO3166 country codes as well, and that all
99 brcm,cal-blob:
101 description: A per-device calibration blob for the Wi-Fi radio. This
|
| /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/arch/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/virt/coco/ |
| D | sev-guest.rst | 138 and snp_ext_report_req.certs_address will contain the certificate blob. If the
139 length of the blob is smaller than expected then snp_ext_report_req.certs_len will
142 See GHCB specification for further detail on how to parse the certificate blob.
206 - Its address is obtained via bootloader/firmware (via CC blob), and those
|
| /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.
|
123456