didn't know about this module. Is it in upstream Linux? and if it is, is it for LTS kernel too? I don't have much time to do research for little issues like this one, sorry, if you could provide me more info it could help

i dont think that linux ever adopted it - it is a very mature project though, GPL-licensed, has been in major distros for many years, and is still actively maintained - the developer is on the debian multimedia team, and also the pure-data team, and a generally well-known person in the "nix audio" world

im not sure what other detail you would need - the README i linked to above has the build instructions - it doesnt necessarily need to be in the kernel modules package - it is a stand-alone package in other distros; and there is a PKGBUILD on the AUR with 39 votes - its mainly a matter of getting linux-libre to allow it to load

https://aur.archlinux.org/packages/v4l2loopback-dkms/

FWIW, i suppose i should mention what it actually does - it allows a video capture device (such as a webcam) to be accessed by more than one program at a time - normally, a single program will grab the device exclusively, blocking other programs from using it

bill-auger wrote:

FWIW, i suppose i should mention what it actually does - it allows a video capture device (such as a webcam) to be accessed by more than one program at a time - normally, a single program will grab the device exclusively, blocking other programs from using it

that sound very interesting

I was wondering if there is a particular reason it is excluded from linux-libre-lts kernel.

is it? and not in linux-libre? if it's a matter of the kernel config, remember that ours are based on Arch's configs, so please, indicate to me how to enable it

its mainly a matter of getting linux-libre to allow it to load

and how? you mean building it and bringing it to [pcr]? in that case anyone could do it

Sorry, maybe what I wrote was misleading. I assumed it was already included in the upstream and the only reason it is not on libre is because someone explicitly left it out. It sounds like this assumption is wrong given what bill-auger said. I will try the aur package.

it is not "excluded" from any kernel - AFAIK, linux-libre uses a
white-list to allow certain modules which it knows are fully-free
- any other module is implicitly excluded - i dont know how
exactly - you are "the kernel guy"

my guess is that linux-libre or you could add it to the
white-list very easily, then we would only need to maintain the
module package in [pcr]

bill-auger wrote:

it is not "excluded" from any kernel - AFAIK, linux-libre uses a
white-list to allow certain modules which it knows are fully-free
- any other module is implicitly excluded - i dont know how
exactly - you are "the kernel guy"

to my knowledge, it uses a "whitelist" for firmware, not kernel modules

my guess is that linux-libre or you could add it to the
white-list very easily, then we would only need to maintain the
module package in [pcr]

youwhy said he would test the AUR pkg. If he's successful, anyone can add it to [pcr]

AUR pkg actually worked. I just had to install linux-libre-lts-headers (presumably if you are using linux-libre kernel, you would need linux-libre-headers).

So, it seems like one of the dependencies depends on which kernel version you are using (as in lts or not). I don't know how to add such a conditional statement to PKGBUILD.

youwhy wrote:

AUR pkg actually worked. I just had to install linux-libre-lts-headers (presumably if you are using linux-libre kernel, you would need linux-libre-headers).

So, it seems like one of the dependencies depends on which kernel version you are using (as in lts or not). I don't know how to add such a conditional statement to PKGBUILD.

just look at other kernel modules in the abslibre, they generally specify the corresponding headers pkg in makedepends