about summary refs log tree commit diff stats
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
...
* 7429Kartik Agaram2020-12-271-0/+7
|
* 7401 - clean up support for non-Linux platformsKartik Agaram2020-12-251-6/+15
|
* 7393Kartik Agaram2020-12-231-0/+3
| | | | | | | | | | | | | | Snapshot. Keyboard interrupt being triggered. This was hard to debug until https://stackoverflow.com/questions/37618111/keyboard-irq-within-an-x86-kernel reminded me that I'd forgotten to enable IRQ1 on port 0x21. For a while I was confused by never hitting a breakpoint at the start of the keyboard handler. Then I found https://sourceforge.net/p/bochs/discussion/39592/thread/5e397455 and started skipping one instruction in my breakpoint. I still don't understand the discrepancy between some people installing the handler at entry 9, and others installing at entry 0x21 = 33.
* 7374Kartik Agaram2020-12-211-3/+16
|
* 7351Kartik Agaram2020-12-141-1/+1
|
* 7268Kartik Agaram2020-11-201-2/+2
|
* 7265Kartik Agaram2020-11-171-2/+2
|
* 7264Kartik Agaram2020-11-171-3/+5
|
* 7259Kartik Agaram2020-11-171-5/+6
|
* 7255Kartik Agaram2020-11-171-1/+1
|
* 7235 - belatedly add spiritual forksKartik Agaram2020-11-141-0/+6
|
* 7204Kartik Agaram2020-11-071-1/+1
|
* clarify that we don't use C++20 modulesKartik Agaram2020-10-231-1/+1
|
* new forkKartik Agaram2020-10-231-0/+4
|
* Fix broken linkJimmy Miller2020-10-081-1/+1
|
* 6640Kartik Agaram2020-07-121-32/+32
| | | | Re-sync markdown files with mu-normie fork.
* 6639Kartik Agaram2020-07-121-6/+4
|
* 6633Kartik Agaram2020-07-111-2/+2
|
* 6618 - new docsKartik Agaram2020-07-061-710/+78
|
* 6499Kartik Agaram2020-06-071-2/+2
|
* 6498Kartik Agaram2020-06-061-108/+108
| | | | | Switch bullet lists in Markdown files away from `*`; it's ambiguous with emphasis.
* 6403Kartik Agaram2020-05-241-1/+1
|
* 6402Kartik Agaram2020-05-241-1/+1
|
* 6386 - documentation on editor setupKartik Agaram2020-05-231-0/+16
|
* 6218 - link to Mu's first forkKartik Agaram2020-05-101-0/+9
|
* 6200 - --dump is not needed for incremental tracesKartik Agaram2020-04-091-1/+1
| | | | | | | | This undoes commit 5764, which was ill-considered. We already had incremental prints at that point to 'last_run'. As long as we don't run out of RAM on large traces, there doesn't seem any need to print to stderr. Now '--dump' is only needed when juggling multiple traces.
* 6174Kartik Agaram2020-03-271-1/+1
|
* 6171Kartik Agaram2020-03-251-2/+2
|
* 6168Kartik Agaram2020-03-251-1/+1
|
* 6167Kartik Agaram2020-03-251-1/+1
|
* 6166Kartik Agaram2020-03-251-2/+2
|
* 6165Kartik Agaram2020-03-251-10/+10
|
* 6154 - include link to the Mu paperKartik Agaram2020-03-161-1/+1
|
* 6151Kartik Agaram2020-03-151-2/+6
|
* 6142Kartik Agaram2020-03-141-6/+9
|
* 6141Kartik Agaram2020-03-141-0/+12
|
* 6140Kartik Agaram2020-03-141-2/+1
|
* 6127Kartik Agaram2020-03-111-0/+11
|
* 5968Kartik Agaram2020-02-011-8/+10
|
* 5966 - document all supported Mu instructionsKartik Agaram2020-01-311-2/+3
|
* 5965Kartik Agaram2020-01-311-10/+1
|
* 5886Kartik Agaram2020-01-121-3/+4
|
* 5874Kartik Agaram2020-01-021-7/+1
|
* 5873Kartik Agaram2020-01-021-25/+20
|
* 5872Kartik Agaram2020-01-021-7/+7
|
* 5871Kartik Agaram2020-01-021-2/+2
|
* 5869Kartik Agaram2020-01-021-7/+8
|
* 5868Kartik Agaram2020-01-021-0/+791
Follow stupid GNU convention, because why not: https://www.gnu.org/prep/standards/html_node/Releases.html