Conversation
Jarkko Sakkinen
jarkko
Edited yesterday
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
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
0