- 04 9月, 2017 7 次提交
-
-
由 Thomas Petazzoni 提交于
This commit removes definitions of CONFIG_SYS_BARGSIZE defined to be equal to CONFIG_SYS_CBSIZE in numerous configuration files. We remove such definitions in two situations: - CONFIG_SYS_CBSIZE is otherwise not defined in the board configuration file, which means the default value of CONFIG_SYS_CBSIZE == 256 applies. In this case, the default value of CONFIG_SYS_BARGSIZE == 512 (common/image.c) is suitable, as it is larger. - CONFIG_SYS_CBSIZE is defined in the board configuration file, but to a value equal or less than 512. In this case, the default value of CONFIG_SYS_BARGSIZE == 512 (common.image.c) is suitable, as it is equal or larger. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Thomas Petazzoni 提交于
CONFIG_SYS_BARGSIZE is already defined to 512 in common/image.c when not defined. Therefore, there is no point in having board configuration files define it to 512. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Thomas Petazzoni 提交于
Now that include/config_fallbacks.h define a sane fallback for CONFIG_SYS_MAXARGS, we can drop the definition of this constant in all configurations that were using the default value. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Thomas Petazzoni 提交于
CONFIG_SYS_MAXARGS contains the maximum number of arguments accepted by U-Boot commands. Since the vast majority of the platforms define it to 16, it makes sense to have a default definition to 16, which will allow to remove this definition from a significant number of platforms. It will allow to remove the default definition from 216 platform .h files, leaving only 56 platforms with non-default values (15, 24, 32, 48, 64, 96, 128 or 256). Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Thomas Petazzoni 提交于
Now that the fallback value of CONFIG_SYS_PBSIZE in include/config_fallbacks.h has been adjusted, remove its definition from a large number of board configuration files. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Thomas Petazzoni 提交于
Most of the platforms are using CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16 as their value for CONFIG_SYS_PBSIZE, so let's adopt this for the fallback value of CONFIG_SYS_PBSIZE. This will allow us to drop an explicit definition of CONFIG_SYS_PBSIZE from a large number of platforms. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Thomas Petazzoni 提交于
Now that include/config_fallbacks.h define a sane fallback for CONFIG_SYS_CBSIZE, we can drop the definition of this constant in all configurations that were using the default value. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com> [trini: Drop <config.h> from stih410-b2260.h] Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 03 9月, 2017 7 次提交
-
-
由 Thomas Petazzoni 提交于
CONFIG_SYS_CBSIZE contains the buffer size for input for the console. The vast majority of platforms define them to some reasonable value (256, 512 or 1024 bytes), and it is quite annoying to repeat this definition for all platforms while it isn't really HW-related. Therefore, let's provide a sane fallback value in config_fallbacks.h, so that platforms can rely on it instead of having to explicitly define it. We use 1024 when KGDB is enabled, and 256 otherwise, which is what the majority of the platforms are doing. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Maxime Ripard 提交于
The current code checks that no partitions overlap with the GPT partition table using the offset of the first LBA usable for that partition. This works fine, unless you have a partition entry that is further away than it usually is and you want to create partitions in the gap between the GPT header and the GPT partition entries, for example to reflash a bootloader that needs to be set there. Rework the test to something a bit smarter that checks whether a partition would overlap with either the GPT header or the partition entries, no matter where it is on the disk. Partitions that do not have a start LBA specified will still start at the first LBA usable set in the GPT header, to avoid weird behaviours. Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Maxime Ripard 提交于
The gpt_fill_pte will need to access the device block size. Let's pass the device descriptor as an argument. Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Maxime Ripard 提交于
The start variable is only used inside a loop, and is never affected inside it, so it's a purely local variable. In the same way the partition size is accessed several times, so we can store it in a variable. Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Maxime Ripard 提交于
Both the config option and the DT options specify the offset to set the GPT at in bytes, yet the code treats those values as block numbers. Fix that. Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
-
由 Adam Ford 提交于
Add the following options to drivers/misc/Kconfig: SYS_I2C_EEPROM_ADDR SYS_I2C_EEPROM_BUS SYS_EEPROM_SIZE SYS_EEPROM_PAGE_WRITE_BITS SYS_EEPROM_PAGE_WRITE_DELAY_MS SYS_I2C_EEPROM_ADDR_LEN SYS_I2C_EEPROM_ADDR_OVERFLOW This does not migrate any boards, but provides a foundations for those who want/need these options Signed-off-by: NAdam Ford <aford173@gmail.com> [trini: Migrate uniphier] Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 02 9月, 2017 14 次提交
-
-
由 Stefan Roese 提交于
Without ethernet cable plugged, "ip=dhcp" leads to a complete hangup in Linux booting and the system does not boot into userland at all. Since its not required to have an active network connection on these board, lets remove this statement from the default environment. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com>
-
由 Bin Meng 提交于
It was noticed a few times, that the reboot from Linux (reboot command) is different from the reboot (reset command) under U-Boot. The U-Boot version does seem to reset the board more deeply (PCI cards etc) than the Linux reboot. This is actually caused by missing full reset bit in the reset register value in the ACPI FADT table. Reported-by: NStefan Roese <sr@denx.de> Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Tested-by: NStefan Roese <sr@denx.de>
-
由 Bin Meng 提交于
The atomic preop register can only be written when SPI settings are not locked, otherwise it's read-only. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NStefan Roese <sr@denx.de>
-
由 Bin Meng 提交于
In ich_spi_xfer() when the driver presets control fields, control variable gets assigned twice. Apparently only the last assignment takes effect. Remove the other one. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NStefan Roese <sr@denx.de>
-
由 Adam Ford 提交于
Manually enable SYS_NAND_U_BOOT_LOCATIONS. Set CONFIG_SYS_NAND_U_BOOT_OFFS=0x80000 and remove it from header Signed-off-by: NAdam Ford <aford173@gmail.com>
-
由 Adam Ford 提交于
This converts the following to Kconfig: CONFIG_BCH Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Adam Ford 提交于
This converts the following to Kconfig: CONFIG_SPL_OMAP3_ID_NAND Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Ford 提交于
This converts the following to Kconfig: CONFIG_SYS_I2C_BUS_MAX Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NHeiko Schocher <hs@denx.de> [trini: Fix AM43XX drop AM44XX] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Adam Ford 提交于
For consistency with other platforms and in preparation of Kconfig migration, let's change Several TI platforms that use I2C_BUS_MAX to CONFIG_SYS_I2C_BUS_MAX Signed-off-by: NAdam Ford <aford173@gmail.com>
-
由 Tom Rini 提交于
- 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 README Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
This syncs all of the currently Kconfig'd symbols out of the headers and into the defconfig files. This has two exceptions, first am335x_evm needs to be converted to DM in SPL and then it can stop undef'ing CONFIG_DM_USB. Leaving this as-is results in a build failure, and without work, run time failure. The other case is am43xx_evm.h and in turn am43xx_evm_usbhost_boot. The problem here is that we need DWC3 USB host mode in SPL, but still desire to have gadget mode in U-Boot proper. Signed-off-by: NTom Rini <trini@konsulko.com>
-
git://git.denx.de/u-boot-video由 Tom Rini 提交于
This reverts commit 1d201704, reversing changes made to 6aee2ab6. The mxc_ipuv3_fb.c changes introduce build failures on some targets. Signed-off-by: NTom Rini <trini@konsulko.com>
-
-
-
- 01 9月, 2017 6 次提交
-
-
由 Dave Prue 提交于
SUNXI_GMAC was still used to configure the code where as the same has been renamed and moved to Kconfig in below commit "sunxi: Move SUNXI_GMAC to Kconfig" (sha1: 4d43d065) Signed-off-by: NDave Prue <dave@prue.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NJagan Teki <jagan@openedev.com> Reviewed-by: NMark Kettenis <kettenis@openbsd.org> Tested-by: NMark Kettenis <kettenis@openbsd.org> [Tweek commit message, config_whitelist.txt, build-whitelist.sh] Signed-off-by: NJagan Teki <jagan@openedev.com>
-
git://git.denx.de/u-boot-imx由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com> Conflicts: configs/imx6qdl_icore_mmc_defconfig configs/imx6qdl_icore_rqs_defconfig
-
-
git://git.denx.de/u-boot-uniphier由 Tom Rini 提交于
- add {ofnode,dev}_read_resource_byname - provide DT probe hook to Denali NAND driver - update clk/reset driver - update DT - misc cleanups
-
-
由 Chen-Yu Tsai 提交于
When enabling the new mmc timing mode, we inadvertently clear all the remaining bits in the new timing mode register. The bits cleared include a default phase delay on the output clock. The BSP kernel states that the default values are supposed to be used. Clearing them results in decreased performance or transfer errors on some boards. Fixes: de9b1771 ("mmc: sunxi: Support new mode") Signed-off-by: NChen-Yu Tsai <wens@csie.org> Acked-by: NMaxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
- 30 8月, 2017 6 次提交
-
-
由 Jagan Teki 提交于
Add Falcon mode support in Engicam i.CoreM6 board. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Jagan Teki 提交于
Memory dt node update introduced by spl_fixup_fdt() in below commit was making DDR configuration in-appropriate to boot falcon mode. Hence added dram_init_banksize for explicit assignment of proper base and size of DDR. "boot: fdt: Perform arch_fixup_fdt() on the given device tree for falcon boot" (sha1: 6e7585bb) Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Stefan Agner 提交于
The NXP i.MX 6UL and 6ULL do not support SATA and have no SATA boot mode, hence remove it from the boot device detecion. This fixes a build error introduced with 3bd1642d ("imx: fix USB boot mode detection for i.MX 6UL and 6ULL") Fixes: 3bd1642d ("imx: fix USB boot mode detection for i.MX 6UL and 6ULL") Signed-off-by: NStefan Agner <stefan.agner@toradex.com> Reviewed-by: NStefano Babic <sbabic@denx.de> Reviewed-by: NJagan Teki <jagan@openedev.com>
-
由 Chris Packham 提交于
U-boots spi-nor support is currently considered a work in progress. For now to avoid issues it is necessary to add a "spi-flash" compatible string. Eventually the "jedec,spi-nor" will be sufficient when the core U-boot code is updated to support it. Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NJagan Teki <jagan@openedev.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Masahiro Yamada 提交于
Now the entry to the NAND driver init can be is controlled by DT; it should not hurt to compile the driver all the time. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Masahiro Yamada 提交于
The system bus is not enabled by default for NAND, eMMC boot etc. of PXs3. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-