diff options
| author | Gabe Black <gabeblack@chromium.org> | 2013-03-02 21:00:03 -0800 |
|---|---|---|
| committer | ChromeBot <chrome-bot@google.com> | 2013-03-04 14:30:23 -0800 |
| commit | 522da3e2c9c016a4bc2124cde69a688e790c9dc5 (patch) | |
| tree | 4d9fde43f508765427ae0ab3f01577dabcbcbf06 /firmware/include/utility.h | |
| parent | 51d22d5f8d05b582423978894352e8f30fd164b6 (diff) | |
| download | vboot-522da3e2c9c016a4bc2124cde69a688e790c9dc5.tar.gz | |
Use Memcpy to avoid unaligned accesses when using RollbackKernelSpace.
This structure, like RollbackSpaceFirmware in my previous CL, contains members
that are inherently unaligned. This breaks when the machine running vboot
cares about alignment. Like before, I'm using Memcpy to avoid the direct
unaligned accesses.
BUG=chrome-os-partner:17340
TEST=Built and booted into depthcharge on Snow. Without this change, there's
an unaligned access in RollbackKernelRead. After this change, the unaligned
access goes away and vboot gets at the kernel version successfully.
BRANCH=None
Change-Id: Ifcdcee1ab4bbce74d05e563cb82bef73a1aa9a84
Signed-off-by: Gabe Black <gabeblack@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/44503
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Queue: Gabe Black <gabeblack@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
Diffstat (limited to 'firmware/include/utility.h')
0 files changed, 0 insertions, 0 deletions