diff options
author | 2011-02-07 23:25:00 -0500 | |
---|---|---|
committer | 2011-02-28 16:22:18 +0100 | |
commit | 299c56966a72b9109d47c71a6db52097098703dd (patch) | |
tree | e2cbb4a2f38a6002cfb53112fc8e04e959585939 /drivers/mmc/host/omap_hsmmc.c | |
parent | Merge branch 'pm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6 (diff) | |
download | wireguard-linux-299c56966a72b9109d47c71a6db52097098703dd.tar.xz wireguard-linux-299c56966a72b9109d47c71a6db52097098703dd.zip |
x86: Use u32 instead of long to set reset vector back to 0
A customer of ours, complained that when setting the reset
vector back to 0, it trashed other data and hung their box.
They noticed when only 4 bytes were set to 0 instead of 8,
everything worked correctly.
Mathew pointed out:
|
| We're supposed to be resetting trampoline_phys_low and
| trampoline_phys_high here, which are two 16-bit values.
| Writing 64 bits is definitely going to overwrite space
| that we're not supposed to be touching.
|
So limit the area modified to u32.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Acked-by: Matthew Garrett <mjg@redhat.com>
Cc: <stable@kernel.org>
LKML-Reference: <1297139100-424-1-git-send-email-dzickus@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/mmc/host/omap_hsmmc.c')
0 files changed, 0 insertions, 0 deletions