A few choices:
2) My patch found it's way into media_tree just a couple of days ago: media_tree.git - Upstream media tree for Remote Controllers, V4L and DVB so you could to build and install the drivers yourself from media_tree to run within your existing kernel: https://www.linuxtv.org/wiki/index.php/how_to_obtain,_build_and_install_v4l-dvb_device_drivers
3) (If both above options are too scary), then wait until the patch filters it's way down to mainstream raspbian kernel.
Thanks for that, and for your patch
Option 3 is the easy way out, but until the patch makes it to the Raspbian Kernel, I'm stuck with a non-working device. Who know how long I'll have to wait...
Previously, my DVBSky adapters were attached to a VM running Debian.
AFAIK the kernel I was using there doesn't include the DVSKy drivers, so I had to built my own drivers.
So, I should be able to get option 2 working.
I hadn't noticed yet that the patch made it to the media tree.
The Raspberry does kernel include the drivers. Wil the driver that I build myself overrule the supplied one?
I suppose it will ...
Option 1 sounds more scary, as I haven't done anything like that before. But, I am willing to give it a try. Probably this is the option where I can learn the most
Since I have 3 rpi + dvbsky, I think I'll fix 2 of them with new drivers and use the 3rd one to experiment with the kernel.