Talk about kmscon at FOSDEM 2024
This upcoming Sunday, 4th of February 2024, I will be talking about my patches to kmscon at FOSDEM 2024. The slot for the talk is allocated in the graphics dev-room between 15:05 – 15:30. Here is the direct link to it: “Scratching an itch… by patching kmscon” or “How OpenGL can lead to systems-programming”.
If you attend FOSDEM 2024 this weekend and are curious about all the shenanigans I did (or plan to do) to kmscon, be sure to stick around the graphics dev-room.
This looks awesome! Thanks for all the hard work you put into it. Any chance it will get merged upstream?
I am about to go figure out if I can grab your forked code to build it on NixOS.which packages against:
stdenv.mkDerivation rec {
pname = “kmscon”;
version = “9.0.0”;
src = fetchFromGitHub {
owner = “Aetf”;
repo = “kmscon”;
rev = “v${version}”;
sha256 = “sha256-8owyyzCrZVbWXcCR+RA+m0MOrdzW+efI+rIMWEVEZ1o=”;
};
patches = [
(fetchpatch {
name = “0001-tests-fix-warnings.patch”;
url = “https://github.com/Aetf/kmscon/commit/b65f4269b03de580923ab390bde795e7956b633f.patch”;
sha256 = “sha256-ngflPwmNMM/2JzhV+hHiH3efQyoSULfqEywzWox9iAQ=”;
})
];
See:
https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/os-specific/linux/kmscon/default.nix#L81
https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/services/ttys/kmscon.nix
Looks like I should be able to apply your branches as patches. Mouse, Rotation, Gyro, Shader.
Greetings Matthew!
In terms of build- and runtime-dependencies, I only added dbus. Since that’s a core system-library, there should be no major issues I assume. Having said that, I do not know anything about packaging on NixOS, thus I cannot help out there should any issues arise.
The shader-branch I would avoid. That was just me messing around. It is really not meant for general consumption. Since it is busy-looping in be background for the realtime-animation, it’s very ‘hostile’ to laptop-batteries 🙂
For what it’s worth… I managed to get my patched kmscon compiled and packaged on fedora, debian and ubuntu. The changes I had to do to the regular kmscon-package were minor. I expect something similar for other modern distros.
Regarding the acceptance of my changes upstream… I have no idea. I wrote them on github, I held a talk about it this year at FOSDEM in Brussels… no feedback yet at all. Only a debian-maintainer once got back to me. But he has no upload-permissions for ‘upstream’ kmscon. BTW, I also once came across some arch-forums, where some people seem to have taken note of my patches… they might have packaged my stuff as distro-patches or something similar.
From my point of view the original upstream ‘kmscon’ (https://github.com/dvdhrm/kmscon) and the newer ‘de facto’ upstream-fork (https://github.com/aetf/kmscon) are dead. I might be forced to roll my own fork, which is a thing I tend to avoid. It’s not like I am eager to take on maintainer-ship of something
Best regards…
MacSlow