Searched hist:fd4e3280e50983aa4d646f2c8fc93b38cc1dddf9 (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/tools/env/ |
| H A D | fw_env.h | fd4e3280e50983aa4d646f2c8fc93b38cc1dddf9 Sat Jul 16 15:06:13 UTC 2016 Andreas Fenkart <andreas.fenkart@digitalstrom.com> tools/env: kernel-doc for fw_printenv, fw_getenv and fw_parse_script
there are two groups of functions:
- application ready tools: fw_setenv/fw_getenv/fw_parse_script
these are used, when creating a single binary containing multiple
tools (busybox like)
- file access like: open/read/write/close
above functions are implemented on top of these. applications
can use those to modify several variables without creating a
temporary batch script file
tested with "./scripts/kernel-doc -html -v tools/env/fw_env.h"
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Andreas Fenkart <andreas.fenkart@digitalstrom.com>
|
| H A D | fw_env.c | fd4e3280e50983aa4d646f2c8fc93b38cc1dddf9 Sat Jul 16 15:06:13 UTC 2016 Andreas Fenkart <andreas.fenkart@digitalstrom.com> tools/env: kernel-doc for fw_printenv, fw_getenv and fw_parse_script
there are two groups of functions:
- application ready tools: fw_setenv/fw_getenv/fw_parse_script
these are used, when creating a single binary containing multiple
tools (busybox like)
- file access like: open/read/write/close
above functions are implemented on top of these. applications
can use those to modify several variables without creating a
temporary batch script file
tested with "./scripts/kernel-doc -html -v tools/env/fw_env.h"
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Andreas Fenkart <andreas.fenkart@digitalstrom.com>
|