diff options
author | Mark Kettenis <kettenis@cvs.openbsd.org> | 2014-06-25 18:56:23 +0000 |
---|---|---|
committer | Mark Kettenis <kettenis@cvs.openbsd.org> | 2014-06-25 18:56:23 +0000 |
commit | 0ad416830e124b328c29547f04ba192771edbcd6 (patch) | |
tree | 5d291d60e49cc630ab5aacdcb2973736c1d61ad2 /regress/sbin/isakmpd | |
parent | 2fbda58435b198fcaf2a5db548561886d5b9eff0 (diff) |
So it turns out that there is AML out there that asks for an access
width that isn't compatible with the alignment of the region:
OperationRegion (SATC, SystemMemory, 0xE008800A, 0x04)
Field (SATC, DWordAcc, NoLock, Preserve)
{
STCL, 16
}
DWordAcc means 4-byte access, but 0xE008800A is only 2-byte aligned.
Moreover, the region itself is 4 bytes long. From this I conclude
that 4-byte wide access to a 2-byte aligned address is really wanted
in cases like this.
ok deraadt@
Diffstat (limited to 'regress/sbin/isakmpd')
0 files changed, 0 insertions, 0 deletions