/openbmc/qemu/tests/qemu-iotests/ |
H A D | 089.out | 38 === Testing qemu-img info output ===
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/images/firmware-image-juno/ |
H A D | images-r0.txt | 53 NOR7FILE: \SOFTWARE\blank.img ;Image File Name
|
H A D | images-r1.txt | 53 NOR7FILE: \SOFTWARE\blank.img ;Image File Name
|
H A D | images-r2.txt | 53 NOR7FILE: \SOFTWARE\blank.img ;Image File Name
|
/openbmc/linux/Documentation/devicetree/bindings/mmc/ |
H A D | synopsys-dw-mshc.yaml | 17 - img,pistachio-dw-mshc
|
/openbmc/linux/drivers/gpu/drm/nouveau/nvkm/engine/gr/ |
H A D | gm20b.c | 55 const u64 base = lsfw->offset.img + lsfw->app_start_offset; in gm20b_gr_acr_bld_write()
|
/openbmc/qemu/docs/interop/ |
H A D | live-block-operations.rst | 38 ``blockdev-snapshot-sync``, or offline via ``qemu-img``):: 693 $ qemu-img create -f qcow2 -b ./Contents-of-A-B-C.qcow2 \ 808 created (using ``qemu-img``) and attach it to live QEMU via 817 (1) Create the target image (using ``qemu-img``), say, ``e.qcow2`` 836 the target copy with ``qemu-img compare``. You should notice: 858 $ qemu-img create -f qcow2 e.qcow2 39M 999 (1) Create the target image (using ``qemu-img``), say, ``e.qcow2`` 1012 the target copy with ``qemu-img compare``. You should notice: 1046 $ qemu-img create -f qcow2 e.qcow2 39M 1103 ``qemu-img compare`` to verify the integrity of the disk image [all …]
|
H A D | bitmaps.rst | 729 $ qemu-img create -f qcow2 drive0.inc0.qcow2 \ 802 $ qemu-img create -f qcow2 drive0.inc1.qcow2 \ 895 $ qemu-img create -f qcow2 drive0.inc2.qcow2 64G 958 $ qemu-img rebase drive0.inc2.qcow2 \ 979 $ qemu-img create -f qcow2 drive0.full.qcow2 64G 980 $ qemu-img create -f qcow2 drive1.full.qcow2 64G 1093 $ qemu-img create -f qcow2 drive0.inc0.qcow2 \ 1095 $ qemu-img create -f qcow2 drive1.inc0.qcow2 \ 1226 $ qemu-img create -f qcow2 drive0.inc0.qcow2 \ 1308 $ qemu-img create -f qcow2 drive0.inc0.qcow2 \
|
/openbmc/openbmc/meta-security/docs/ |
H A D | dm-verity.txt | 26 IMAGE_CLASSES += "dm-verity-img" 32 which will source features/device-mapper/dm-verity.scc when dm-verity-img
|
/openbmc/openbmc/poky/scripts/lib/wic/plugins/imager/ |
H A D | direct.py | 520 with open(device, 'r+b') as img: 521 img.seek(0x1B8) 522 img.write(identifier.to_bytes(4, 'little'))
|
/openbmc/qemu/docs/system/arm/ |
H A D | aspeed.rst | 151 -blockdev node-name=fmc0,driver=file,filename=/path/to/fmc0.img \ 153 -blockdev node-name=fmc1,driver=file,filename=/path/to/fmc1.img \ 155 -blockdev node-name=spi1,driver=file,filename=/path/to/spi1.img \
|
/openbmc/linux/drivers/infiniband/hw/qib/ |
H A D | qib_sd7220.c | 859 const u8 *img, int len, int offset) in qib_sd7220_prog_ld() argument 869 (u8 *)img + sofar, req, 0); in qib_sd7220_prog_ld() 883 const u8 *img, int len, int offset) in qib_sd7220_prog_vfy() argument 902 if (readback[idx] != img[idx+sofar]) in qib_sd7220_prog_vfy()
|
/openbmc/phosphor-webui/app/common/styles/directives/ |
H A D | app-navigation.scss | 102 img {
|
/openbmc/qemu/pc-bios/s390-ccw/ |
H A D | netboot.mak | 16 s390-netboot.img: s390-netboot.elf
|
/openbmc/qemu/docs/system/s390x/ |
H A D | bootdevices.rst | 85 Beside the normal guest firmware (which is loaded from the file ``s390-ccw.img`` 88 firmware is loaded from a file called ``s390-netboot.img`` in the QEMU data
|
/openbmc/linux/arch/arm64/boot/dts/freescale/ |
H A D | imx8qm.dtsi | 425 #include "imx8-ss-img.dtsi" 431 #include "imx8qm-ss-img.dtsi"
|
/openbmc/u-boot/doc/ |
H A D | README.rockchip | 135 sudo dd if=firefly-rk3288/u-boot-dtb.img of=/dev/sdc seek=16384 202 sudo dd if=u-boot-dtb.img of=/dev/mmcblk0 seek=16384 263 cat spl-out.bin chromebook_jerry/u-boot-dtb.img >out.bin && \ 348 u-boot-dtb.img to the SD card at that offset. See above for instructions.
|
/openbmc/qemu/docs/system/riscv/ |
H A D | sifive_u.rst | 235 image sdcard.img { 261 image spi-nor.img { 296 -drive file=/path/to/sdcard.img,if=sd 305 -drive file=/path/to/spi-nor.img,if=mtd
|
/openbmc/qemu/docs/ |
H A D | meson.build | 52 'qemu-img.1': (have_tools ? 'man1' : ''),
|
H A D | qcow2-cache.txt | 30 The 'qemu-img create' command supports specifying the size using the 33 qemu-img create -f qcow2 -o cluster_size=128K hd.qcow2 4G 71 qemu-img create -f qcow2 -o refcount_bits=8 hd.qcow2 4G
|
/openbmc/linux/Documentation/devicetree/bindings/clock/ |
H A D | imx8qxp-lpcg.yaml | 41 - fsl,imx8qxp-lpcg-img
|
/openbmc/linux/drivers/input/rmi4/ |
H A D | rmi_f34.h | 267 struct image_metadata img; member
|
/openbmc/linux/drivers/dma/ |
H A D | Makefile | 43 obj-$(CONFIG_IMG_MDC_DMA) += img-mdc-dma.o
|
/openbmc/linux/drivers/pwm/ |
H A D | Makefile | 22 obj-$(CONFIG_PWM_IMG) += pwm-img.o
|
/openbmc/u-boot/board/freescale/t208xqds/ |
H A D | README | 246 0x000000 0x0FFFFF U-Boot img 1MB (2 blocks) 254 0x008 2048 U-Boot img 1MB 262 0x000000 0x0FFFFF U-Boot img 1MB
|