Conversation

Jarkko Sakkinen

Edited 2 days ago
I think vcam driver is almost ready for RFC submission. It is a dual-VB2 queue architecture and intermediator that moves frames between the queues. Flow can be either based on copying or shared DMA-BUF's and memory allocation can be either vmalloc or dma-sg based.

Right now VCAM_IOC_CREATE locks in "physical characteristics" of the device. It might be nice to be able to change them without re-creating the device but this is *purposely* left out as nothing prevents extending uAPI that way later on.

SLOC is now varying between 2-2.5 KSLOC, which "feels" about right for me considering complexity of the flow etc.

I'll hold for a week so that I discover low-hanging stupid stuff and send it late next week.
2
1
0

Jarkko Sakkinen

Edited 2 days ago
Implementation was really done by starting with v4l2-loopback year ago and unwriting/re-writing everything piece by piece (there was almost year break between "sprints" tho). Right now there is not much left of the original driver.
0
0
1
@jani This was somewhat exhausting mind-bending I have to say to deconstruct and reconstruct brick by brick :-) I'm so glad this was not a complete failure. The topic is alien enough for me that I could not really project the outcome without trying to do it.
0
0
1