| /openbmc/u-boot/doc/ |
| H A D | README.fdt-overlays | 82 2. Load the base blob and overlay blobs
|
| H A D | README.x86 | 63 little bit tricky, as generally it requires several binary blobs which are not
80 First, you need the following binary blobs:
87 You can get these binary blobs by:
89 $ git clone http://review.coreboot.org/p/blobs.git
90 $ cd blobs
100 Make sure all these binary blobs are put in the board directory.
111 First, you need the following binary blobs:
261 You still need two more binary blobs. For Bayley Bay, they can be extracted
944 graphics and still has binary blobs containing Intel code. You should aim to
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/ |
| H A D | phosphor-ipmi-flash_git.bb | 7 phosphor-ipmi-blobs \
|
| /openbmc/qemu/docs/specs/ |
| H A D | vmgenid.rst | 151 The mechanism chosen for this memory sharing is writable fw_cfg blobs.
157 Two fw_cfg blobs are used in this case:
|
| /openbmc/phosphor-ipmi-blobs/test/ |
| H A D | process_unittest.cpp | 33 namespace blobs namespace
|
| /openbmc/u-boot/board/intel/ |
| H A D | Kconfig | 71 It requires some binary blobs - see README.x86 for details.
|
| /openbmc/linux/Documentation/translations/zh_CN/filesystems/ |
| H A D | debugfs.rst | 137 读取此文件将返回由指针指向debugfs_blob_wrapper结构体的数据。一些驱动使用“blobs”
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | meson.build | 130 blobs_dep = dependency('phosphor-ipmi-blobs')
|
| /openbmc/google-misc/subprojects/libcr51sign/src/ |
| H A D | libcr51sign_mauv.c | 371 ctx, intf, payload_blob_offset + offsetof(struct blob, blobs), in find_and_read_image_mauv_data_from_payload()
|
| /openbmc/linux/Documentation/translations/zh_TW/filesystems/ |
| H A D | debugfs.rst | 139 讀取此文件將返回由指針指向debugfs_blob_wrapper結構體的數據。一些驅動使用「blobs」
|
| /openbmc/linux/Documentation/security/keys/ |
| H A D | trusted-encrypted.rst | 8 stores, and loads only encrypted blobs. Trusted Keys require the availability
10 system. All user level blobs, are displayed and loaded in hex ASCII for
69 have many saved blobs under different PCR values, so multiple boots are
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | allocators.rst | 49 over a disk; as the top-level directory/file blobs fill up one block
|
| /openbmc/phosphor-ipmi-blobs/ |
| H A D | ipmi.cpp | 24 namespace blobs namespace
|
| /openbmc/linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 49 string "Build named firmware blobs into the kernel binary"
82 string "Firmware blobs root directory"
|
| /openbmc/linux/security/tomoyo/ |
| H A D | tomoyo.c | 613 .blobs = &tomoyo_blob_sizes,
|
| /openbmc/linux/fs/erofs/ |
| H A D | Kconfig | 123 This permits EROFS to use fscache-backed data blobs with on-demand
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/uc/ |
| H A D | intel_uc_fw.c | 242 const struct uc_fw_platform_requirement *blobs; member
287 fw_blobs = blobs_all[uc_fw->type].blobs; in __uc_fw_auto_select()
339 fw_blobs = blobs_all[type].blobs; in validate_fw_table_type()
|
| /openbmc/linux/drivers/input/touchscreen/ |
| H A D | sur40.c | 91 struct sur40_blob blobs[]; member
460 struct sur40_blob *inblob = &sur40->bulk_in_buffer->blobs[0]; in sur40_poll()
|
| /openbmc/qemu/scripts/ |
| H A D | meson-buildoptions.sh | 346 --enable-install-blobs) printf "%s" -Dinstall_blobs=true ;;
347 --disable-install-blobs) printf "%s" -Dinstall_blobs=false ;;
|
| /openbmc/qemu/docs/devel/ |
| H A D | control-flow-integrity.rst | 95 * TCG creates binary blobs at runtime, with the transformed code.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | erofs.rst | 40 - Support multiple devices to refer to external blobs, which can be used
126 with the same blobs under a given domain ID can share storage.
|
| /openbmc/pldm/tools/fw-update/ |
| H A D | README.md | 4 firmware image blobs into a PLDM firmware update package, as per the DSP0267
|
| /openbmc/u-boot/tools/binman/ |
| H A D | README | 32 So far binman is pretty simple. It supports binary blobs, such as 'u-boot',
131 Binman considers the output files created by mkimage to be binary blobs
169 In most cases x86 images have a lot of binary blobs, 'black-box' code
171 these blobs are not relocatable and must be placed at fixed areas in the
|
| /openbmc/linux/drivers/gpu/drm/ |
| H A D | drm_file.c | 172 INIT_LIST_HEAD(&file->blobs); in drm_file_alloc()
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | microcode.rst | 103 The loading mechanism looks for microcode blobs in
|