https://bugs.kde.org/show_bug.cgi?id=365083
--- Comment #24 from Mauro Carvalho Chehab <mchehab+...@kernel.org> --- (In reply to Mauro Carvalho Chehab from comment #3) > (In reply to Jonathan Riddell from comment #1) > > <mchehab> also, the hack to support mrec's devices will soon not work with > > newer versions of Kaffeine, as I'm planning to rely on some new methods at > > libdvbv5 > > My plans for the next Kaffeine version is to move all access to the hardware > to libdvbv5. It means that device notification will come from the library, > and the library will only work with the devices it knows, as, for local > devices, it will rely on udev to get the device name (as they can be changed > via udev rules). This is meant to fix a long-standing issue on Kaffeine > that got broken on version 1.0.0, related to dtvdaemon support. That's why > we can't add device-specific hacks at the Kaffeine's code. Once such changes > were merged in Kaffeine, it shouldn't be hard for a vendor that doesn't > provide open source drivers to develop other ways to integrate with libdvbv5 > that won't require touching at the Kaffeine nor at the library code. As people pinged me on IRC about this BZ, let me write a better explanation about why this patch won't be applied. Kaffeine 0.x had a feature of allowing to watch Digital TV with Kaffeine on a hardware without Digital TV hardware. That was done by accessing a remote Kaffeine instance connected to the hardware. At Qt4 rework (Kaffeine 1.x), this feature got removed, and a prototype for a feature with a similar function was written, at the dtvdaemon/ directory. Such feature is important, as it would allow someone to have cheap boards like Raspberry PI connected to DVB boards, allowing multiple computers to use the DVB hardware to watch TV. It would also allow using old PC hardware with PCI digital TV boards to provide digital TV streams to modern PC hardware (that's actually my main usecase: I have a very slow hardware with I use to test Kernel support for old PCI hardware). I tried to play with Kaffeine's dtvdaemon code for a while, in order to extend to a functional code, on an experimental branch (not pushed upstream): https://git.linuxtv.org/mchehab/kaffeine.git/log/?h=dtvdaemon Using dtvdaemon approach, each function at src/dvb/dvbcam_linux.cpp would need to be mapped into two TCP/IP messages (message, message reply) and a few ones also on a notify message. It would also require a complex change at dvbcam_linux, in order to use this code. For development purposes, a text mode application would also be required, in order to check if the API calls are working: So, I came with another solution, with is a lot simpler: to implement this feature directly at libdvbv5 library, and have a daemon non-GUI application, running on the machine. As it depends only on libc, it is easier to build it on SoC hardware, like RPi. It also brings another advantage over dtvdaemon. With dtvdaemon, I had to write a non-GUI code to test the TCP/IP protocol during its development. Adding it via libdvbv5, there's no need for that, as the same tools there (dvbv5-zap, dvbv5-scan, dvb-fe-tool) can easily be modified to use a remote hardware. The daemon code is at: https://git.linuxtv.org/v4l-utils.git/tree/utils/dvb/dvbv5-daemon.c -- You are receiving this mail because: You are watching all bug changes.
