Skip to contentSkip to conversation

binman: Use qemu-x86_defconfig in the example

PATCH New Bin Meng 2 participants 3 messages Oct 3, 2019 – Oct 11, 2019

lore
Share & tools
lore

Bin Meng

author
#0 lore raw

PATCH 1/1 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.

---

 tools/binman/README | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
tools/binman/README +2 -2
index 8e0f0a8..c96a564 100644
@@ -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
 
 
Signature · 1 line
2.7.4
#1 lore raw

PATCH 1/1 binman: Use qemu-x86_defconfig in the example

Quoted 10 lines · Bin Meng

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.

---

 tools/binman/README | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
author
#2 lore raw

PATCH 1/1 binman: Use qemu-x86_defconfig in the example

Quoted 7 lines · Simon Glass
Quoted 5 lines · Bin Meng

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.

Quoted 7 lines
Quoted 5 lines

---

 tools/binman/README | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

applied to u-boot-x86, thanks!