Re: Use /dev/swradioN (v4l2 api) as source

2022-06-14 Thread Stefan Oltmanns
Franco, as far as I understand this, the libraries like libmirisdr and librtlsdr do not use the v4l2 kernel driver at all, they use libusb to connect to the devices and the driver is implemented in user-space. I looked into the v4l2 documentation and the example fm radio, it's not exactly easy to

Re: Use /dev/swradioN (v4l2 api) as source

2022-06-13 Thread Franco VENTURI
Stefan, if I were you I would contact the author of that SoapyMiri driver on GitHub about your problems with it, since to me he seems interested in improving it and he probably would be able to run some tests on his setup to troubleshoot and fix those issues. As per my comment about using the k

Re: Use /dev/swradioN (v4l2 api) as source

2022-06-13 Thread Stefan Oltmanns
Thank you very much for that information, haven't seen that somebody continued the work on libmirisdr. I was able to get it working with an OsmoSDR Source using soapy=0,driver=soapyMiri I had to modify the SoapyMiri driver, as OsmoSDR sets the bandwidth to 3/4 of the sample rate, but there are on

Re: Use /dev/swradioN (v4l2 api) as source

2022-06-13 Thread Chris Vine
On Mon, 13 Jun 2022 21:26:34 +0200 Stefan Oltmanns wrote: > Hello, > > is there any way to use devices exposed as /dev/swradioN by the v4l2 > Linux kernel API with GNURadio directly? > > At the moment there are only two in-tree kernel drivers, one for the > RTL2832U and the other for the Mirics

Re: Use /dev/swradioN (v4l2 api) as source

2022-06-13 Thread Franco VENTURI
Stefan, instead of using the kernel API directly you may want to look into a SoapySDR source in GNU Radio, since the SoapySDR block is now a first class citizen in GNU Radio 3.9/3.10 According to this recent discussion in the SoapySDR GitHub repository (https://github.com/pothosware/SoapySDR/is