Process specific ABI (psABI) specification can take dozens of pages in total. For RISC-V the spec has 95 pages. It is not ergonomic to print it all, so what to print out?

I usually print just the section enumerating the relocation's. It is the nastiest differentiatior and the part one is most likely continue to revisit forever after 🙂 For RISC-V that totals six pages.

Maybe less Nazi salutes would help with a more positive turn?

https://www.theverge.com/2025/1/24/24351317/elon-musk-x-twitter-bank-debt-stagnant-growth

A random pick from this years FOSDEM keynotes.

"What FLOSS Means in the AI World"

https://fosdem.org/2025/schedule/event/fosdem-2025-5495-what-floss-means-in-the-ai-world/

From description:

'"Mozilla has been doing extensive work in the AI ecosystem by defining a principled approach to AI that prioritizes transparency, ethics, and community-driven innovation."

Some highlights of Mozilla from the past year time window:

1. https://www.techradar.com/computing/cyber-security/mozilla-stands-by-its-controversial-privacy-feature-but-ready-to-clear-up-confusion
2. https://www.theverge.com/2020/8/11/21363424/mozilla-layoffs-quarter-staff-250-people-new-revenue-focus
3. https://www.theregister.com/2024/06/24/mozilla_product_chief_sues_over/
4. https://www.theregister.com/2024/06/18/mozilla_buys_anonym_betting_privacy/


Right but I get it. Mitchell Baker is only an employee with almost eight figure (in 2022 $7 000 000), not evil billionaire, and a true contributor to the open source.

This should highlight how hypocritical the campaign against Jack Dorsey has been.

I would not put high hopes on Mozilla's AI story TBH ;-) 🍿

I cannot even imagine what kind of "best of keynote speakers" list I could collect if I enumerated every keynote speaker from every FOSDEM ever organized...

#FOSDEM #Mozilla #JackDorsey #Keynote @fosdem @fosdem_countdown

OK sorry about FOSDEM rants. I just have zero-tolerance for hypocrisy.

I would get a position that "I don't want to visit OSS conferences because they are dominated by the evil corps AND Microsoft does not actually love Linux even tho they've made a marketing campaign that says so" ;-)

In this context I would get even protesting against Jack Dorsey...

#FOSDEM #hypocrisy

o_O

These people should spent some time AWAY from computer TBH.

As far as I'm concerned I never ever want to visit at FOSDEM. I hate when people are not absolutely sound in their moral and ethical values.

https://www.cnx-software.com/2025/01/18/jack-dorsey-talk-at-fosdem-2025-may-lead-to-protest/

That said my "protest" does not really count as I dislike tech conferences anyhow ;-) Just want to emphasize to ultimate stupidity in this whole matter.

Anyone involved with this ridiculous protest: you should be ashamed of yourself.

#fosdem #hypocrisy

In a conference where Microsoft, Google and Meta employees are giving talks, Jack Dorsey and Block Inc. is the prime evil :-)

#FOSDEM #hypocrisy

https://www.politico.com/news/2025/01/23/trump-staff-musk-conflict-00200311

A #vim thing that I tend to forget.

q: in normal mode gives you a buffer containing the history of ex command-lines for the sake of convenient copy-paste.

Does SDL 3.x do immediate mode GUI like for plugins and stuff? I.e. similarly as egui and imgui (with appropriate backends)?

#libsdl #sdl

how an interns attempts to familiarize themselves with a codebase, and spice up the comments resulting in finding a major security vulnerability. Via Reddit, via 🤷‍♀️

One more existential reason for v4l2-loopback: testing video4linux features other than v4l2-loopback.

It is always nice to have a module in the stack that can pretend to be a piece of hardware in various end-to-end tests.

Just writing these down so that I can make a credible cover letter at the time :-)

I did this one big refactor few days ago: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?h=v4l2-loopback&id=ccb1b6e1247887be17bf22b3809c50848e87a4db

I'm still editing it up until I'm happy with capture/output separation and some other things related (e.g. life-cycle and removal).

Obviously once I sent a patch set I will squash everything before sending...

#video4linux #linux #kernel #media

Designing Custom #Linux Schedulers with sched_ext – slides and the recording of yesterdays #LinuxFoundation Mentorship session from @arighi are now online:

https://www.linuxfoundation.org/webinars/designing-custom-linux-schedulers-with-sched_ext

Direct link to the slides: https://events.linuxfoundation.org/wp-content/uploads/2025/01/Andrea-Righi-Mentorship-1_22_25-scx.pdf

Direct link to the recording: https://www.youtube.com/watch?v=jsLjg9tGuVI

#Kernel #LinuxKernel

With these I wonder "why even bother" o_O

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