Cycling and Coding Around the World

Most cyclists who enter Mongolia through the western border with China stick to the main road for the first days, heading north or east.

Crossing the Pamirs was always the main goal of this journey without a fixed destination.

During my recent discussions about upstreaming a new Linux kernel driver, a tool was mentioned that I had not used before: Include What You Use (IWYU).

💡 This article contains Amazon affiliate links.

This article is still only available on Patreon for HACKERS here.

Our bikepacking adventure towards Central Asia (and beyond!)

This article is still only available on Patreon for HACKERS here.

This article is still only available on Patreon for HACKERS here.

Our bikepacking adventure towards Central Asia (and beyond!)

This article is still only available on Patreon for HACKERS here.

This article is still only available on Patreon for HACKERS here.

This article is still only available on Patreon for HACKERS here.

This article is still only available on Patreon for HACKERS here.

This article is still only available on Patreon for HACKERS here.

I have been writing articles about Linux for over a year, and I just realized that I did not cover the first and foremost point for many beginners: how to install a Linux-based operating system!

Although people have been bikepacking for many decades, it seems that nowadays you must have a $2000+ state-of-the-art bike to do so unless you are a bike mechanic.

This third episode brings up a key feature for all Linux device drivers that read and write registers, either memory mapped or through a communication protocol.

In this episode we are going to actually write a device driver and interact with a device.

💡 This article contains Amazon affiliate links.

The day has finally arrived: I’m starting a series on how to write your first device driver for Linux.

Although I’m someone who tends to leave a lot to improvisation, I’m not so carefree as to skip testing the gear I’ll take on the BIG JOURNEY.

I’m packing my bags and off to discover the world by bike.

Most of the articles about Open Source (including mine) only focus on technical aspects: coding, statistics, results, etc.

Building the Linux kernel from scratch is very easy: you only need the source code (git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git), a few tools to be able to compile it (the list of minimal requirements is here), and simple co…

Without setting a precedent, this time I am going to talk about some userland tools.

I have said several times in different articles that contributing to the Linux kernel is both satisfying and rewarding.

After spending some days learning how some compiler attributes (__cleanup, __counted_by) work in the Linux kernel, and fixing multiple bugs by using them properly, I have decided to move on, and start learning how Rust is used in the Linux kernel.

This second and last episode about the automatic cleanup mechanisms in the Linux kernel covers the concept of classes, macros being used to automatically release resources like mutexes, and the ongoing work to increase its coverage.

One of the most common criticisms of the C programming language is that dynamically allocated objects are not automatically released.

The vast majority of devices supported by the Linux kernel require little to no intervention to start running: maybe powering up (e.g. via regulators), de-asserting a reset or accessing a few configuration registers.