[U-Boot] [PATCH] binman: Use qemu-x86_defconfig in the example
The doc currently uses sandbox_defconfig as examples of enabling debug/verbose output of binman. However during a sandbox build it does not call binman at all. Change it to qemu-x86_defconfig.
Signed-off-by: Bin Meng bmeng.cn@gmail.com ---
tools/binman/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/binman/README b/tools/binman/README index 8e0f0a8..c96a564 100644 --- a/tools/binman/README +++ b/tools/binman/README @@ -931,13 +931,13 @@ old. To enable a full backtrace and other debugging features in binman, pass BINMAN_DEBUG=1 to your build:
- make sandbox_defconfig + make qemu-x86_defconfig make BINMAN_DEBUG=1
To enable verbose logging from binman, base BINMAN_VERBOSE to your build, which adds a -v<level> option to the call to binman:
- make sandbox_defconfig + make qemu-x86_defconfig make BINMAN_VERBOSE=5
On Wed, 2 Oct 2019 at 19:07, Bin Meng bmeng.cn@gmail.com wrote:
The doc currently uses sandbox_defconfig as examples of enabling debug/verbose output of binman. However during a sandbox build it does not call binman at all. Change it to qemu-x86_defconfig.
Signed-off-by: Bin Meng bmeng.cn@gmail.com
tools/binman/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Simon Glass sjg@chromium.org
On Fri, Oct 11, 2019 at 1:06 AM Simon Glass sjg@chromium.org wrote:
On Wed, 2 Oct 2019 at 19:07, Bin Meng bmeng.cn@gmail.com wrote:
The doc currently uses sandbox_defconfig as examples of enabling debug/verbose output of binman. However during a sandbox build it does not call binman at all. Change it to qemu-x86_defconfig.
Signed-off-by: Bin Meng bmeng.cn@gmail.com
tools/binman/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Simon Glass sjg@chromium.org
applied to u-boot-x86, thanks!
participants (2)
-
Bin Meng -
Simon Glass