| commit | 16cc9c9599262828407146129485590d90600ad7 | |
| author | Aaron Durbin <adurbin@chromium.org> | |
| Mon, 9 Dec 2013 23:03:34 +0000 (9 15:03 -0800) | ||
| committer | Kyösti Mälkki <kyosti.malkki@gmail.com> | |
| Fri, 9 May 2014 03:41:40 +0000 (9 05:41 +0200) | ||
| tree | 80cb8162ab47119e94f7887ae5687722f423685a | treesnapshot (tar.gz zip) |
| parent | 7538937d6e7c474dc7c17a1bc3c3591f0e6ef311 | commitdiff |
baytrail: fix nvs offsets
The VDAT data was off by 2 bytes when reading it from the
kernel. The reason is that the header did not line up
correctly with actual ACPI code.
BUG=chrome-os-partner:24440
BRANCH=None
TEST=crossystem devsw_cur now returns either 0 or 1 depending
on state.
Change-Id: Ie78599f29cd5daf7da98db5e37fa276d24339f6a
Signed-off-by: Aaron durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/179372
Reviewed-on: http://review.coreboot.org/4996
Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com>
Tested-by: build bot (Jenkins)
The VDAT data was off by 2 bytes when reading it from the
kernel. The reason is that the header did not line up
correctly with actual ACPI code.
BUG=chrome-os-partner:24440
BRANCH=None
TEST=crossystem devsw_cur now returns either 0 or 1 depending
on state.
Change-Id: Ie78599f29cd5daf7da98db5e37fa276d24339f6a
Signed-off-by: Aaron durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/179372
Reviewed-on: http://review.coreboot.org/4996
Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com>
Tested-by: build bot (Jenkins)
| src/soc/intel/baytrail/baytrail/nvs.h | diffblobblamehistory |