While looking into issue #653814 I noticed that crossystem output shows an error when reading wpsw_cur. I'm currently a 8350.74.0 (R52) test image. I don't think this is blocking, though it might confuse the updater so we should probably fix it if feasible (Pri=2 for now).

The jumper itself is operational as I can successfully alter firmware ROM write-protect settings by shorting/opening it.

Crossystem appears to try to get the value by reading GPIOs in /sys/class/gpio. However that directory doesn't have anything other than "export" and "unexport" in it:
localhost gpio # ls -l /sys/class/gpio/
total 0
--w------- 1 root root 4096 Oct 14 17:01 export
--w------- 1 root root 4096 Oct 14 17:01 unexport

It's been a while since I've looked at this, but I thought the kernel was supposed to recognize Panther Point as the chipset and populate these automatically.

If I follow the testing steps from https://chromium-review.googlesource.com/#/c/28183/ I see an error:
localhost ~ # echo $(( 160 + 70 )) > /sys/class/gpio/export
-bash: echo: write error: No such device

dmesg shows an error when I do this:
[ 3149.537166] gpio_request: gpio-230 (sysfs) status -517
[ 3149.537175] export_store: status -19

Kernel is 3.8.11 (according to uname -r).