about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 7457Kartik Agaram2020-12-282-10/+14
|
* 7456Kartik Agaram2020-12-281-2/+1
|
* 7455Kartik Agaram2020-12-281-2/+15
| | | | | | | | | | New approach to disambiguating /disp32 arguments: based on opcodes rather than metadata. I interpret /disp32 as PC-relative in a short list of instructions. Otherwise it's absolute if it gets a label. There should be no reason to pass labels into /disp8 or /disp16.
* 7454Kartik Agaram2020-12-285-341/+119
| | | | Go back to commit 7448.
* 7453Kartik Agaram2020-12-281-74/+23
| | | | | Snapshot: this approach of disambiguating /disp32 based on metadata doesn't work. The `survey` phase runs after `pack`, which gets rid of most metadata.
* 7452Kartik Agaram2020-12-284-24/+286
|
* 7451Kartik Agaram2020-12-284-20/+28
|
* 7450Kartik Agaram2020-12-282-2/+2
|
* 7449Kartik Agaram2020-12-281-0/+3
| | | | | | | | | | | | | | | | | | | | There's an ambiguity in how x86 interprets disp32 fields: - For jumps and calls they're displacements from the starting address of the next instruction. So far so good. - However, when the ModR/M requires them they can also be absolute addresses. Ideally I'd take the presence of the ModR/M byte into account in interpreting them. However, it's easier to assume relative addressing only for labels in the code segment. This commit raises an error if we ever refer to labels in the code segment in instructions with a ModR/M byte. (I'm assuming that no instruction with a ModR/M byte will ever use a displacement without the ModR/M byte requiring it.)
* 7448Kartik Agaram2020-12-282-0/+18
|
* 7447Kartik Agaram2020-12-282-2/+2
|
* 7446Kartik Agaram2020-12-282-185/+0
|
* 7445Kartik Agaram2020-12-282-185/+0
|
* 7444Kartik Agaram2020-12-281-1/+1
|
* 7443Kartik Agaram2020-12-284-0/+4802
| | | | | A new phase for baremetal compilations. Doesn't work yet, but it passes all its tests, so we can add it to CI.
* 7442Kartik Agaram2020-12-283-0/+10
|
* 7441Kartik Agaram2020-12-2816-16/+16
|
* 7440Kartik Agaram2020-12-282-18/+18
|
* 7439 - start translating Mu programs to baremetalKartik Agaram2020-12-2810-19/+19
|
* 7438Kartik Agaram2020-12-283-244/+600
|
* 7437 - baremetal: draw pixel on keyboard eventKartik Agaram2020-12-282-7/+68
| | | | | It's now clear that our keyboard handler doesn't trigger after the first event.
* 7436Kartik Agaram2020-12-272-22/+22
| | | | Start highlighting lines that may need to be recomputed when offsets change.
* 7435 - baremetal: buffer for keyboard eventsKartik Agaram2020-12-271-20/+49
| | | | | | | | | I'm trying to read the status register, but I'm still not seeing the breakpoint being hit a second time. (And I again ran into the Bochs bug that breakpoints at the first instruction of an interrupt handler don't work.) Maybe this is just a debugger issue. Let's keep going, and try to start using the keyboard events.
* 7434Kartik Agaram2020-12-271-1/+1
| | | | Fix a stale displacement.
* 7433 - some major layout changesKartik Agaram2020-12-272-55/+51
| | | | | | I'd missed that VBE call 0x4f01 (get video mode) can write up to 256 bytes. Unexpected areas were getting clobbered because I wasn't reserving enough space.
* 7432Kartik Agaram2020-12-271-5/+5
| | | | | Bugfix: 32-bit code in 16-bit mode. Seems like it was benign, maybe.
* 7431Kartik Agaram2020-12-271-1/+1
| | | | Typo.
* 7430Kartik Agaram2020-12-271-1/+1
|
* 7429Kartik Agaram2020-12-272-0/+7
|
* 7428Kartik Agaram2020-12-278-555/+0
|
* 7427Kartik Agaram2020-12-274-4/+4
|
* 7426Kartik Agaram2020-12-273-57/+154
|
* 7425 - baremetal: render the paletteKartik Agaram2020-12-271-6/+5
| | | | | It's now very obvious that we don't actually have 256 unique colors by default in 256-color graphics modes.
* 7424 - baremetal: downsize graphics resolutionKartik Agaram2020-12-274-6/+7
| | | | | | | | If it's large enough that I have doubts whether my top-of-the-line Mac is showing the bottom of the screen inside an emulator, it's too large. This way I also feel more confident that most modern hardware will support this graphics mode, and that these programs will work for others.
* 7423Kartik Agaram2020-12-271-6/+15
|
* 7422Kartik Agaram2020-12-261-2/+1
|
* 7421 - baremetal: beginnings of keyboard mapKartik Agaram2020-12-261-16/+37
| | | | First keypress is detected, but we need to ack it somehow.
* 7420Kartik Agaram2020-12-261-1/+2
|
* 7419Kartik Agaram2020-12-261-0/+1
|
* 7418 - baremetal: adjust entrypoint addressKartik Agaram2020-12-264-8/+151
| | | | | | | | | | | 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).
* 7417 - baremetal: drawing on LFB in BochsKartik Agaram2020-12-262-2/+3
|
* 7416 - baremetal: drawing on frame bufferKartik Agaram2020-12-261-6/+17
| | | | | This currently works on Qemu, but not on Bochs. I'm now trying to make sense of https://wiki.osdev.org/Bochs_VBE_Extensions#Using_a_linear_frame_buffer_.28LFB.29
* 7415 - baremetal: locate the linear frame bufferKartik Agaram2020-12-261-6/+55
| | | | | 0xa0000 only contains a single bank's worth of memory-mapped video RAM. The LFB is supposed to have everything.
* 7414Kartik Agaram2020-12-261-14/+14
|
* 7413Kartik Agaram2020-12-261-4/+4
|
* 7412 - drawing pixels to screenKartik Agaram2020-12-264-3/+32
| | | | | This works, but colors are unexpected. 0xff isn't white. Lots of colors are black. Perhaps I need to initialize a palette.
* 7411Kartik Agaram2020-12-261-1/+1
|
* 7410Kartik Agaram2020-12-261-1/+1
|
* 7409Kartik Agaram2020-12-261-1/+1
|
* 7408Kartik Agaram2020-12-261-2/+2
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-18 09:30:20 +0000