summaryrefslogtreecommitdiffstats
path: root/external/gard/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Makefile: Paper over gard and pflash coverage issuesAndrew Jeffery2019-02-211-0/+4
| | | | | | | | | | | | | | | | | | | | | | | `make coverage-report` gave the following error: (cd external/pflash; lcov -q -c -d . -o pflash.info --rc lcov_branch_coverage=1; sed -i -e 's%external/pflash/libflash%libflash%; s%external/pflash/ccan%ccan%' pflash.info) (cd external/gard; lcov -q -c -d . -o gard.info --rc lcov_branch_coverage=1; sed -i -e 's%external/gard/libflash%libflash%; s%external/gard/ccan%ccan%' gard.info) geninfo: WARNING: no .gcda files found in . - skipping! geninfo: WARNING: no .gcda files found in . - skipping! lcov -q -c -d . -d ccan/check_type/test/ -d ccan/str/test/ -d ccan/str/test/ -d ccan/list/test/ -d ccan/list/test/ -d ccan/list/test/ -d ccan/list/test/ -d ccan/list/test/ -d ccan/build_assert/test/ -d ccan/short_types/test/ -d ccan/short_types/test/ -d ccan/array_size/test/ -d ccan/container_of/test/ -d ccan/endian/test/ -d libc/test/ -d libc/test/ -d libc/test/ -d libc/test/ -o skiboot.info --rc lcov_branch_coverage=1 lcov -q -r skiboot.info 'external/pflash/*' -o skiboot.info lcov -q -r skiboot.info 'external/gard/*' -o skiboot.info lcov -q -a skiboot.info -a external/pflash/pflash.info -o skiboot.info lcov: ERROR: no valid records found in tracefile external/pflash/pflash.info make: *** [/home/andrew/src/open-power/skiboot/Makefile.main:315: skiboot.info] Error 255 And similar again for the gard tool. We should really untangle the build strategy for tools in external/, but in the mean time paper over the problem of generating the lcov output at the top level by ensuring we have a means to generate the necessary gcda files for lcov to consume. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
* external/gard: Fix make dist targetCyril Bur2017-02-231-10/+9
| | | | | | | | | | | | | | | | | Several problems: Firstly, it could never have worked, it was using the wrong variable. Secondly, if it was using GARD_VERSION it produced a broken tarball that still looked into the skiboot source for files despite them having been copied into the tarball. Lastly (and not really a make dist issue) the current way of symlinking make_version.sh was racey. Get around the issue by refering to it in its actual location (if we know it will be there) or by looking at .version if building from tarball. Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* Make links target reusableDinar Valeev2016-03-311-17/+2
| | | | | | | | | Move symlinking target to external/common/rules.mk, so the rule could be reused by gard and opal-prd. Signed-off-by: Dinar Valeev <dvaleev@suse.com> Reviewed-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: Add make distCyril Bur2015-11-161-0/+11
| | | | | Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: Add version informationCyril Bur2015-11-161-5/+15
| | | | | | | | Method for recording version is identical to pflash. Uses the current skiboot version and any current repository state. Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: Update gard building to use external/common filesCyril Bur2015-11-161-26/+18
| | | | | | | | This will enable building the gard tool on any arch which may prove useful for debug parsing of gard records in a binary file format Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard/tests: Add tests for the gard toolCyril Bur2015-10-141-1/+5
| | | | | | | Simple tests for the gard tool that can be expanded on over time Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: Update gard tool to new blocklevel interfaceCyril Bur2015-07-171-1/+1
| | | | | Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: change gard manual page filenameCédric Le Goater2015-07-101-1/+1
| | | | | | | | | | | | | This patch fixes : commit 6c458a036949 ("external/gard: Install gard manual page") which did not take into account the changes from : commit 2e2fb4dfff5c ("Renaming to opal-gard and minus escaping") Signed-off-by: Cédric Le Goater <clg@fr.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: Install gard manual pageCédric Le Goater2015-06-231-0/+3
| | | | | Signed-off-by: Cédric Le Goater <clg@fr.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* Honor compilation flags passed from the environmentFrederic Bonnard2015-06-231-3/+3
| | | | | | | | Adding the environment variables CFLAGS, CPPFLAGS and LDFLAGS to the one in the Makefiles. Debian/Ubuntu use this mechanism to do hardened builds. Signed-off-by: Frederic Bonnard <frediz@linux.vnet.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external/gard: add Makefile targets to make debian packagesCyril Bur2015-06-091-0/+8
| | | | | | | | | | The Makefile is missing a install target which will be needed to package and distribute into ubuntu. Added a simple install target. Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
* external: create a GUARD partition parsing utilityCyril Bur2015-04-011-0/+26
This utility is designed to run completely in userland linux and make use of OPAL APIs (exposed to userland via the linux MTD abstraction) to read, parse, display and optionally clear firmware GUARD partition information. The main intended use case is to have the tool run on the OpenPOWER machine and automatically detect the flash device containing the gard data and display information about the running system. The tool can also read a flash imagine contained in a specified file. The tool can also be used to parse just guard data not contained in a flash image but rather dumped to a file. The tool understands ECC and does its best to detect this automatically. There are three commands: - list: lists all the records - show: show more information about a specific record - clear: clear/erase a specific record or the entire flash. The tool makes some assumptions: - gard data is terminated by an entry containing all FF bytes. In the case of the tool detecting ECC it will always read with ECC correction so the final all FF record will still need to contain ECC bytes. - The GUARD partition will not have gaps, the clear code does shuffle entires up and set the last one to all FF bytes. Note: This tool has been named 'gard' because this is the traditional name for hardware that has been detected as faulty and has been 'gard'ed. It turns out that in the flash the partition is named 'GUARD'. Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com> Reviewed-by: Daniel Axtens <dja@axtens.net> [stewart@linux.vnet.ibm.com: add correct (C) header to gard.c] Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
OpenPOWER on IntegriCloud