| Age | Commit message (Collapse) | Author |
|---|
|
As already done for NOR chips, if device ESIZE and ENVSECTORS static
configurations are both zero, then autodetect them at runtime.
Cc: Joe Hershberger <[email protected]>
cc: Stefan Agner <[email protected]>
cc: Rasmus Villemoes <[email protected]>
Signed-off-by: Anthony Loiseau <[email protected]>
|
|
Commit aeb40f1166e0 ("tools: env: use /run to store lockfile") updated the
path to the lockfile but did not update the documentation to match.
Use the new path in the documentation.
Fixes: aeb40f1166 ("tools: env: use /run to store lockfile")
Signed-off-by: John Keeping <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
|
|
The target is not currently mentioned anywhere. Add it to the help so
people can find it.
Signed-off-by: Simon Glass <[email protected]>
|
|
This was broken by the recent environment refactoring. Specifically:
$ make environ
scripts/Makefile.build:59: tools/environ/Makefile: No such file or directory
make[1]: *** No rule to make target 'tools/environ/Makefile'. Stop.
make: *** [Makefile:1469: environ] Error 2
Fix this by updating the Makefile and adjusting the #include filesnames in
two C files.
Fixes: ec74f5f (Makefile: Rename 'env' target to 'environ')
Reported-by: Måns Rullgård <[email protected]>
Signed-off-by: Simon Glass <[email protected]>
|
|
fw_printenv is a program which mostly runs on the target Linux.
Before switching to Kbuild, we needed to set HOSTCC at the
command line like this:
make HOSTCC=<your CC cross-compiler> env
Going forward we can cross compile it by specifying CROSS_COMPILE:
make CROSS_COMPILE=<your cross-compiler prefix> env
This looks more natural.
Signed-off-by: Masahiro Yamada <[email protected]>
Tested-by: Gerhard Sittig <[email protected]>
|
|
Signed-off-by: Robert P. J. Day <[email protected]>
|
|
Add a mention of the lock file to the README for the fw_printenv tool.
Signed-off-by: Joe Hershberger <[email protected]>
Reported-by: Luka Perkov <[email protected]>
|
|
The 'trab' board configuration is broken, and there is nobody who is
interested and willing to fix it. Drop it.
This includes support for VFD displays which have always been used by
this board only.
Signed-off-by: Wolfgang Denk <[email protected]>
|
|
Signed-off-by: Luca Ceresoli <[email protected]>
|
|
Add support for environment in NAND with automatic NOR / NAND recognition,
including unaligned environment, bad-block skipping, redundant environment
copy.
Signed-off-by: Guennadi Liakhovetski <[email protected]>
|
|
This patch updates the fw_printenv/fw_setenv userspace tool to include
the correct MTD header in order to compile against current kernel
headers. Backward compatibility is preserved by introducing an option
MTD_VERSION which can be set to "old" for compilation using the old MTD
headers. Along with this a number of warnings are fixed.
Signed-off-by: Markus Klotzbuecher <[email protected]>
|
|
when watchdog is on
* Update baudrate in bd_info when it gets changed
* Add watchdog trigger points while waiting for serial port
(so far only 8xx -- needed on LWMON with 100ms watchdog)
* Improve command line tool to access the U-Boot's environment
(figuration of the utility, using a config file)
|
|
Add i2c commands to PM826 config
* extend I2C POST code: check for list on known addresses
|
