a73b93157f
It encourages users from writing to the FSF without giving an address. Linux also prefers to drop that and their checkpatch.pl (that we imported) looks out for that. This is the result of util/scripts/no-fsf-addresses.sh with no further editing. Change-Id: Ie96faea295fe001911d77dbc51e9a6789558fbd6 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: http://review.coreboot.org/11888 Tested-by: build bot (Jenkins) Reviewed-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> Reviewed-by: Ronald G. Minnich <rminnich@gmail.com> |
||
|---|---|---|
| .. | ||
| COPYING | ||
| Kconfig | ||
| Makefile | ||
| README | ||
| bootlog_module.c | ||
| cbfs_module.c | ||
| coreboot_module.c | ||
| coreinfo.c | ||
| coreinfo.h | ||
| cpuid.S | ||
| cpuinfo_module.c | ||
| lar_module.c | ||
| multiboot_module.c | ||
| nvram_module.c | ||
| pci_module.c | ||
| ramdump_module.c | ||
README
This is a silly little program that demonstrates how cool libpayload is and also serves a purpose. It is fun and educational! Requirements ------------ You should use the coreboot reference cross compiler. If you insist on using your system compiler, some Linux distributions might require you to install a package called gcc-multilib if you are on a 64bit system. Build ----- You need libpayload to build coreinfo. So, first, you need follow the README of libpayload to build it but install libpayload into its own directory by doing this: $ make DESTDIR=/path/to/libpayload/install install Then you can build coreinfo now: $ cd coreinfo $ make menuconfig $ make