Vero does support most Linux tuners, but all of them will require an element of setup due to how scanning for TV channels works! Without access to everyone of these sticks however, universal support is tricky.
That said, without having one, this would probably work:
Get OSMC build tools
sudo apt-get install build-essential git
Get Vero kernel headers
set -- $(cat /proc/cmdline) && for x in "$@"; do case "$x" in osmcdev=*) sudo apt-get update && sudo apt-get install -y "${x#osmcdev=}-headers-$(uname -r)"; ;; esac; done
Get V4L and build it
git clone --depth=1 git://linuxtv.org/media_build.git
cd media_build
./build
sudo make install
sam thanks for the reply, this seems very similar to what I had tried (but not exactly the --depth bit I know I didnt try) so ill try it out again and let you know
cheers pete
@sam_nazarko seems we were on the same path Im back at the point I got stuck on last time trying a full build
so I had to install these
sudo apt-get install patch patchutils
sudo apt-get install libproc-processtable-perl
then after headers installed had to do this:
cd lib/modules/3.14.14-7-osmc
sudo ln -s /usr/src/vero-headers-3.14.14-7-osmc/ build
and then get ths error:
/usr/src/vero-headers-3.14.14-7-osmc/arch/arm/include/asm/io.h:305:0: note: this is the location of the previous definition
#define writel_relaxed(v,c) __raw_writel((__force u32) cpu_to_le32(v),c)
^
CC [M] /home/osmc/media_build/v4l/flexcop-pci.o
In file included from <command-line>:0:0:
/home/osmc/media_build/v4l/compat.h:1563:0: warning: "writel_relaxed" redefined
#define writel_relaxed writel
^
In file included from include/linux/io.h:22:0,
from include/linux/pci.h:31,
from /home/osmc/media_build/v4l/compat.h:1454,
from <command-line>:0:
/usr/src/vero-headers-3.14.14-7-osmc/arch/arm/include/asm/io.h:305:0: note: this is the location of the previous definition
#define writel_relaxed(v,c) __raw_writel((__force u32) cpu_to_le32(v),c)
^
/home/osmc/media_build/v4l/flexcop-pci.c: In function 'flexcop_pci_write_ibi_reg':
/home/osmc/media_build/v4l/flexcop-pci.c:100:2: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
writel(v.raw, fc_pci->io_mem + r);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:308: recipe for target '/home/osmc/media_build/v4l/flexcop-pci.o' failed
make[3]: *** [/home/osmc/media_build/v4l/flexcop-pci.o] Error 1
Makefile:1274: recipe for target '_module_/home/osmc/media_build/v4l' failed
make[2]: *** [_module_/home/osmc/media_build/v4l] Error 2
make[2]: Leaving directory '/usr/src/vero-headers-3.14.14-7-osmc'
Makefile:51: recipe for target 'default' failed
make[1]: *** [default] Error 2
make[1]: Leaving directory '/home/osmc/media_build/v4l'
Makefile:26: recipe for target 'all' failed
make: *** [all] Error 2
build failed at ./build line 491.
osmc@osmc:~/media_build$
I can disable that module in the .config file under v4l folder but the there is another that will fail in the same or similar way and they seem to just keep coming and coming ?
@sam_nazarko, I think with the concept of the Vero, uses shouldn’t really be the ones going through all this hassles to get the tuner working. Also from research, this tuner seems to be one the best option for UK viewers wanting HD, it could also serve as a selling point that it works out of the box with specific tuners with HD capabilities. I will suggest making this work by default for Vero, Im almost certain, alot of buyers of Vero will have a very similar issue sometime in the future. By my estimation most users who eventually buy the Vero and want so TV experience will end up buying this tuner, as its probably the best option for now.
The amount of TV tuners out there: insurmountable. We do support quite a few as is out of the box, but we can’t support all of them.
Vero is very new, and supporting TV dongles will come in time, but we won’t have the resources to support all of them.
When working on Vero we considered adding a TV tuner to the device, but again, one size does not fit all. Some will want DVB-S and some will want DVB-T…
@phate1, by the way -Werror=implicit-function-declaration is not really an error, it is a warning turned to error. If you look for a file called Makefile in the directory, and remove the -Werror=implicit-function-declaration option, it will compile just fine and the tuner should work.
I’ll add kernel support for this if it’s cleanly backportable. I am sure the 292e can work with Vero ‘out of the box’
sed -i 's/\-Werror-implicit-function-declaration/ /g' .*.cmd
and re-run the grep command and I get no more hits, figure the ./build would re write them so just use make … but fails the same and i find all those files have the same -Werror-implicit-function-declaration again
sdev->gpio_reset = devm_gpiod_get_optional(&client->dev, "reset",
^
/home/osmc/media_build/v4l/si4713.c:1463:10: error: 'GPIOD_OUT_LOW' undeclared (first use in this function)
GPIOD_OUT_LOW);
^
/home/osmc/media_build/v4l/si4713.c:1463:10: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:314: recipe for target '/home/osmc/media_build/v4l/si4713.o' failed
make[3]: *** [/home/osmc/media_build/v4l/si4713.o] Error 1
Makefile:1273: recipe for target '_module_/home/osmc/media_build/v4l' failed
make[2]: *** [_module_/home/osmc/media_build/v4l] Error 2
make[2]: Leaving directory '/usr/src/vero-headers-3.14.14-7-osmc'
Makefile:51: recipe for target 'default' failed
make[1]: *** [default] Error 2
make[1]: Leaving directory '/home/osmc/media_build/v4l'
Makefile:26: recipe for target 'all' failed
make: *** [all] Error 2
build failed at ./build line 491.
osmc@osmc:~/media_build$
appreciate you keep coming back to this, must be close now
I think we are just looking to get the most popular UK HD version supported which you and @phate1 seem to be making headway on. As it’s been mentioned already this would be a selling point for Vero/OSMC.
I like the idea of Suntek cards. They don’t rely on a kernel module (independent of kernel) and so this gives them a bit more resilience and probably better support in the long run.
@phate1: looks like missing kernel config option. Will investigate post-RC2
That is a beast, and Sundtek sent me one to get working with OSMC… I’ll dig it up (probably in a cupboard somewhere). Can let you know how DVB-S2 satellite works
It looks like we will be moving Vero to a more modern kernel (3.19 or 4.0) in the near future, so we will gain a lot of tuner support as a result of that.
