mirror of
https://review.coreboot.org/flashrom.git
synced 2025-04-27 23:22:37 +02:00
5609fa752c
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>
------------------------------------------------------------------------------- flashrom README ------------------------------------------------------------------------------- flashrom is a utility for detecting, reading, writing, verifying and erasing flash chips. It is often used to flash BIOS/EFI/coreboot/firmware images in-system using a supported mainboard, but it also supports flashing of network cards (NICs), SATA controller cards, and other external devices which can program flash chips. It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash, or SPI. Please see the flashrom(8) manpage. Packaging --------- To package flashrom and remove dependencies on subversion, either use make export or make tarball make export will export all flashrom files from the subversion repository at revision BASE into a directory named $EXPORTDIR/flashrom-$VERSION-r$SVNREVISION and will additionally modify the Makefile in that directory to contain the svn revision of the exported tree. make tarball will simply tar up the result of make export and gzip compress it. The snapshot tarballs are the result of make tarball and require no further processing. Build Instructions ------------------ To build flashrom you need to install the following packages or ports: Linux et al: * pciutils / libpci * pciutils-devel / pciutils-dev / libpci-dev * zlib-devel / zlib1g-dev (only needed if libpci is static) On FreeBSD, you need the following ports: * devel/gmake * devel/libpci To compile on Linux, use: make To compile on FreeBSD, use: gmake To compile on Nexenta, use: make To compile on Solaris, use: gmake LDFLAGS="-L$pathtolibpci" CC="gcc -I$pathtopciheaders" CFLAGS=-O2 To compile on DragonFly BSD, use: ln -s /usr/pkg/include/pciutils pci gmake CFLAGS=-I. LDFLAGS="-L/usr/pkg/lib" To compile and run on Darwin/Mac OS X: Install DirectIO from coresystems GmbH. DirectIO is available at http://www.coresystems.de/en/directio. Installation ------------ In order to install flashrom and the manpage into /usr/local, type: make install For installation in a different directory use DESTDIR, e.g. like this: make DESTDIR=/usr install If you have insufficient permissions for the destination directory, use sudo by adding sudo in front of the commands above. Contact ------- The official flashrom website is: http://www.flashrom.org/ The IRC channel is #flashrom at irc.freenode.net The Mailing list addess is flashrom@flashrom.org