Posts
4106
Following
280
Followers
428
Software Engineer at Opinsys Oy (starting 03/2025)
Entrepreneur at Siltakatu Solutions Oy

OpenPGP: 3AB05486C7752FE1

Jarkko Sakkinen

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.

0
0
4
There's enough AAA titles in Steam for instance to keep SDL alive in foreseeable future. It's way too big ecosystem to die.
0
0
2
Just interested. Even with Rust it would be a great solution in many cases, as it has the "long-term solution" benefit. Many other libraries come and go.
1
0
2

Jarkko Sakkinen

Edited 1 month ago
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
1
0
2
@phoenix the sponsor list for this year.

It's total hypocrisy and nonsense to complain about Jack Dorsey giving a keynote and this *objectively* proves it. Get a life.
0
0
0
@phoenix There's every single year employees of Meta, Google and Microsoft giving talks at FOSDEM. Why do you allow that to happen? :-)
1
0
0

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 🤷‍♀️

4
10
1

Jarkko Sakkinen

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
0
2
1
@oleksandr ya, in kernel email service we trust
0
0
0

Jarkko Sakkinen

With these I wonder "why even bother" o_O
1
0
1
Personally I think that it would make a lot of sense to have this type of meta-data in DNS attributes. I.e. some means to say that this IP is a blockchain node and the type of the blockchain. Not much else but it could help a lot with low cost.
0
0
0

Jarkko Sakkinen

Edited 1 month ago
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.
1
0
0
@cesarb @pid_eins Also even if all those procedure were taken care of (rescue password locked into PCR's), I would never use a computer, which has been physically compromised. A physical compromise is a game over as far as I'm concerned, and TPM's work best against software attacks :-) That has been the driving design goal in the standard.
0
0
0
@cesarb @pid_eins For my home desktop I would never lock password into the PCR's, i.e. that really should be a choice. Depends on deployment really.
1
0
0
@ljrk @pid_eins Thanks for all the feedback on this (from everyone who comments, all comments were useful).

I posted this mainly because could not get the gist, and was wondering do I have some blind spot here, that's all.

There's like a drum roll but no drop...
0
0
1
@pid_eins This was circling around social media, I read it 3~ times, and could not catch the dragon tail...

The only thing I also did catch was that "PCR 7 locking is unsafe", which is obviously dead obvious, so I guess this is noise about nothing then :-)
0
0
0

Jarkko Sakkinen

Edited 1 month ago
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
0
2
1
Show older