Hi Istvan, istvan_v@xxxxxxxxxx wrote: > The attached new patches contain all the previous changes merged, and > are against the latest v4l-dvb revision. Please provide your Signed-off-by. This is a basic requirement for your driver to be accepted. Please read: http://linuxtv.org/hg/v4l-dvb/raw-file/tip/README.patches for instructions on how to submit a patch. Cheers, Mauro. > > By the way, someone on a forum reported having a DTV1800 H card with > a PCI ID of 107d:6f38. This seems to differ from the already supported > DTV1800 H version (107d:6654) by having an XC4000 tuner instead of > XC3028. From the Windows INF files it seems this card is very similar > to the DTV2000 H Plus, but there is no GPIO for selecting antenna/cable > input. > > On 02/11/2010 08:16 PM, istvan_v@xxxxxxxxxx wrote: > >> Update: the following patch, which should be applied after the previous >> ones, makes a few additional changes to the XC4000 driver: >> - adds support for DTV7 >> - implements power management >> - adds a mutex and locking for tuner operations >> - some unused or unneeded code has been removed >> >> On 02/09/2010 06:35 PM, istvan_v@xxxxxxxxxx wrote: >> >>> There are two separate patches for v4l-dvb revision 28f5eca12bb0: the >>> first one adds the XC4000 driver, while the second one adds support for >>> the Leadtek WinFast DTV2000H Plus card in the CX88 driver. >>> >>> http://www.sharemation.com/IstvanV/v4l/xc4000-28f5eca12bb0.patch >>> http://www.sharemation.com/IstvanV/v4l/cx88-dtv2000h+-28f5eca12bb0.patch >>> >>> These new firmware files are more complete than the previous ones, but >>> are not compatible with the original driver. Both version 1.2 and 1.4 >>> are available: >>> >>> http://www.sharemation.com/IstvanV/v4l/xc4000-1.2.fw >>> http://www.sharemation.com/IstvanV/v4l/xc4000-1.4.fw >>> >>> The following simple utility was used for creating the firmware files. >>> >>> http://www.sharemation.com/IstvanV/v4l/xc4000fw.c -- Cheers, 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
