Hi!<br><br>I recently purchased a Genius TVGo DVB-T02Q, a usb dvb-t device<br><br> i found in this mail list that this device belongs to the m920x family. The <br>windows INF file makes reference to the m9207 chip, as frontends, someone
<br>pointed out in this mail list that it has got inside a Zarlink ZL10353 and <br>MT2060 chipsets, the windows INF file also makes reference to QT1010 and <br>MT352...<br><br>I took a patch i also located in this mail list, but had to modify it a bit to
<br>make it up-to-date with the current mercury m920x branch of the v4l-dvb <br>project,... after modification i applied this patch to m920.c file, i send <br>attached the modified m920.c file.<br><br>As a result i found out that the device is recognised by the system, as stated
<br>in the dmesg output:<br><br>[ 125.352000] usb 2-3: new high speed USB device using ehci_hcd and address 4<br>[ 125.496000] usb 2-3: configuration #1 chosen from 1 choice<br>[ 125.700000] dvb-usb: found a 'Genius TVGo DVB-T02Q' in cold state, will try
<br> to load a firmware<br>[ 125.808000] dvb-usb: downloading firmware from file 'dvb-usb-t02q-02.fw'<br>[ 125.812000] usbcore: registered new interface driver dvb_usb_m920x
<br><br><br>but the device did not work and the frontends were not loaded, here you are <br>the related modules automatically loaded when the usb device is connected.<br><br><br>Module Size Used by<br>dvb_usb_m920x 20484 0
<br>dvb_usb 24972 1 dvb_usb_m920x<br>dvb_core 80808 1 dvb_usb<br>dvb_pll 15620 1 dvb_usb<br><br>I think the patch only gets the device recognized but is not configured <br>properly to detect and load the frontends... if I unplug the devive the
<br>modules won't be removed<br><br>I'm wokring witha a 2.6.20-15 kernel in a kubuntu system.<br><br>I'm willing to make this device work and help in the m920x branch, i'm quite <br>newbie in programming and then i will need some indications on how to debuge
<br>to get more output from the code or how to try to 'communicate' with the <br>device (send it stuff and see what comes back).<br><br>If anyone else has got some experience with this device, every comment, <br>suggestion are very wellcome (appart of giving it back and buy a new
<br>one ;)... i'm very stubborn and won't stop trying untill i get this one <br>working)<br><br>cheers,<br>Pere Blay