[linux-dvb] Support for newest DVICO Fusion HDTV Dual Express

Michael Krufky mkrufky at linuxtv.org
Mon Oct 15 14:15:31 CEST 2007


Michael Krufky wrote:

>Patrick Claven wrote:
>  
>
>>Hi people,
>>
>>I've got the latest DVICO Fusion HDTV Dual Express. From what I have  
>>gathered thus far, it has a Conexant cx23885 chipset and an xceive   
>>xc30xx chipset.
>>
>>I'm not sure whether it would work with the xc3028 driver, i have  
>>loaded the xc3028-fe patched module as according to steps outlined  
>>here: http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4- 
>>under-linux but it has no effect.
>>
>>I actually have the dual digital 4 card referred to in that article  
>>running perfectly, but I'm not so naive as to think that my new card  
>>which is PCIe 1x will work, especially given the fact that I think  
>>it's a newer xceive chipset than
>>that in the dual digital 4.
>>
>>I compiled the very latest v4l-dvb and got the cx23885 module loaded,  
>>it detects the card as an unknown type, as shown in the following  
>>dmesg output:
>>
>>[ 5980.021706] cx23885 driver version 0.0.1 loaded
>>[ 5980.021770] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 19 (level,  
>>low) -> IRQ 17
>>[ 5980.021774] cx23885[0]: Your board isn't known (yet) to the  
>>driver.  You can
>>[ 5980.021776] cx23885[0]: try to pick one of the existing card  
>>configs via
>>[ 5980.021777] cx23885[0]: card=<n> insmod option.  Updating to the  
>>latest
>>[ 5980.021778] cx23885[0]: version might help as well.
>>[ 5980.021780] cx23885[0]: Here is a list of valid choices for the  
>>card=<n> insmod option:
>>[ 5980.021782] cx23885[0]:    card=0 -> UNKNOWN/GENERIC
>>[ 5980.021784] cx23885[0]:    card=1 -> Hauppauge WinTV-HVR1800lp
>>[ 5980.021786] cx23885[0]:    card=2 -> Hauppauge WinTV-HVR1800
>>[ 5980.021788] cx23885[0]:    card=3 -> Hauppauge WinTV-HVR1250
>>[ 5980.021789] cx23885[0]:    card=4 -> DViCO FusionHDTV5 Express
>>[ 5980.021798] CORE cx23885[0]: subsystem: 18ac:db78, board: UNKNOWN/ 
>>GENERIC [card=0,autodetected]
>>[ 5980.120888] cx23885[0]: i2c bus 0 registered
>>[ 5980.120905] cx23885[0]: i2c bus 1 registered
>>[ 5980.120919] cx23885[0]: i2c bus 2 registered
>>[ 5980.147782] cx23885[0]/0: found at 0000:03:00.0, rev: 2, irq: 17,  
>>latency: 0, mmio: 0xfd800000
>>[ 5980.147801] PCI: Setting latency timer of device 0000:03:00.0 to 64
>>[ 6178.439162] Linux video capture interface: v2.00
>>[ 6178.531298] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
>>[ 6279.216926] usbcore: registered new interface driver dvb_usb_cxusb
>>
>>Okay, so if I tell it that its card number 4, it registers the dvb  
>>adapter0 in /dev/dvb/adapter0 and so forth. However it loads the LG  
>>tuner chipset that ships with the HDTV5 Express card, so we  
>>definitely know that won't work.
>>
>>So to cut a long story short, reading the xceive chipset on the card  
>>it appears to say xc3008ACQ. This may not mean much to anybody, it  
>>doesnt to me. So realising this card does not have support under  
>>linux yet, I primarily would
>>like to volunteer for testing of this card for anybody brave enough  
>>to endeavour to get this working.
>>
>>Thanks a lot, and I hope some of this made sense. This is the first  
>>time I've posted to any mailing list.
>>    
>>
>
>Patrick-
>
>I can post a test patch for you, within the next few days.  Which demod is used on that card?  Is it two zl10353's ?
>
>Can you show me the output of 'modprobe cx23885 i2c_scan=1' , after first doing 'modprobe -r cx23885' ?
>
UPDATE:

Patrick has the DViCO FusionHDTV Express DVB-T Dual Pro, which uses the 
same configuration as the DVB-T NANO, and the DD4, but using the CX23885 
PCI Bridge.  It's safe to assume that it uses the zl10353 demod, 
although we'll be screwed if DViCO went for the newer Intel version of 
that part.  (I've yet to see the zl10353 linux driver work for the Intel 
part)

%Zulu885.DvbtDualPro%      =  Zulu885.DvbtDualPro,  
PCI\VEN_14F1&DEV_8852&SUBSYS_DB7818AC

I'll work on a xc-zulu885.patch this week, which will depend on my 
xc-bluebird.patch, so you can test it.  In the meanwhile, the i2c_scan 
output will be helpful, so that I can determine which i2c bus I can 
expect to find the tuner hardware.

Regards,

Mike




More information about the linux-dvb mailing list