about summary refs log tree commit diff stats
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
* make the library reference easier to findKartik K. Agaram2021-03-091-16/+18
|
* .Kartik K. Agaram2021-03-091-10/+13
|
* 7848Kartik K. Agaram2021-03-041-2/+2
|
* 7847Kartik K. Agaram2021-03-041-2/+1
|
* 7846Kartik K. Agaram2021-03-041-1/+1
|
* 7845Kartik K. Agaram2021-03-031-0/+2
|
* 7844Kartik K. Agaram2021-03-031-7/+8
|
* 7843 - clean up README after directory reorgKartik K. Agaram2021-03-031-32/+41
|
* 7842 - new directory organizationKartik K. Agaram2021-03-031-36/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Baremetal is now the default build target and therefore has its sources at the top-level. Baremetal programs build using the phase-2 Mu toolchain that requires a Linux kernel. This phase-2 codebase which used to be at the top-level is now under the linux/ directory. Finally, the phase-2 toolchain, while self-hosting, has a way to bootstrap from a C implementation, which is now stored in linux/bootstrap. The bootstrap C implementation uses some literate programming tools that are now in linux/bootstrap/tools. So the whole thing has gotten inverted. Each directory should build one artifact and include the main sources (along with standard library). Tools used for building it are relegated to sub-directories, even though those tools are often useful in their own right, and have had lots of interesting programs written using them. A couple of things have gotten dropped in this process: - I had old ways to run on just a Linux kernel, or with a Soso kernel. No more. - I had some old tooling for running a single test at the cursor. I haven't used that lately. Maybe I'll bring it back one day. The reorg isn't done yet. Still to do: - redo documentation everywhere. All the README files, all other markdown, particularly vocabulary.md. - clean up how-to-run comments at the start of programs everywhere - rethink what to do with the html/ directory. Do we even want to keep supporting it? In spite of these shortcomings, all the scripts at the top-level, linux/ and linux/bootstrap are working. The names of the scripts also feel reasonable. This is a good milestone to take stock at.
* 7834Kartik Agaram2021-03-011-2/+3
|
* 7833Kartik Agaram2021-02-281-8/+7
|
* 7832Kartik K. Agaram2021-02-281-0/+2
|
* 7831Kartik K. Agaram2021-02-281-26/+31
|
* 7756Kartik Agaram2021-02-181-3/+6
|
* 7755Kartik Agaram2021-02-181-3/+3
|
* 7754Kartik Agaram2021-02-171-16/+23
|
* 7691Kartik Agaram2021-02-071-4/+5
|
* 7681Kartik Agaram2021-02-011-4/+3
|
* 7675 - drop Travis CIKartik Agaram2021-01-281-2/+0
|
* 7475Kartik Agaram2020-12-301-7/+7
|
* 7471Kartik Agaram2020-12-291-0/+7
|
* 7465Kartik Agaram2020-12-291-4/+3
|
* 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
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-16 14:56:58 +0000