https://bugs.kde.org/show_bug.cgi?id=365083
--- Comment #25 from Mauro Carvalho Chehab <mchehab+...@kernel.org> --- (In reply to Mauro Carvalho Chehab from comment #24) My comment #24 is incomplete. Hit enter by mistake, before finishing it... > 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 That solution require that the board detection and all DVB access to go via the library, as the library is responsible to route it to the local or remote hardware. This is incompatible with the hack added on libdvbv5 to support a proprietary DVB driver on userspace. -- You are receiving this mail because: You are watching all bug changes.
