u-boot.git/board/keymile/scripts, branch master

Kconfig: Move CONFIG_BOOTCOUNT_ALTBOOTCMD to Kconfig

2025-02-14T16:19:24+00:00

Add CONFIG_BOOTCOUNT_ALTBOOTCMD so the developer is able to add
custom altbootcmd via Kconfig when they enable BOOTCOUNT. With this now
in Kconfig, we need to move it from environment files / config.h files
and in to the defconfig file.

This was done by generating u-boot-initial-env for all platforms before
the Kconfig change, to extract altbootcmd values and then again after to
compare the result.

[trini: Perform migration to defconfigs, reword commit message]
Signed-off-by: Tom Rini

board/km: remove kirkwood boards

2022-10-06T08:13:38+00:00

These boards are out of maintenance and can be removed.

Signed-off-by: Holger Brunck 
Reviewed-by: Stefan Roese

km/scripts: fix saveenv command syntax

2021-06-17T06:16:11+00:00

This is most probably a typo, and in older u-uboot versions is same as
'saveenv', in the newer uboot versions there is a separate 'save' command
that is different from 'saveenv'.

Signed-off-by: Aleksandar Gerasimovski 
Reviewed-by: Priyanka Jain

km: replace hardcoded address for imported environment

2020-11-19T14:45:49+00:00

Instead of using an hard coded address, make use of an
already defined address for importing the environment
for ramfs and nfs boot. This allows boards having different
mapping to use the same code.

CC: Heiko Schocher 
CC: Tom Rini 
Signed-off-by: Matteo Ghidoni 
Signed-off-by: Holger Brunck

km/scripts: product env and auto-reset for ramfs

2020-01-23T12:29:58+00:00

This patch adds the possibility in both debug and ramfs modes to
optionally load an env file from /tftpboot/$tftppath (this is ignored if
not present, so the change is backward compatible). This gives the debug
and ramfs scripts the possibility to set uboot environment variables
that were previously asked the users to manually set (nfs path in debug
and rootfs size in ramfs).

Signed-off-by: Holger Brunck 
CC: Tom Rini

km/scripts: fix run ramfs and COGE5 tftppath problem

2020-01-23T12:29:58+00:00

The tftppath was not set in case of run ramfs. It worked only by chance
if was already set before.

Also check the boardname before setting the tftppath for COGE5.

Signed-off-by: Holger Brunck 
CC: Tom Rini

km/scripts: search for kernel/DTBs at serverip:/PRODUCTNAME via TFTP in develop mode

2015-11-18T20:28:51+00:00

Search for the kernel and DTBs in a folder named PRODUCTNAME (found in the IVM)
at the TFTP server instead of the u-boot boardname.

Signed-off-by: Tobias Müller 
Signed-off-by: Valentin Longchamp 
Reviewed-by: Heiko Schocher

km/scripts: load fdt_bid_kwkey.dtb when working with tftp

2015-11-18T20:28:50+00:00

When loading the dtb file via tftp we should load the one which matches
boardId and hwKey and not a common one for the boardname. We have boards
were different hwKeys are used and then we may load an incorrect dtb
file. If no fdt_bid_kwkey.dtb file is not a fallback to boardname.dtb is used.

Signed-off-by: Holger Brunck 
Signed-off-by: Tobias Müller 
Signed-off-by: Valentin Longchamp 
Reviewed-by: Heiko Schocher

arm/km: define fdt_high env variable and allow backwards compatibility

2014-02-13T15:18:13+00:00

Add set_fdthigh subcommand to "subbootcmds" (release) so to set "fdt_high"
This is necessary on Kirkwood so that the FDT does not get relocated
above the memory limit that the kernel cannot access
(that is the memory part reserved for the switch).
This was tested on NUSA1, where it is necessary, and on ETER1, where it
doesn't seem to hurt.

We want the scripts to also work with older versions of u-boot, where:
a) set_fdthigh is not defined (will be default env for newer u-boots)
b) the fdt will not be available

For this reason, we use "set_fdthigh" to tell whether we are running
a newer (FDT-aware) u-boot or not.
So if "set_fdthigh" runs successfully or arch != arm we try loading
the fdt; otherwise we proceed normally.

Notice how, contrary to release mode, set_fdthigh will _not_ be part of
subbootcmds for develop and ramfs, but will be executed as part of
"tftpfdt".

Since this is only needed for kirkwood cards, and it prevents the kernel
from booting on QorIQ (though it seemed to work on ETER1), we change
its definition in the default env for powerpc so that the value is only
set on ARM.

Signed-off-by: Valentin Longchamp 
Signed-off-by: Gerlando Falauto 
Signed-off-by: Holger Brunck 
Acked-by: Valentin Longchamp

arm/km: enable FDT for km_kirwkood

2014-02-13T15:17:54+00:00

This consists of:
a) Defining the addresses, enabling fdtsupport [arm]
b) Defining "cramfsloadfdt"  [arm,powerpc => common]
c) Adding the FDT address to bootm [arm,powerpc => common]
d) Defining "tftpfdt" in ramfs-,develop- [arm,powerpc >= common]

This should work with 3.10 kernels, whether loaded through TFTP
(with rootfs either through NFS or TFTP-ramfs) or from the NAND.

The machid was left unchanged, this should keep compatibility with both
older and newer kernels.

Signed-off-by: Valentin Longchamp 
Signed-off-by: Gerlando Falauto 
Signed-off-by: Holger Brunck 
Acked-by: Valentin Longchamp