about summary refs log tree commit diff stats
path: root/boot.subx
Commit message (Collapse)AuthorAgeFilesLines
* start hacky experiment to support combining charsKartik K. Agaram2021-08-311-1/+1
| | | | | | | | | | | https://en.wikipedia.org/wiki/Combining_character The plan: just draw the combining character in the same space as the previous character. This will almost certainly not work for some Unicode blocks (tibetan?) This commit only changes the data/memory/disk model to make some space. As always in Mu, we avoid bit-mask tricks even if that wastes memory.
* load Font in a non-contiguous area of memoryKartik K. Agaram2021-08-291-0/+8
|
* .Kartik K. Agaram2021-08-291-1/+1
|
* .Kartik K. Agaram2021-08-291-3/+3
|
* retreat to 640KBKartik K. Agaram2021-08-291-15/+3
|
* build still brokenKartik K. Agaram2021-08-291-0/+28
| | | | | Now we load all the code, but it overwrites the extended BIOS area. 640KB is no longer enough. Need to rethink loading strategy.
* reorganize font before adding non-ASCIIKartik K. Agaram2021-08-271-238/+0
|
* update memory map doc and anticipate a gotchaKartik K. Agaram2021-07-221-3/+3
|
* .Kartik K. Agaram2021-07-161-9/+9
|
* initial image renderingKartik K. Agaram2021-07-071-0/+7
| | | | | | Supports just some ASCII formats: https://en.wikipedia.org/wiki/Netpbm Colors are messed up. That's next.
* grow code region yet againKartik K. Agaram2021-07-051-0/+14
| | | | We need a cleaner way to do this.
* more general timer interfaceKartik K. Agaram2021-06-291-17/+2
|
* move timer handler to boot.subxKartik K. Agaram2021-06-291-4/+26
|
* .Kartik K. Agaram2021-06-291-10/+8
|
* poking at the broken timer interrupt handler againKartik K. Agaram2021-06-291-19/+1
|
* ok, function modal now has full coverageKartik K. Agaram2021-06-081-12/+26
|
* .Kartik K. Agaram2021-05-301-10/+10
|
* fix a bug in loading code diskKartik K. Agaram2021-05-291-1/+1
| | | | Identical bug to commit 2f10bc7302.
* shell: skeleton for scrollingKartik K. Agaram2021-05-291-0/+14
|
* press '0' to reset all stateKartik K. Agaram2021-05-161-1/+1
|
* .Kartik K. Agaram2021-05-141-1/+1
|
* load debug info from disk on abortKartik K. Agaram2021-05-141-6/+28
|
* expand stack to 16MBKartik K. Agaram2021-04-251-4/+4
| | | | It's also no longer contiguous with code.
* expand heap to Qemu defaultKartik Agaram2021-04-251-2/+2
|
* .Kartik K. Agaram2021-04-191-1/+2
|
* fix a bug in loading code diskKartik K. Agaram2021-04-181-1/+1
|
* revert experiment: expand heapKartik K. Agaram2021-04-181-3/+2
| | | | | There are several things in the codebase right now that don't seem sustainable. I need to take them out and bring them back in more gradually.
* experiment: expand heapKartik K. Agaram2021-04-181-2/+3
|
* update the memory mapKartik K. Agaram2021-04-181-1/+1
|
* shell: ctrl-r runs on real screen without a traceKartik K. Agaram2021-04-171-0/+14
| | | | | We run out of memory fairly early in the course of drawing a chessboard on the whole screen.
* write-multiple supportKartik K. Agaram2021-04-171-3/+24
| | | | | | | Is flush-ata-cache even needed? Reading the ATA 5 spec more closely, it looks like it's only required by ATAPI devices! (Packet Interface is what the 'PI' stands for!) And it's unclear if my driver actually supports ATAPI at the moment.
* start flushing the ATA disk cacheKartik K. Agaram2021-04-171-0/+18
| | | | | | "Make sure to do a Cache Flush (ATA command 0xE7) after each write command completes." https://wiki.osdev.org/index.php?title=ATA_PIO_Mode&oldid=25664#Writing_28_bit_LBA
* starting write-multiple supportKartik K. Agaram2021-04-171-52/+55
|
* data.img now has more than one sector of dataKartik K. Agaram2021-04-161-33/+78
|
* support for arrow keysKartik K. Agaram2021-04-051-4/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mu's keyboard handling is currently a bit of a mess, and this commit might be a bad idea. Ideally keyboards would return Unicode. Currently Mu returns single bytes. Mostly ASCII. No support for international keyboards yet. ASCII and Unicode have some keyboard scancodes grandfathered in, that don't really make sense for data transmission. Like backspace and delete. However, other keyboard scancodes don't have any place in Unicode. Including arrow keys. So Mu carves out an exception to Unicode for arrow keys. We'll place the arrow keys in a part of Unicode that is set aside for implementation-defined behavior (https://en.wikipedia.org/wiki/C0_and_C1_control_codes#C1_controls): 0x80: left arrow 0x81: down arrow 0x82: up arrow 0x83: right arrow The order is same as hjkl for mnemonic convenience. I'd _really_ to follow someone else's cannibalization here. If I find one later, I'll switch to it. Applications that blindly assume the keyboard generates Unicode will have a bad time. Events like backspace, delete and arrow keys are intended to be processed early and should not be in text. With a little luck I won't need to modify this convention when I support international keyboards.
* undo previous commitKartik K. Agaram2021-04-051-118/+89
|
* snapshot: stupid debugging sessionKartik K. Agaram2021-04-051-89/+118
| | | | | | | | | | | | | | | I spent a while building a little keyboard scancode printer: $ ./translate ex1.mu && qemu-system-i386 disk.img ..and wondering why up-arrow was 0x48 in hex but 724 in decimal. I ended up paranoidly poking at a bunch of crap (though there _is_ a cool chromatography-based debugging technique in 126write-int-decimal.subx) before I realized: - 724 just has one extra digit over the correct answer - the 0xe0 scan code is a 3-digit number in decimal -- and the final digit is '4' There's nothing actually wrong.
* delete some obsolete filesKartik Agaram2021-04-041-2/+0
| | | | | They stopped working ever since boot.subx started relying on functions (for the disk driver) implemented in Mu.
* .Kartik K. Agaram2021-04-021-2/+2
|
* .Kartik K. Agaram2021-03-281-0/+2
|
* .Kartik K. Agaram2021-03-281-2/+20
|
* always acknowledge enabled interruptsKartik K. Agaram2021-03-281-2/+17
| | | | | Now we can start enabling the timer interrupt. It doesn't do anything yet, but keyboard continues to work.
* .Kartik K. Agaram2021-03-271-169/+0
| | | | Clean up some debug prints.
* explicitly pass data disk to mainKartik K. Agaram2021-03-271-99/+296
|
* .Kartik K. Agaram2021-03-271-1/+1
| | | | | | | https://wiki.osdev.org/ATA_PIO_Mode#IDENTIFY_command recommends the straight-and-narrow way, but the LBA bit shouldn't matter in drive-select during IDENTIFY command, according to the ATA 3 spec. And it works in Qemu and bochs. It'll slightly simplify drive parameter management.
* .Kartik K. Agaram2021-03-231-125/+132
|
* reorg boot.subxKartik K. Agaram2021-03-231-10/+9
|
* mouse support that requires pollingKartik K. Agaram2021-03-231-2/+213
|
* get rid of unnecessary paddingKartik K. Agaram2021-03-231-115/+2
| | | | Now we only specify addresses where it matters.
* .Kartik K. Agaram2021-03-231-3/+5
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-06-01 21:47:09 +0000