G'day Daniel, On Mon, Jun 18, 2007 at 09:30:29PM +0200, Daniel Weigl wrote: > If i set the USB_PID_MSI_DIGI_VOX_MINI_II to 0x0506 i get following dmesg: > [ 340.530811] usb 6-3: new high speed USB device using ehci_hcd and > address 8 > [ 340.645215] PM: Adding info for usb:6-3 > [ 340.645315] PM: Adding info for No Bus:usbdev6.8_ep00 > [ 340.645345] usb 6-3: configuration #1 chosen from 1 choice > [ 340.645456] PM: Adding info for usb:6-3:1.0 > [ 340.645548] PM: Adding info for No Bus:usbdev6.8 > [ 340.705639] dvb-usb: found a 'MSI DIGI VOX mini II DVB-T USB2.0' in > warm state. Warm state ... no firmware download required (well, not right now anyway). > [ 342.724107] dvb-usb: no frontend was attached by 'MSI DIGI VOX mini II > DVB-T USB2.0' Oh well, I was just hoping your device would have the same tuner/demodulator config as one of the supported devices. Since it evidently does not, you will need to do some work to find out what it does have. Are you able to open it up and find out what chips are inside? > In case of "define USB_PID_LIFEVIEW_TV_WALKER_TWIN_COLD 0x0506" the > cpu-load goes up for about 30 seconds, but i was unable to get the dmesg, > bec. my keyboard somehow get locked (no response on any keypress, even > numlock was disfunct). Time to stop playing now I think. Next step is to open it up and look what chips it uses, and/or do lots of windows usb traces to find the i2c bus addresses of those chips. > I have done a first quick dvb-snoop on Windows XP (running in a VMWare). > The log contains the plugin of the COLD device, it seems to get some > commands, then replugs as the hot (0x0500 as far as i can see). > The logfile: http://nopaste.info/eead046817.html I couldn't download this; it is wrapped in HTML. > Firmware: > I did not get any hint (by dmesg), which (or if at all) firmware is sent > to the stick... how can i debug this? Or where is it defined, which FW is > send to whom? It's part of the device configuration struct in m920x.c, but when you plugged in the device (as you showed above) it was in warm state, so no firmware was required to download. You should try to extract your device's firmware from that dvbsnoop output so you won't be dependent on Windows when you get the device working. Nick. _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
