diff options
author | Kartik Agaram <vc@akkartik.com> | 2020-12-23 11:10:52 -0800 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2020-12-23 11:10:52 -0800 |
commit | e60e0e06453788c769c457c64448fa5d00681707 (patch) | |
tree | 90b339fb44fdc3bb6523c1a5eada569dfb681845 /310copy-bytes.subx | |
parent | 286ccc40e0c0ec2f897cd93a730ea8bacc84cf3e (diff) | |
download | mu-e60e0e06453788c769c457c64448fa5d00681707.tar.gz |
7389 - snapshot
Ok, we're back at the reset loop. Let's keep going; maybe having a decent keyboard handler will fix it. The bug I fixed here was caused by misunderstanding what m16&32 mean in the Intel manual. It's still a regular regmem operand that uses all of the ModR/M byte (which can be interpreted in 16-bit mode, adding to the complication). It's just constrained to not allow direct addressing (mod 00). I needed to better internalize the format of the instruction set references at the start of Volume 2, Chapter 3.
Diffstat (limited to '310copy-bytes.subx')
0 files changed, 0 insertions, 0 deletions