u-boot/drivers/fastboot
Tom Rini a077ac13d0 Kconfigs: Correct default of "0" on hex type entries
It is not a parse error to have a default value of "0" for a "hex" type
entry, instead of "0x0".  However, "0" and "0x0" are not treated the
same even by the tools themselves. Correct this by changing the default
value from "0" to "0x0" for all hex type questions that had the
incorrect default. Fix one instance (in two configs) of a default of "0"
being used on a hex question to be "0x0". Remove the cases where a
defconfig had set a value of "0x0" to be used as the default had been
"0".

Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
2023-08-09 09:21:42 -04:00
..
fb_command.c Correct SPL uses of FASTBOOT_FLASH_NAND 2023-02-10 07:41:41 -05:00
fb_common.c fastboot: Only call the bootm command if it is enabled 2023-05-31 17:23:01 -04:00
fb_getvar.c Revert "lib: string: Fix strlcpy return value", fix callers 2023-08-08 17:05:43 -04:00
fb_mmc.c lib: sparse: allocate FASTBOOT_MAX_BLK_WRITE instead of small number 2023-07-25 12:44:46 -04:00
fb_nand.c Audit <flash.h> inclusion 2022-08-04 16:18:47 -04:00
Kconfig Kconfigs: Correct default of "0" on hex type entries 2023-08-09 09:21:42 -04:00
Makefile Revert "fastboot: Add default fastboot_set_reboot_flag implementation" 2021-02-07 19:22:54 +01:00