0fa6d28e14
7429
2020-12-27 11:50:05 -08:00
47287fbf1a
7401 - clean up support for non-Linux platforms
2020-12-25 12:28:10 -08:00
a94ac8f068
7393
...
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.
2020-12-23 22:18:11 -08:00
6cd12b1822
7374
2020-12-21 23:11:02 -08:00
670cbb3d33
7351
2020-12-14 20:02:21 -08:00
e786968a9c
7268
2020-11-20 17:08:01 -08:00
396a7ef691
7265
2020-11-17 19:06:19 -08:00
fc83d26766
7264
2020-11-17 19:03:55 -08:00
1eb1cade71
7259
2020-11-17 13:12:36 -08:00
e3349a169c
7255
2020-11-17 08:20:27 -08:00
3b12aab3bc
7235 - belatedly add spiritual forks
2020-11-14 11:28:40 -08:00
2136ad26b8
7204
2020-11-07 15:12:53 -08:00
07a1a29912
clarify that we don't use C++20 modules
2020-10-23 11:17:57 -07:00
9a83eac410
new fork
2020-10-23 00:18:35 -07:00
97f4d3ed95
Fix broken link
2020-10-08 20:05:56 -04:00
7817fdb29c
6640
...
Re-sync markdown files with mu-normie fork.
2020-07-12 16:37:58 -07:00
ac8b37f9a8
6639
2020-07-12 16:28:24 -07:00
7b5ad6028c
6633
2020-07-11 09:10:57 -07:00
9a524793ee
6618 - new docs
2020-07-06 01:05:10 -07:00
64bf0e8b97
6499
2020-06-07 15:43:13 -07:00
e2e0f5cce7
6498
...
Switch bullet lists in Markdown files away from `*`; it's ambiguous with
emphasis.
2020-06-06 15:55:03 -07:00
3351d83f8b
6403
2020-05-24 23:06:07 -07:00
f5c45f8614
6402
2020-05-24 23:03:20 -07:00
7852e65c7f
6386 - documentation on editor setup
2020-05-23 00:24:13 -07:00
b338e82e22
6218 - link to Mu's first fork
2020-05-10 13:21:52 -07:00
d260b01748
6200 - --dump is not needed for incremental traces
...
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.
2020-04-09 00:56:32 -07:00
6efd1778e1
6174
2020-03-27 09:07:04 -07:00
0ea5f759fc
6171
2020-03-25 11:46:07 -07:00
8fa7c79685
6168
2020-03-25 09:39:46 -07:00
9470451cb1
6167
2020-03-25 09:21:06 -07:00
7d117e4699
6166
2020-03-25 09:20:33 -07:00
41d5e711f2
6165
2020-03-25 09:16:04 -07:00
e1de7e0661
6154 - include link to the Mu paper
2020-03-16 01:53:09 -07:00
e2a0b44073
6151
2020-03-15 10:54:25 -07:00
b7b24ec242
6142
2020-03-14 01:03:30 -07:00
9f589350cf
6141
2020-03-14 00:58:52 -07:00
a598d09082
6140
2020-03-14 00:50:38 -07:00
e420279ac1
6127
2020-03-11 19:50:49 -07:00
924ed08aca
5968
2020-02-01 12:14:20 -08:00
aeac1e061d
5966 - document all supported Mu instructions
2020-01-31 18:55:37 -08:00
4bb0b7e93f
5965
2020-01-31 16:17:04 -08:00
730e689467
5886
2020-01-12 21:30:29 -08:00
6f1581e77b
5874
2020-01-02 15:13:44 -08:00
300aa16720
5873
2020-01-02 15:11:10 -08:00
8bbafb1397
5872
2020-01-02 14:12:46 -08:00
42b4da908e
5871
2020-01-02 13:57:47 -08:00
e968735e60
5869
2020-01-02 12:43:24 -08:00
7fd4a87066
5868
...
Follow stupid GNU convention, because why not:
https://www.gnu.org/prep/standards/html_node/Releases.html
2020-01-02 12:27:35 -08:00
Kartik Agaram
Jimmy Miller