Jarkko Sakkinen
Posts
4937Following
327Followers
492OpenPGP: 3AB05486C7752FE1
Jarkko Sakkinen
jarkko
@Aissen Looking at existing code base for the loopback driver, I'd find any excuse not to review it because it would be too much work to tell all the details "what needs to be done".
So I believe that once there is a cleaner driver and easy to run test program, and legit use NON-PROPRIETARY use cases clearly explained, also maintainers give less hate :-) And today companies have started to anyway prefer in-tree drivers more, as it is just plain more practical and cheaper over long period of time. We are big enough, and your proprietary crap will be made obsolete by competitors.
So I believe that once there is a cleaner driver and easy to run test program, and legit use NON-PROPRIETARY use cases clearly explained, also maintainers give less hate :-) And today companies have started to anyway prefer in-tree drivers more, as it is just plain more practical and cheaper over long period of time. We are big enough, and your proprietary crap will be made obsolete by competitors.
1
0
1
@Aissen lol and at least FSF does not have a campaign against this ;-) I don't get how they still today campaign against TPM. https://www.defectivebydesign.org/dayagainstdrm
1
0
1
Jarkko Sakkinen
jarkko
@Aissen It's really a project where 80% is doing other than kernel code and 20% is the kernel challenge. I pretty much know how to do the API shift but I need to finish up this test program first :-) We have done something quite close e.g. in tpm_vtpm_proxy.
And yeah, it's like the meat is great but it is surrounded by a broken framework so you need to do small steps and run the test for every single iteration. It's too easy otherwise to look at a piece of code and decide that it is crap and remove something actually relevant :-)
And yeah, it's like the meat is great but it is surrounded by a broken framework so you need to do small steps and run the test for every single iteration. It's too easy otherwise to look at a piece of code and decide that it is crap and remove something actually relevant :-)
1
0
1
@Aissen there's libcamera and pipewire etc. but what people actually use is a tainted driver ;-) in their work machines. i don't really fully believe that proprietary driver story in 2024 given how many things you can anyway do in user space so not stopping based on this doing a RFC patch TBH (if that was the recommendation).
1
0
1
Jarkko Sakkinen
jarkko
@Aissen it is based on that fixes up the device model https://social.kernel.org/notice/ApXBpAVuAyGBmcPye8
1
0
0
Jarkko Sakkinen
jarkko
Great found the most suitable crate for my test program:
https://github.com/zesterer/euc
I.e. I can pre-render the frame to buffers and then loop those frames to "cast_fd" with a given FPS (25) so it should be fairly timing accurate.
Using rotating and shaded torus I have cyclic movement which the other side (opening /dev/video0) can then read and store a full cycle of the animation.
Client and server can be two threads in the same process, and as final step the client can compare that the read frames are close proximity enough to the pre-rendered frames.
That should create a full headless and "CI friendly" system test for v4l2-cast. Definitely still hold a bit before doing too heavy refactoring and make this happen!
I wonder can we already have Rust programs in kselftest's? My driver is in C but this could be potentially part of the kselftest (at some point).
#linux #kernel #video4linux
https://github.com/zesterer/euc
I.e. I can pre-render the frame to buffers and then loop those frames to "cast_fd" with a given FPS (25) so it should be fairly timing accurate.
Using rotating and shaded torus I have cyclic movement which the other side (opening /dev/video0) can then read and store a full cycle of the animation.
Client and server can be two threads in the same process, and as final step the client can compare that the read frames are close proximity enough to the pre-rendered frames.
That should create a full headless and "CI friendly" system test for v4l2-cast. Definitely still hold a bit before doing too heavy refactoring and make this happen!
I wonder can we already have Rust programs in kselftest's? My driver is in C but this could be potentially part of the kselftest (at some point).
#linux #kernel #video4linux
2
1
2
@mjg59 have not read this nonsense about TPM's for some time. picking up the old classics i suppose... and ignores the fact that TPM is more like a protocol than a piece of hardware. that would be a proprietary hell if everyone had (like Apple) their own TPM alike incompatible chips.
0
0
0
Jarkko Sakkinen
repeated
repeated
Matthew Garrett
mjg59@nondeterministic.computer"Today, most of the major streaming media platforms utilize the TPM to decrypt media streams, forcefully placing the decryption out of the user's control." (from https://www.defectivebydesign.org/dayagainstdrm) I… just… what? This isn't even slightly true. There's plenty of good reasons to object to Microsoft imposing hardware requirements on Windows 11 that aren't strictly required, but *nobody* is doing media decryption on a TPM because TPMs are nowhere near fast enough to do that
4
7
0
Jarkko Sakkinen
repeated
repeated
Jarkko Sakkinen
jarkko
@nogodsnomasters So. I spent ages paying mortgage loan for my small apartment, and if I move away and rent I am "stealing my tenant's labor value"?
It is investment income and there is nothing wrong in that.
It is investment income and there is nothing wrong in that.
0
1
0
Jarkko Sakkinen
jarkko
Edited 10 months ago
I will name my driver as "v4l2-cast". The ioctl will return the file descriptor with the field name "cast_fd".
Feels Platonic sense the best possible name, i.e. you have video capture and video cast devices.
It is more like user space video capture driver than loopback/proxy device. And we have too many things already named as "proxy" or "loopback". They are as descriptive if I named this as v4l2-object or v4l2-instance IMHO. From "cast" you get immediately a gist what is going on and like the use and purpose.
Feels Platonic sense the best possible name, i.e. you have video capture and video cast devices.
It is more like user space video capture driver than loopback/proxy device. And we have too many things already named as "proxy" or "loopback". They are as descriptive if I named this as v4l2-object or v4l2-instance IMHO. From "cast" you get immediately a gist what is going on and like the use and purpose.
0
1
0