diff options
| author | Kartik Agaram <vc@akkartik.com> | 2020-12-26 22:33:48 -0800 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2020-12-26 22:36:52 -0800 |
| commit | 6f3f8148399abdba78c7fb1e8a2b635af67215ff (patch) | |
| tree | ca416060c021661af3811a5a65538078c9de07ed /baremetal/README.md | |
| parent | 0243ee4e834e4118e3c2eadc68d36f8e62d94d28 (diff) | |
| download | mu-6f3f8148399abdba78c7fb1e8a2b635af67215ff.tar.gz | |
7418 - baremetal: adjust entrypoint address
We need a few pages of data for the keyboard mappings. If I moved them to some later address I'd be able to keep the nice round starting address unchanged. But that seems like a superficial aesthetic concern. There's really no value in having an array of hex bytes represented in SubX rather than just raw hex. And it's better to colocate data near the handler code which uses it (and which runs instructions SubX doesn't support).
Diffstat (limited to 'baremetal/README.md')
| -rw-r--r-- | baremetal/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/baremetal/README.md b/baremetal/README.md index e2bc81c4..e87cd74c 100644 --- a/baremetal/README.md +++ b/baremetal/README.md @@ -20,7 +20,7 @@ keyboard. These programs don't convert to ELF, and there's also currently no code/data segment separation. Just labels and bytes. -Most programs here assume `main` starts at address 0x8000 (1KB or 2 disk +Most programs here assume `main` starts at address 0x8800 (3KB or 6 disk sectors past the BIOS entrypoint). See baremetal/boot.hex for details. So far the programs have only been tested in Qemu and Bochs emulators. |