Home
last modified time | relevance | path

Searched refs:its (Results 1 – 25 of 139) sorted by relevance

123456

/rk3399_rockchip-uboot/scripts/
H A Dbuild-tftp-firmware.sh102 rm -f *${SUFFIX} *.itb *.its *.dtb *.dts data2sign* *.hdr *.hash orderlist.txt
176 cat > update.its << EOF
197 };" >> update.its
210 };" >> update.its
220 cat >> update.its << EOF
248 cp update.its key.its
249 sed -i "/data =/d" key.its
250 dtc -I dts -O dtb key.its -o key.dtb
252 ./mkimage -f update.its -k keys/ -K key.dtb -E -p ${HDR_SIZE} -r update.itb -v ${ARG_VERSION}
256 ./mkimage -f update.its -E -p ${HDR_SIZE} update.itb -v ${ARG_VERSION}
[all …]
/rk3399_rockchip-uboot/doc/uImage.FIT/
H A Dhowto.txt22 for its latest version. mkimage (together with dtc) takes as input
24 its various properties used during booting. By convention, image source file
25 has the ".its" extension, also, the details of its format are given in
37 - image source file (*.its)
60 If a platform specific image source file (.its) is shipped with the U-Boot
77 doc/uImage.FIT/kernel.its (note that kernel.its assumes that vmlinux.bin.gz is
79 specified in the kernel.its file). Here's how to create the image and inspect
80 its contents:
83 $ mkimage -f kernel.its kernel.itb
84 DTC: dts->dtb on file "kernel.its"
[all …]
H A Dsource_file_format.txt58 .its - image tree source
64 image source file (.its) and a set of data files. Image is created with the
70 tqm5200.its
78 - create .its file, automatically filled-in properties are omitted
79 - call mkimage tool on a .its file
261 of strings. U-Boot will load each binary at its given start-address and
263 on its component image node type.
301 Please see doc/uImage.FIT/*.its for actual image source files.
/rk3399_rockchip-uboot/doc/device-tree-bindings/serial/
H A Dsandbox-serial.txt3 The sandbox serial device is an emulated device which displays its output
4 on the host machine's console, and accepts input from its keyboard.
/rk3399_rockchip-uboot/test/py/tests/
H A Dtest_fit.py168 its = make_fname('test.its')
169 with open(its, 'w') as fd:
171 return its
186 its = make_its(params)
187 util.run_and_log(cons, [mkimage, '-f', its, fit])
H A Dtest_vboot.py80 def make_fit(its): argument
89 '%s%s' % (datadir, its), fit])
/rk3399_rockchip-uboot/arch/mips/mach-bmips/
H A DKconfig94 Between its different peripherals there's an integrated switch with 4
105 Between its different peripherals there's a BCM5325 switch with 4
116 Between its different peripherals there's an integrated switch with 4
127 Between its different peripherals there's a BCM5325 switch with 4
138 Between its different peripherals there's a BCM53115 switch with 4
149 Between its different peripherals there's a BCM5325 switch with 4
160 Between its different peripherals there's a BCM5325 switch with 4
/rk3399_rockchip-uboot/doc/
H A DREADME.update48 Since the update file is in FIT format, it is created from an *.its file using
60 Example .its files
63 - doc/uImage.FIT/update_uboot.its
70 'update_uboot.its' file is where the U-Boot is stored in Flash, the
73 mkimage -f update_uboot.its update_uboot.itb
91 - doc/uImage.FIT/update3.its
H A DREADME.vxworks24 From VxWorks 7, VxWorks starts adopting device tree as its hardware decription
45 board-specific address before loading VxWorks. U-Boot supplies its address
48 parameter called BOOT_LINE_ADRS. Assign its value to "bootaddr". A typical
51 If a "bootargs" variable is defined, its content will be copied to the memory
H A DREADME.menu9 console, and an entry can be selected by entering its label.
29 * preventing consumers of the menu interfaces from accessing its
69 * menu_destroy() - frees the memory used by a menu and its items.
H A DREADME.bcm7xxx47 mkimage -f image.its image.itb
58 image.its:
112 * done its runtime modifications to it. For
H A DREADME.sh7752evb28 This board has the following its specific command:
H A DREADME.sh7753evb28 This board has the following its specific command:
/rk3399_rockchip-uboot/lib/efi/
H A DKconfig8 application, with U-Boot using EFI's drivers instead of its own.
33 Set the amount of EFI RAM which is claimed by U-Boot for its own
/rk3399_rockchip-uboot/doc/driver-model/
H A DMIGRATION.txt4 U-Boot has been migrating to a new driver model since its introduction in
H A Dusb-info.txt48 Each has its own data value. Controllers must be in the UCLASS_USB uclass.
57 The driver can use priv_auto_alloc_size to set the size of its private data.
73 each controller will be probed and its bus scanned.
119 possible to power up a hub and find out which of its ports have devices
127 setting its address to the next available address. The USB bus stretches out
225 speed) in its parent platform data. We cannot store it its private data
230 intended to set up a child device ready to be used with its parent bus. For
263 all of its downstream devices also
290 As an example of a USB device driver, see usb_storage.c. It uses its own
370 flash stick to emulate on one of its ports.
/rk3399_rockchip-uboot/arch/x86/dts/
H A Dcrownbay.dts186 * PCIe port 0, so its bus number is 1
187 * for its PCIe port and 2 for its PCI
/rk3399_rockchip-uboot/drivers/video/drm/
H A DKconfig174 support LVDS, rgb, dual LVDS output mode. say Y to enable its
183 say Y to enable its driver.
192 bridge chips driver. say Y to enable its driver.
199 bridge chips driver. say Y to enable its driver.
208 bridge chips driver. say Y to enable its driver.
/rk3399_rockchip-uboot/tools/env/
H A DREADME11 the same program and its function depends on its basename.
/rk3399_rockchip-uboot/fs/fat/
H A DKconfig6 It is useful mainly for its wide compatibility with various operating
/rk3399_rockchip-uboot/board/freescale/common/
H A Dfsl_validate.c344 u32 its = sfp_in32(&sfp_regs->ospr) >> 2; in fsl_secboot_header_verification_failure() local
346 if (its == 1) in fsl_secboot_header_verification_failure()
368 u32 its = (sfp_in32(&sfp_regs->ospr) & ITS_MASK) >> ITS_BIT; in fsl_secboot_image_verification_failure() local
370 if (its == 1) { in fsl_secboot_image_verification_failure()
/rk3399_rockchip-uboot/
H A Dmake.sh663 cp ${SPL_FIT_SOURCE} u-boot.its
668 ${SPL_FIT_GENERATOR} u-boot.dtb > u-boot.its
670 … ${SPL_FIT_GENERATOR} ${TEE_ARG} ${COMPRESSION_ARG} ${INIT_ARG} ${MCU_ARG} ${LOAD_ARG} > u-boot.its
674 ./tools/mkimage -f u-boot.its -E u-boot.itb >/dev/null 2>&1
/rk3399_rockchip-uboot/arch/arm/mach-rockchip/rk3399/
H A DKconfig20 supply and exposing its external interfaces on a MXM-230
/rk3399_rockchip-uboot/board/technexion/pico-imx7d/
H A DREADME31 Then U-Boot starts and its messages appear in the console program.
/rk3399_rockchip-uboot/board/renesas/sh7757lcr/
H A DREADME.sh7757lcr29 This board has the following its specific command:

123456