Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
Signed-off-by: Wei Liang Lim <weiliang.lim@starfivetech.com>
|
|
|
|
|
|
Reassign address for SPL STACK to avoid global data being wiped off during mem_malloc_init
Remove unused config CONFIG_SPL_LOAD_FIT_ADDRESS
Signed-off-by: woonjiet.chong <woonjiet.chong@starfivetech.com>
|
|
|
|
|
|
Signed-off-by: Tom Rini <trini@konsulko.com>
|
|
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini <trini@konsulko.com>
|
|
Set my current personal email in the MAINTAINERS file.
Signed-off-by: Bhupesh Sharma <bhupesh.linux@gmail.com>
|
|
https://source.denx.de/u-boot/custodians/u-boot-at91
Second set of u-boot-atmel fixes for the 2023.10 cycle:
Two small fixes , one for an array not initialized and the second one
fixes an error case when a DT property is missing for the atmel NAND
driver.
|
|
Arrays are not cleared entirely because ARRAY_SIZE
returns the number of elements in an array, not the size
in bytes.
This commit fixes the calls to memset by providing the
array size in bytes instead of the number of elements
in the array.
Signed-off-by: Francois Berder <fberder@outlook.fr>
|
|
https://source.denx.de/u-boot/custodians/u-boot-efi
Pull request doc-2023-10-rc5-3
Documentation:
* describe that partition numbers are hexadecimal in load command
* remove obsolete half sentence in tools/binman/binman.rst
|
|
- Fixes for two board builds and a script fix for many TI platforms
|
|
This is the difference between version 1 and 2 of Massimo's patch:
binman: doc: fix reference tag placement for Logging section
v2: https://lore.kernel.org/u-boot/20230913161633.999542-1-massimo.pegorer+oss@gmail.com/
v1: https://lore.kernel.org/u-boot/20230909135235.21242-1-massimo.pegorer+oss@gmail.com/
Fixes: 0f40e23fd22 ("binman: add documentation for binman sign option")
Signed-off-by: Massimo Pegorer <massimo.pegorer+oss@gmail.com>
Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Acked-by: Massimo Pegorer <massimo.pegorer+oss@gmail.com>
|
|
`part` option is in hexadecimal, so information is missing in usage
documentation.
Callgraph for `part` parsing is :
do_load -> fs_set_blk_dev -> part_get_info_by_dev_and_name_or_num ->
blk_get_device_part_str -> hextoul (This is why it is hexadecimal)
Signed-off-by: Mickaël Tansorier <mickael.tansorier@smile.fr>
Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
|
We only have serial as console option, and leaving this on turns on
SYS_CONSOLE_IS_IN_ENV which is also not true for these devices, leaving
an ugly
In: No input devices available!
Out: No output devices available!
Err: No error devices available!
behind.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
|
|
CONFIG_SYS_BOOT_LOCKED means that a restricted boot environment will
be used. In this case, hab_auth_img_or_fail should be called to prevent
U-Boot to continue running when the fitImage authentication fails.
Fix the logic accordingly.
Additionally, select CONFIG_SYS_BOOT_LOCKED by default.
Signed-off-by: Eduard Strehlau <eduard@lionizers.com>
Signed-off-by: Fabio Estevam <festevam@denx.de>
|
|
After the refactor with conf- nodes in fitImage, overlaystring wasn't
didn't handle the new conf- nodes in FIT Booting. Fix get_overlaystring
to handle conf- nodes.
Fixes: 837833a724b7 ("environment: ti: Add get_fit_config command to get FIT config string")
Reported-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Reviewed-by: Andrew Davis <afd@ti.com>
|
|
Adapt behaviour to Linux kernel driver.
The return value of gpio_request_by_name_nodev() was not checked before,
and thus in case 'rb-gpios' was missing in DT, rb.type was set to
ATMEL_NAND_GPIO_RB nevertheless, leading to output like this for
example (on sam9x60-curiosity with the line removed from dts):
NAND: Could not find valid ONFI parameter page; aborting
device found, Manufacturer ID: 0xc2, Chip ID: 0xdc
Macronix NAND 512MiB 3,3V 8-bit
512 MiB, SLC, erase size: 256 KiB, page size: 4096, OOB size: 64
atmel-nand-controller nand-controller: NAND scan failed: -22
Failed to probe nand driver (err = -22)
Failed to initialize NAND controller. (error -22)
0 MiB
Note: not having that gpio assigned in dts is possible, the driver does
not override nand_chip->dev_ready() then and a generic solution is used.
Fixes: 6a8dfd57220d ("nand: atmel: Add DM based NAND driver")
Signed-off-by: Alexander Dahl <ada@thorsis.com>
Reviewed-by: Eugen Hristev <eugen.hristev@collabora.com>
Acked-by: Michael Trimarchi <michael@amarulasolutions.com>
|
|
+ Fix VisionFive2 booting issue by providing the correct FDT.
|
|
Multiple revisions of the StarFive VisionFive 2 board exist. They can be
identified by reading their EEPROM.
Linux uses two differently named device-tree files. To load the correct
device-tree we need to set $fdtfile to the device-tree file name that
matches the board revision.
Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
Tested-by: Milan P. Stanić <mps@arvanta.net>
|
|
https://source.denx.de/u-boot/custodians/u-boot-imx
Fixes for 2023.10
-----------------
CI: https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/17831
|
|
https://source.denx.de/u-boot/custodians/u-boot-dm
trace: correct format of flyrecord
minor bug fixes
|
|
Set CONFIG_SYS_LOAD_ADDR=0x88000000 and use this address for
loading fitImage.
Also pass the standard CONFIG_BOOTFILE option to indicate
the fitImage file.
Signed-off-by: Eduard Strehlau <eduard@lionizers.com>
Signed-off-by: Fabio Estevam <festevam@denx.de>
|
|
Trying to boot a fitImage after a successful hab_auth_img operation
causes the following error:
## Loading kernel from FIT Image at 88000000 ...
Using 'conf-imx7d-smegw01.dtb' configuration
Trying 'kernel-1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x8800010c
Data Size: 9901752 Bytes = 9.4 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80800000
Entry Point: 0x80800000
Hash algo: sha256
Hash value: 28f8779bbf010780f16dd3d84ecb9b604c44c5c2cf7acd098c264a2d3f68e969
Verifying Hash Integrity ... sha256Error in SEC deq
CAAM was not setup properly or it is faulty error!
The reason for this error is that the BootROM uses the CAAM Job Ring 0,
so disable its node in U-Boot to avoid the resource conflict.
imx8m dtsi files also have the Job Ring 0 disable since the following
kernel commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch?h=v6.5&id=dc9c1ceb555ff661e6fc1081434600771f29657c
For a temporary solution, disable the Job Ring 0 in imx7s-u-boot.dtsi.
Reported-by: Eduard Strehlau <eduard@lionizers.com>
Signed-off-by: Fabio Estevam <festevam@denx.de>
|
|
The ivt_offset parameter is optional for both hab_auth_img_or_fail
and hab_auth_img commands.
Document it in their usage texts to make it clearer.
Signed-off-by: Fabio Estevam <festevam@denx.de>
|