Home
last modified time | relevance | path

Searched refs:update (Results 1 – 25 of 184) sorted by relevance

12345678

/u-boot/arch/x86/cpu/intel_common/
A Dmicrocode.c43 struct microcode_update *update) in microcode_decode_node() argument
45 update->data = fdt_getprop(blob, node, "data", &update->size); in microcode_decode_node()
46 if (!update->data) in microcode_decode_node()
126 struct microcode_update cpu, update; in microcode_update_intel() local
167 update.processor_flags); in microcode_update_intel()
175 rev, update.date_code & 0xffff, in microcode_update_intel()
176 (update.date_code >> 24) & 0xff, in microcode_update_intel()
177 (update.date_code >> 16) & 0xff); in microcode_update_intel()
178 if (update.update_revision != rev) { in microcode_update_intel()
184 ucode_base = (ulong)update.data; in microcode_update_intel()
[all …]
/u-boot/doc/
A DREADME.update1 Automatic software update from a TFTP server
10 boot. The update file should be a FIT file, and can contain one or more
11 updates. Each update in the update file has an address in NOR Flash where it
13 TFTP transfer is successful, the hash of each update is verified, and if the
14 verification is positive, the update is stored in Flash.
16 The auto-update feature is enabled by the CONFIG_UPDATE_TFTP macro:
21 Note that when enabling auto-update, Flash support must be turned on. Also,
27 The auto-update feature uses the following configuration knobs:
83 where the update will be placed is correct. Making mistake here and
84 attempting the auto-update can render the system unusable.
[all …]
A DREADME.dfutftp39 for USB based DFU (CONFIG_DFU_*) and DFU TFTP update
40 (CONFIG_DFU_TFTP) described in ./doc/README.update.
46 the update.c code is not enabled (CONFIG_UPDATE_TFTP) by any board in the
82 3. If required, to update firmware on boot, put the "dfu tftp 0 mmc 0" in the
95 To create FIT image for download one should follow the update tftp README file
96 (./doc/README.update) with one notable difference:
101 update@1 {
/u-boot/tools/binman/test/
A D122_entry_expand_twice.dts9 bad-update-contents;
10 bad-update-contents-twice;
18 bad-update-contents;
A D121_entry_expand.dts9 bad-update-contents;
17 bad-update-contents;
A D123_entry_expand_section.dts9 bad-update-contents;
18 bad-update-contents;
A D039_x86_ucode_missing_node2.dts16 update@0 {
19 update@1 {
A D038_x86_ucode_missing_node.dts19 update@0 {
22 update@1 {
A D040_x86_ucode_not_in_image.dts21 update@0 {
24 update@1 {
A D034_x86_ucode.dts22 update@0 {
25 update@1 {
A D049_x86_ucode_spl.dts22 update@0 {
25 update@1 {
A D044_x86_optional_ucode.dts23 update@0 {
26 update@1 {
A D093_x86_tpl_ucode.dts22 update@0 {
25 update@1 {
A D058_x86_ucode_spl_needs_retry.dts29 update@0 {
32 update@1 {
/u-boot/doc/uImage.FIT/
A Dupdate3.its2 * Example Automatic software update file.
12 update-1 {
22 update-2 {
33 update-3 {
A Dupdate_uboot.its2 * Automatic software update for U-Boot
9 description = "Automatic U-Boot update";
13 update-1 {
/u-boot/board/synopsys/hsdk/
A Dconfig.mk15 -d $(srctree)/u-boot-update.txt \
16 $(srctree)/u-boot-update.scr &> /dev/null
29 -d $(srctree)/u-boot-update.txt \
30 $(srctree)/u-boot-update.scr &> /dev/null
/u-boot/board/Marvell/db-88f6820-gp/
A DREADME7 To update the SPI NOR flash, please use the following
11 sf update 2000000 0 60000
14 problems with the "sf update" command. This does not
/u-boot/lib/
A Dmembuff.c22 static int membuff_putrawflex(struct membuff *mb, int maxlen, bool update, in membuff_putrawflex() argument
47 if (update) in membuff_putrawflex()
56 if (update) in membuff_putrawflex()
68 if (update) in membuff_putrawflex()
76 int membuff_putraw(struct membuff *mb, int maxlen, bool update, char **data) in membuff_putraw() argument
82 size = membuff_putrawflex(mb, maxlen, update, &datap, &offset); in membuff_putraw()
99 int membuff_getraw(struct membuff *mb, int maxlen, bool update, char **data) in membuff_getraw() argument
120 if (update) in membuff_getraw()
135 if (update) { in membuff_getraw()
143 maxlen, update, (int)(mb->head - mb->start), in membuff_getraw()
/u-boot/test/py/tests/test_efi_capsule/
A Duboot_bin_env.its2 * Automatic software update for U-Boot
9 description = "Automatic U-Boot environment update";
/u-boot/arch/x86/dts/
A Dcougarcanyon2.dts69 update@0 {
72 update@1 {
75 update@2 {
78 update@3 {
81 update@4 {
/u-boot/include/
A Dmembuff.h67 int membuff_putraw(struct membuff *mb, int maxlen, bool update, char **data);
85 int membuff_getraw(struct membuff *mb, int maxlen, bool update, char **data);
/u-boot/board/synopsys/axs10x/
A Dconfig.mk28 -d $(srctree)/u-boot-update.txt \
29 $(srctree)/u-boot-update.img &> /dev/null
/u-boot/doc/sphinx/
A Dload_config.py53 namespace.update(config)
57 namespace.update(config)
/u-boot/doc/board/emulation/
A Dqemu_capsule_update.rst7 Support has been added for the UEFI capsule update feature which
23 The capsule update feature is enabled with the following configuration
47 e2bb9c06-70e9-4b14-97a3-5a7913176e3f --verbose --update-image-index \
57 Before initiating the firmware update, the efi variables BootNext,
68 Finally, the capsule update can be initiated with the following
71 => efidebug capsule disk-update
97 update::
127 --update-image-index <val> --signer-private-cert \
179 Enable all configs needed for capsule update(listed above)
205 4. Finally, the capsule update can be initiated with the following
[all …]

Completed in 29 milliseconds

12345678