This post continues after Keyboard from scratch. I messed up. I don’t know the exact details yet, but for some reason with the code linked in the previous post, the interrupts don’t come through. So, back to blinky we go. Blinky? Blinky is quite literally the example that just lights up an LED for a second then turns it off for a second again. The code is pretty simple and just downloaded from upstream. So, stepwise we iterate on building up interrupt driven code again, to see what’s going wrong here. Add GPIO IN Step one, add GPIO read to see whether what we are doing on the outside of the device actually has the impact on MCU state that we want.

Like the blog title says, I like to tinker with things that make no sense. I recently got msyelf an irix keyboard for work. Since I like the split design and my MX Blue switches at home make it impossible to listen and write at the same time, I want to build another set. It’d be boring to just build another iris though. So I decided to go down another route. One that’s more custom. Way more custom… I had some longan nano laying around. So I decided to base my new keyboard on those. As I soon realized, that’s not supported by qmk.

If you got linked to the toplevel of this file, something went wrong. The main post is Sway and systemd. This post is intended as technical details and the “why”. The main post has the motivation and for all of this. SDDM /etc/sddm.conf.d/autologin.conf is the only config file I have here. [Autologin] User=ongy Session=sway-systemd.desktop Sway stuff sway.desktop This is the .desktop file that should be used for our sway session. It’s placed into /usr/share/wayland-sessions/sway-systemd.desktop [Desktop Entry] Name=Sway Service Comment=Start sway via systemd Exec=sway-service.sh Type=Application It needs a secondary shell script, for me it’s at /usr/local/bin/sway-service.sh #!/bin/sh systemctl --user import-environment exec systemctl --wait --user start sway.

For some reason, that I don’t even remember, I wanted to have my user daemons started by systemd. Partially as an exercise, partially to have them auto-restart and to get a bit more familiar with the concept. The first task to get this done, is to start sway (or whatever compositor you use) via systemd, so we don’t run into any timing problems. While logging into a tty and starting sway works fine, I decided I want to directly boot into sway. My boot queries for the disk encryption passphrase on boot either way. Start the user instance Most of what I wanted to use is done by the systemd --user instance started for every user on login.