Name Date Size #Lines LOC

..--

docker/flashrom.org/H25-Apr-2025-7959

flashrom_tester/H25-Apr-2025-2,8921,949

git-hooks/H25-Apr-2025-380230

ich_descriptors_tool/H25-Apr-2025-315266

lint/H25-Apr-2025-7041

ubertest/H25-Apr-2025-2,0941,704

READMEH A D25-Apr-20251.2 KiB3426

flashrom.bash-completion.tmplH A D25-Apr-20251.7 KiB7875

flashrom_partial_write_test.shH A D25-Apr-20257 KiB290183

flashrom_udev.rulesH A D25-Apr-20253.8 KiB10078

list_yet_unsupported_chips.shH A D25-Apr-2025691 2420

shell.nixH A D25-Apr-2025192 1916

README

1Flashrom Testing
2
3Overall idea:
4- Break tests into small chunks
5- Have a single program that does generic setup and shutdown functions
6- Executes specified tests in a simple loop
7
8Dependencies:
9- uuencode
10- diff
11- A version of flashrom which is installed in $PATH. This is assumed to be a
12  "good" version of Flashrom and will be used to obtain a backup copy of the
13  ROM image at the beginning, and restore the image at the end.
14
15Important environment variables:
16FLASHROM: Path to the Flashrom binary to test
17FLASHROM_PARAM: Extra parameters to pass into flashrom, such as -p. Do *not*
18specify chip operations such as read/write/erase/verify here, as they are
19redundant with commands the script executes.
20
21Important global variables:
22BACKUP: The backup copy of ROM image which is read before executing any tests,
23        and restored unconditionally after execution of tests.
24
25Syntax:
26ENV_VARS="blah" ./do_tests.sh <test1> <test2>
27
28Example:
29FLASHROM="../flashrom" FLASHROM_PARAM="-p internal:bus=spi" ./do_tests foo.sh bar.sh
30
31Each unit test might have its own special requirements, such as extra
32environment variables, layout files, etc. Please read the comments at the top
33of each unit test to ensure there are no special dependencies.
34