Compare commits

...

2 commits

Author SHA1 Message Date
bb8caf62bf
the tweaks will continue until morale improves 2025-04-02 11:35:44 -04:00
2c7f53616e
slight edit 2025-04-02 11:35:24 -04:00
4 changed files with 6 additions and 6 deletions

View file

@ -69,6 +69,7 @@ header {
padding: 1rem; padding: 1rem;
display: block; display: block;
overflow-x: auto; overflow-x: auto;
font-size: 90%;
} }
article h1 { article h1 {
@ -136,6 +137,5 @@ hr {
code { code {
/* what a horrible hack*/ /* what a horrible hack*/
font-family: monospace, serif; font-family: monospace, serif;
font-size: 90%;
white-space: preserve nowrap; white-space: preserve nowrap;
} }

View file

@ -16,7 +16,7 @@ I need to set up a good workflow for building and testing.
## Building the Kernel ## Building the Kernel
For this go around, I decided to write my kernel in Zig. I've gotten too used to For this go around, I decided to write my kernel in Zig.[^name] I've gotten too used to
the conveniences of a modern language to go back to C, and while I love Rust the conveniences of a modern language to go back to C, and while I love Rust
dearly I've found myself frustrated by having to use shell scripts and make to dearly I've found myself frustrated by having to use shell scripts and make to
take care of the parts of getting to a bootable image that Cargo doesn't concern take care of the parts of getting to a bootable image that Cargo doesn't concern
@ -82,6 +82,8 @@ a little strange in that it reads most of its firmware from the boot drive
instead of from flash on the board. Normally we'd just download these firmware instead of from flash on the board. Normally we'd just download these firmware
files ourselves, but we can do better! files ourselves, but we can do better!
[^name]: Hence the name taken from [my recent reading][visions], which
conveniently starts with Z and has OS in it (twice!).
[^2]: The filename `kernel8.img` is important since it tells the board to boot [^2]: The filename `kernel8.img` is important since it tells the board to boot
up in 64 bit mode. This can be overridden in [`config.txt`][7] if you really up in 64 bit mode. This can be overridden in [`config.txt`][7] if you really
want a different filename. want a different filename.
@ -89,6 +91,7 @@ files ourselves, but we can do better!
[1]: https://git.wires.systems/wires/zosimos/src/commit/8466e9b4d2fbca85d53d8dadc87914b4766c43de/src [1]: https://git.wires.systems/wires/zosimos/src/commit/8466e9b4d2fbca85d53d8dadc87914b4766c43de/src
[code]: https://git.wires.systems/wires/zosimos/src/commit/b6b96f651f060ae6cff9e4e184799bb354ce6d07 [code]: https://git.wires.systems/wires/zosimos/src/commit/b6b96f651f060ae6cff9e4e184799bb354ce6d07
[7]: https://www.raspberrypi.com/documentation/computers/config_txt.html [7]: https://www.raspberrypi.com/documentation/computers/config_txt.html
[visions]: https://www.3ammagazine.com/3am/three-visions-of-zosimus/
## Fetching Firmware ## Fetching Firmware

View file

@ -2,7 +2,6 @@ baseURL = 'https://wires.systems'
languageCode = 'en-us' languageCode = 'en-us'
title = "wires" title = "wires"
uglyurls = true uglyurls = true
enableGitInfo = true
disableKinds = ['section'] disableKinds = ['section']
summaryLength = 10 summaryLength = 10

View file

@ -2,9 +2,7 @@
<article> <article>
<header> <header>
<h1>{{ .Title }}</h1> <h1>{{ .Title }}</h1>
<time datetime="{{ .Lastmod }}" <time datetime="{{ .Date }}">{{ .Date.Format "January 2, 2006" }}</time>
>{{ .Lastmod.Format "January 2, 2006" }}</time
>
</header> </header>
{{ if .Params.toc }} {{ if .Params.toc }}
<aside id="toc"> <aside id="toc">