Em 24-01-2012 16:30, Lars Hanisch escreveu: > Hi, > > Am 24.01.2012 14:01, schrieb Mauro Carvalho Chehab: > [...] >>> That would be awesome to have this functionality in the kernel. I maintained the "unicable"-patch for the vdr (written by some guy from the vdr-portal.de who sadly doesn't seem to respond to mails via that forum anymore). >>> It would be great if all the work could be summarized in one ioctl. >> >> I don't think that SCR/Unicable, bandstacking, LNBf settings, rotor >> control, etc. should belong to the Kernel. There are too many variants, >> and several of them are not properly standardized or properly implemented. >> Also, the actual options to use will depend on what type of DiSEqC components >> used on his particular setup. So, it would be very difficult to write >> something at the Kernel that will fit in all cases. >> >> What the Kernel should support is the capability of sending/receiving DiSEqC >> commands, allowing userspace libraries to do the job of setting it. Such >> feature is already there, so there's no need to change anything there. >> >> That's said, I'm working on a library to be used by applications that want >> to talk with DVB devices. Together, with the library, there are a scanning >> tool and a zapping tool. >> >> So, inspired by this patch, and using a public tech note about SCR/Unicable [1], >> I wrote an Unicable patch for such library: >> >> http://git.linuxtv.org/v4l-utils.git/commit/6c2c00ed3722465ed781ad49567e34dc7a5f92e7 >> >> I'm currently without DVB-S/DVB-S2 antennas, so, I was not able to test it. >> >> It would be very nice if you could help us by testing if those tools are >> working with DVB-S with SCR, and, if not, help fixing its support. > > Maybe the absence of a good libdvb lead to such patches as the SCR-patch. Yes, that's my opinion too. That's one of the reasons why I'm writing it, even for hardware that I can't test. I even added an option to read and write from a few commonly used file formats. > I understand why such functionality should not be in the kernel. Hopefully the > libdvb will combine all nice features for dvb hardware so no application has to build > its own implementations. Another advantage will be that there will be only one place > where to configure your hardware setup (like SCR, "use only specific delivery system > of hybrid cards" etc.). Yes. Currently, I think that there are very few things missing there. The only two I'm aware of are: - DiSEqC rotor control; - SCR auto-discovery, for bi-directional DiSEqC hardware; - ATSC-specific tables parsing (for libscan); - DVB-S2 non-emulated-mode descriptor. > I myself have only DVB-C but I know someone with a SCR-setup and will try to convince him to test this. Thank you! Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
