I've talked to my colleagues that one thing that strikes me in presentations given about any blockchain technology, is that they have a problem that the presentation goes straight into cryptography and smart contracts.

What you *actually* should start with is how the network discovery works. I.e. plain and simple how network nodes find each other. It's not flashy but it is like the first question for any seasoned engineer.

In order to do the secret handshakes you need to first bump into someone else to do your dance.

Multiple capture/output devices issue in the OOT driver and v4l2-loopback. It has the unfinished "SPLIT_DEVICES" compilation options, which I DO NOT fully cope with. I don't get what the heck they are aiming for TBH.

A video device can be either something like camera or something that takes input from client and displays that, e.g. similar device to ChromeCast would be a good example in this context.

I'm aligning to a solution where the initial "ADD" ioctl has:

1. flags (for setting the RW properties)
2. video_nr
3. video_fd (for server to read OR write)

And the direction is determined by flags. I did not fully understand why OOT driver aimed to do both capture and output device simultaneously, which does bother me a bit since it would be best to know the original reasoning, even if the conclusions were wrong.

Moving slowly in this area still and experimenting with options.

#linux #kernel #media #video4linux

At least something done in the kernel side for the v4l2-loopback driver this week:

1. The first baby step towards anonymous inode based loopback device: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?h=v4l2-loopback&id=90235ae07630962e6dc7c6b2b67f9e94584a6b74
2. And a reflective step in my test program: https://codeberg.org/jarkko/v4l2-loopback-test/commit/8950e975817e9d9b8012880dd9f2443d2fe13c77

The next small push is to split v4l2_loopback_fops into two: one for /dev/videoX and other for the anonymous inode returned back from the ioctl.

#linux #kernel #media

Got tired of updating clangd data manually so did a quick script to automate it :

#!/usr/bin/env bash
# Copyright (c) Jarkko Sakkinen 2025

set -e

run_build() {
  make ARCH=x86_64 O=.clangd -j$(nproc)
  scripts/clang-tools/gen_compile_commands.py -d .clangd
}

run_menuconfig() {
  if [[ ! -d .clangd ]]; then
    exit 1
  fi
  make ARCH=x86_64 O=.clangd menuconfig
  run_build
}

while getopts ":m" opt; do
  case $opt in
    m)
      run_menuconfig
      exit 0
      ;;
    *)
      echo "Usage: $0 [-m]"
      exit 1
      ;;
  esac
done

if [[ ! -d .clangd ]]; then
  make ARCH=x86_64 O=.clangd tinyconfig
fi
run_build

#linux #kernel #clangd

Reported to rust-lang/rust if anything to get some ideas how to fix this in the downstream:

https://github.com/rust-lang/rust/issues/135704

It's weird...

#rust #rustlang

https://oddlama.org/blog/bypassing-disk-encryption-with-tpm2-unlock/ #systemd #tpm #tpm2

Related to the recent #LWN article: can Sequoia already all kernel maintainer workflows or not?

https://www.linkedin.com/posts/marklemley_i-have-struggled-with-how-to-respond-to-mark-activity-7284685204676362241-7h9r

It feels suboptimal that each fedi service requires a different account.

e.g. I have a Flohmarkt instance, which is different from my Mastodon instance. If I also ran a pixelfed instance, that would be a third account.

Rather than one "me", with different linked services.

Perhaps there is a need for a fedi directory service / "main" account, which people can use for discovering of sub-accounts?

(I can see that, for some users, separation of accounts will be valuable, so I wouldn't want to remove that ability.)

After trying bunch of things over the last few weeks I finally have a test program for feeding the data for a video loopback device, i.e. to work as fake webcam:

- Has zero dependencies other than libc. Draws the frames, converts the pixel formats and writes them to the device.
-.Has optional debug display using minifb.
- Predictable cyclic motion, which useful in future for automated testing.

Repository: https://codeberg.org/jarkko/v4l2-loopback-test/
BuildRoot package: https://codeberg.org/jarkko/linux-tpmdd-test/src/branch/main/package/v4l2-loopback-test

I've not been able to make any major changes to the driver I would like to do because it does not make much when being blind. Now it is finally possible to forget user space and move on to the kernel changes.

#linux #kernel #media #video4linux

https://bsky.app/profile/jarkk0.bsky.social/post/3lfgwtb6wns2n

The New Yorker has unveiled its Jan. 20 (Inauguration Day) cover. https://www.newyorker.com/culture/cover-story/cover-story-2025-01-20

Mad skills:

https://www.dropbox.com/scl/fo/200s1wx4b3df5uie9wxb9/AENl9GUXrx9zgR7OPjAmgi4?rlkey=p4bv768slmuldsemyx9kb9zcu&e=2&st=hj34wdc2&dl=0

"Quantum Soundtracker is a 3-channel sample-based tracker with 16 kHz mixing rate and internal 8-bit resolution." -user manual

For C64.

Demo song render to MP3:

https://www.dropbox.com/scl/fo/200s1wx4b3df5uie9wxb9/AENl9GUXrx9zgR7OPjAmgi4?dl=0&e=2&preview=No+Limit+(Quantum+Soundtracker+Demo).mp3&rlkey=p4bv768slmuldsemyx9kb9zcu&st=qmsfpmb4

o_O

Some people know what they are doing! The same guy is working also on a port of Elite. For VIC-20 (with memory expansion to 35 kB but still).

#commodore

Fedora Server Working Group has created a
10 question survey aimed at people who use #Fedora Server.

https://fedoraproject.limequery.com/fedora-server-f41

The goal here is to increase our knowledge of how people use the Server
offerings and what they do with it. In turn, this will help us priotise our efforts into areas that actually matter to our users.

Answering this survey will not take a lot of time, please consider helping us to help you with Fedora Server development.

https://www.bbc.com/news/articles/cgmy71rgreno

Here we go again... Audacity part two.

https://techcrunch.com/2025/01/09/vlc-tops-6-billion-downloads-previews-ai-generated-subtitles/

https://bsky.app/profile/brucerfeldman.bsky.social/post/3lfd4s5bf222g

https://bsky.app/profile/jarkk0.bsky.social/post/3lfesh3jvvk2c

This would be a great moment for Microsoft to express their love towards Linux and open source ;-)

https://bsky.app/profile/jarkk0.bsky.social/post/3lfe3m6ucxs2h

#microsoft #windows #opensource

"Kernel plumber at kernel.org. Uncloud plumber at parity.io."

I guess that is pretty accurate description what I do for the most part :-)