20 Dec, 2018
1 commit
-
To avoid end user executing uboot command through fastboot, the fastboot
command of "ucmd" and "acmd" in the uboot to be flashed into
non-volatile storage device is removed in this partch.Change-Id: I999b8688a53c2201d02979be68266afc110dfb15
Signed-off-by: faqiang.zhu
15 Aug, 2018
1 commit
-
The BCB_SUPPORT is not needed by fastboot to support uuu, change it to
disabled at default. Android header file explicitly enables this
config, so there is no impact to android.Signed-off-by: Ye Li
(cherry picked from commit 36fd8fd0d5f34d69ef9a1a3833f3f052d64a25b3)
13 Jun, 2018
1 commit
-
Porting the FSL android fastboot features from imx u-boot v2017.03 to
support all SoCs: imx6/imx7/imx7ulp/imx8/imx8mSigned-off-by: Ye Li
22 Feb, 2018
1 commit
-
When FASTBOOT is activated, only one the supported device is supported in
code at the same time
- CONFIG_FASTBOOT_FLASH_MMC_DEV
- CONFIG_FASTBOOT_FLASH_NAND_DEVBut Today the choice is not exclusive in Kconfig
and that cause Kconfig issue when :
- CONFIG_FASTBOOT, CONFIG_MMC, CONFIG_NAND are activated
- CONFIG_FASTBOOT_FLASH_MMC_DEV = 0
- CONFIG_FASTBOOT_FLASH_NAND_DEV is not activatedThe patch add a choice in Kconfig to select the FLASH provider
- CONFIG_FASTBOOT_FLASH_MMC
- CONFIG_FASTBOOT_FLASH_NANDSigned-off-by: Patrick Delaunay
Acked-by: Maxime Ripard
07 Dec, 2017
1 commit
-
Now that more and more devices are built using eMMC, providing a way to
easily flash the system without too much hassle seems like a right thing to
do.Since fastboot is the most deployed tool to do that these days, we can just
rely on it to provide a way to flash the various components in the system
(SPL, U-Boot and the system itself) easily, especially since you can upload
the U-Boot hosting the fastboot "server" through FEL.Reviewed-by: Andre Przywara
Signed-off-by: Maxime Ripard
25 Oct, 2017
1 commit
-
Encountered an issue where fastboot can't write to NAND on a CHIP_pro,
the symbol was neither present in the board's config header, nor the
Kconfig, this patch puts it in the Kconfig and defaults on when
SUNXI_NAND is selected.Signed-off-by: Ben Young
Signed-off-by: Maxime Ripard
04 Oct, 2017
2 commits
-
The current code, if there's both an eMMC and an MMC slot available on the
board, will swap the MMC indices based on whether we booted from the eMMC
or the MMC. This way, the MMC we're supposed to boot on will always have
the index 0.However, this causes various issues, for example when using other
components that base their behaviour on the MMC index, such as fastboot.Let's remove that hack, and take the opposite approach. The MMC will always
have the same index, but the bootcmd will pick the same device than the one
we booted from. This is done through the introduction of the mmc_bootdev
environment variable that will be filled by the board code based on the
boot device informations we can get from the SoC.In order to not introduce regressions, we also need to adjust the fastboot
MMC device and the environment device in order to set it to the eMMC, over
the MMC, like it used to be the case.Tested-by: Chen-Yu Tsai
Signed-off-by: Maxime Ripard -
Fastboot need a bunch of options to be operating properly, such as the
g_dnl gadget, the fastboot command, and some options that make sense. Since
fastboot is now part of Kconfig, make sure we have them right.That will also reduce the boilerplate in the defconfigs.
Reviewed-by: Łukasz Majewski
Reviewed-by: Simon Glass
Signed-off-by: Maxime Ripard
02 Sep, 2017
1 commit
-
- Move ANDROID_IMAGE_SUPPORT to top level Kconfig under images as it's
not strictly part of fastboot.
- Add some defaults for the fastboot buffer location and size
- Migrate all options listed in cmd/fastboot/Kconfig
- Cleanup the READMESigned-off-by: Tom Rini
12 Aug, 2017
1 commit
-
Most of this is duplicated in Kconfig help. Add some of that which is not,
and remove the help from the README.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
Reviewed-by: Philipp Tomsich
22 Nov, 2016
2 commits
-
Currently, the fastboot item in menuconfig is a comment followed by a
boolean option withan empty prompt, followed by a menu:*** FASTBOOT ***
[*]
Fastboot support --->This is not "nice-looking" at all...
Change the logic to make the boolean option a "menuconfig" rather than a
mere "config", so that all dependent options gets groupped under a menu.
The layout is now:*** FASTBOOT ***
[*] Fastboot support --->Signed-off-by: "Yann E. MORIN"
Cc: Simon Glass
Reviewed-by: Simon Glass
Tested-by: Simon Glass -
Some boards (like AM57x EVM) has USB OTG controller other than 0. So in
order to use correct controller number in compiled environment we should
define CONFIG_FASTBOOT_USB_DEV option.For example, when doing "fastboot reboot-bootloader" we want to enter
fastboot mode automatically. But to do so we need to provide controller
number to "fastboot" command. If this procedure is defined in some config
which is common to bunch of boards, and boards have different USB
controller numbers, we can't just hardcode "fastboot 0" in the
environment. We need to use configurable option, which this patch adds.Signed-off-by: Sam Protsenko
Reviewed-by: Tom Rini
02 Oct, 2016
1 commit
-
Move FASTBOOT_MBR_NAME and FASTBOOT_GPT_NAME into Kconfig.
Add dependency on the FASTBOOT_FLASH setting (also for FASTBOOT_MBR_NAME).
Remove the now redundant GPT_ENTRY_NAME.Signed-off-by: Petr Kulhavy
Reviewed-by: Tom Rini
Acked-by: Steve Rae
Reviewed-by: Simon Glass
[trini: Add FIXME about xxx_PARTITION needing to be in Kconfig]
Signed-off-by: Tom Rini
21 Aug, 2016
1 commit
-
implement Kconfig for the 'fastboot' feature set
Signed-off-by: Steve Rae