u-boot.git/tools/env, branch v2017.11

tools: env: allow to print U-Boot version

2017-11-06T14:58:59+00:00

The fw_env utility family has a default environment compiled in
which ties it quite strongly to the U-Boot source/config it has
been built with. Allow to display the U-Boot version it has been
built with using the -v/--version argument.

Signed-off-by: Stefan Agner 
Reviewed-by: Lukasz Majewski

tools: env: Add embedded.c to .gitignore

2017-10-16T13:42:51+00:00

Signed-off-by: Bin Meng

env: Add 'envtools' target to 'make help'

2017-09-06T00:34:09+00:00

The target is not currently mentioned anywhere. Add it to the help so
people can find it.

Signed-off-by: Simon Glass

env: Fix operation of 'make environ'

2017-09-06T00:34:08+00:00

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 
Signed-off-by: Simon Glass

env: Fix out of tree building of tools-all

2017-09-05T19:59:47+00:00

With the move of environment code from common/ to env/ a number of
changes needed to be made to various make targets.  We missed updating
some of the files required for out of tree builds of the tools.  Correct
the 'environ' target to know that we need to work under tools/env/ still
(not tools/environ/) and then update the wrappers in env_attr.c and
env_flags.c to point to the new correct file.

Reported-by: Peter Robinson 
Tested-by: Peter Robinson 
Signed-off-by: Tom Rini

fix: fw_env: Prevent writing error message on special files, which don't support fsync

2017-09-03T19:30:31+00:00

According to fsync specification [1] some special files (e.g., a pipe, FIFO,
or socket) don't support synchronization and return either EROFS or EINVAL.

On the linux side the sys_fsync -> do_fsync() checks if the requested file
has f_op->fsync defined. If not it returns EINVAL [2].

This commit prevents writing error messages for files (devices), which
do not support fsync().

[1] - http://man7.org/linux/man-pages/man2/fsync.2.html
[2] - http://elixir.free-electrons.com/linux/v4.13-rc6/source/fs/sync.c#L183

Signed-off-by: Lukasz Majewski 
Acked-by: Michael Heimpold

env: Rename setenv() to env_set()

2017-08-16T12:22:18+00:00

We are now using an env_ prefix for environment functions. Rename setenv()
for consistency. Also add function comments in common.h.

Suggested-by: Wolfgang Denk 
Signed-off-by: Simon Glass

tools/fw_env: use fsync to ensure that data is physically stored

2017-07-22T19:36:16+00:00

Closing a file descriptor does not guarantee that the data has been
successfully saved to disk, as the kernel might defer the write.

Signed-off-by: Michael Heimpold

tools/env: avoid memory leak in fw_setenv

2017-04-18T14:29:22+00:00

If realloc fails we should release the old buffer.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Tom Rini 
Reviewed-by: Simon Glass

env: fix memory leak in fw_env routines

2017-04-12T17:28:29+00:00

fw_env_open allocates buffers to store the environment, but these
buffers are never freed. This becomes quite nasty using the fw_ tools as
library, because each access to the environment (even just reading a
variable) generates a memory leak equal to the size of the environment.

Fix this renaming fw_env_close() as fw_env_flush(), because the function
really flushes the environment from RAM to storage, and add a
fw_env_close function to free the allocated resources.

Signed-off-by: Stefano Babic