Getting a little more organized in my workshop. My pain point was boxes of nails or screws falling off shelves.
And, of course, I wanted an excuse to use the laser cutter.
I took a lesson from Minecrafters and put an instance of what was inside the box on the front id the box.
We use gitlab to post internal releases of archives. I want to be able to automate the process of downloading these artifacts. Here it is using the glab CLI.
Continue readingOn Fedora:
yum install termdebugin ~/.vimrc
let g:termdebug_config = {}
let g:termdebug_config['command'] = 'rust-gdb'
packadd! termdebug
Inside vim:
Termdebug target/debug<executable>
Use Ctrl-W DownArrow to switch between windows
Use :Break to set a breakpoint in the code window
Use Ctrl-W UpArrow to go to the gdb window
use run to run the program and cont to continue after hitting a break point.
I usually don’t want all of the files in the linux Kernel for my ctags. Sometimes I want a cvery small subset: a set of C files and the included header files.
Continue readingI got my network working again, and this time I am running the VM as non-root user.
Continue readingTHe cloud image is shipped as a qcow2 file. It has about 3 GB of usable space. I need more.
Continue readingAfter building a custom Qemu, there are a couple ways to run a VM to get to it. The older approach to VM management is to create a block device, run the VM with a boot device, do a full install and log in to the serial console. However, if you run the Qemu/KVM machine from the command lilne, hitting control C will stop your VM, and this is annoying. I have found it worth while to set up networking and then to SSH in to the machine.
My notes here suck. I am going to try and document what I have here working, and, over time, reverse engineer how I got here.
Edit: here are the steps
In order to perform test driven development, you need a way to drive your code that can isolate behavior. Linux Kernel drivers that communicate with hardware devices can be hard to test: you might not have access to the hardware from your test systems, or the hardware may be flakey. I have such a set of issues with the Platform Communication Channel (PCC) drivers I am working with.
My primary work has been with a network driver that only exists on the newest hardware. However, I also need to be able to handle some drivers that would only work against old hardware. There are also PCC based drivers for hardware that my company does not support or have access to. I might want to make a test to ensure that changes to the Linux Kernel PCC driver does not change its behavior against these drivers. There exists no system where all of these drivers would be supported. But I can build one with Qemu.
The Qemu based driver might not completely simulate the hardware exactly as implemented, and that is OK: I want to be able to do things with Qemu I cannot do with current hardware. For example, the MCTP-over-PCC driver should be able to handle a wide array of messages, but the hardware I have access to only supports a very limited subset of message types.
The full code for the device is here.
Here is how I went about building a Qemu based PCC driver.
Continue readingChanges do not always get accepted upon initial submission. My current submission of the MCTP over PCC patch is at revision 37 and will likely have more. Previously, this patch was part of a series, and the change log was displayed in the series header email. However, now that I am down to a single patch, the change log should go in the email message with the patch attached.
It rturns out this is fairly simple to do: Puyt the change log at the =bottom of the commit message, after the Signed-Off-By tag. and after three dashes:
Continue reading