summaryrefslogtreecommitdiffstats
path: root/cli_classic.c
diff options
context:
space:
mode:
authorCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2010-01-07 03:32:17 +0000
committerCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2010-01-07 03:32:17 +0000
commit5609fa752ca1c36d00d915e94d481a9a457c85cf (patch)
treeff145bc4ed987c3c81870ddb6e7ce6a929ca9b47 /cli_classic.c
parenta84835a7eadadb715a61d993da6766bdf1b37c5e (diff)
downloadast2050-flashrom-5609fa752ca1c36d00d915e94d481a9a457c85cf.zip
ast2050-flashrom-5609fa752ca1c36d00d915e94d481a9a457c85cf.tar.gz
Allow one to disable programmer debug messages at compile time
Programmer debug messages during programmer init/shutdown are useful because they print hardware settings and desired configuration. They help in getting a quick overview of hardware and software state on startup and shutdown. Programmer debug messages during flash chip access are mostly a distraction in logs and should only be enabled if someone is having problems which are suspected to stem from a programmer hardware or programmer software bug. Disable those messages by default, they can be reenabled by #define COMM_DEBUG in the affected programmer file. An added benefit is a tremendous size reduction in verbose probe/read/write/erase logs because only flash chip driver messages remain. In some cases, logs will shrink from 65 MB to 10 kB or less. The right(tm) fix would be two different debug levels (DEBUG and SPEW) and the ability to differentiate between programmer debug messages and flash chip debug messages. Until the design for the message printing infrastructure is finished, this is the best stop-gap measure we can get. Corresponding to flashrom svn r834. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: Sean Nelson <audioahcked@gmail.com>
Diffstat (limited to 'cli_classic.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud