Uli m9206

[Michael Krufky]

Hello,
i followed the mailarchive through posts dealing with the m9206 chipset.
A few days ago i bought a cheap dvb-t reciver, its a DigiVox Mini II
from Msi. I opend it and saw that it contains an uli m9206 chip and an
phillips tda 10046a. and another phillips chip. i tried to load your rep
called megasky, but i was unable to compile due to errors in aci.*
files. do you think there ist a chance to get my device working? or
should i better return it to seller?
regards
arian sigari

There is a chance, but I will need for you to subscribe to the linux-dvb mailing
list in order to be able to help you with this.

To subscribe: http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Please subscribe BEFORE responding to this email (use reply-to-all).

The megasky tree will not yet work for your device, although you can help us to
add support for it.

I am helping to facilitate the development of this driver between a few other
developers of whom are also active on the mailing list. It would be helpful if
you could provide a list of every chip inside this device. Photos would also help,
in addition to output of "lsusb -vvv"

Most importantly, I need to know what the "other philips chip" is. If I were to
guess, I would think it might be a tda8290 silicon tuner.

Let us know.

Cheers,

Mike Krufky

[Michael Krufky]

Hi! Thanks for the reply. I thought I was already subscribed to the
Linux-dvb mailing list. I mean, isn't this how you got my mail and
replied? :-)
You will find towards the end of this message the output of lsusb -vvv
Loading Image...
Loading Image...
The chips can be seen in the photos. As you can see, there are no
Philips chips there Please tell me if any important info is not visible,
and I will open the case again.

Lucian,

Thank you for sending this information. When I wrote that last email, it
was in response to a private email message that Arian Sigari wrote to me.

However, I did seem to miss your email on the linux-dvb list... But I just
found it now, "[linux-dvb] ULI M9207" from 11/1/06 ....

Anyway, looking at your photos.... I am not familiar with the Atmel and
Techwell chips on that board.... I do not see a DVB-T demodulator.

The Atmel AT49BV512 is a "512 Kbit (64K x 8), 2.7-Volt Read and 2.7-Volt
Write Flash", and seems to be supported in drivers/mtd/chips/jedec_probe.c

Techwell TW9903 is a multi-standard video decoder. Not yet supported, in
mainline, but it seems to be supported in the go7007 wischip driver.

I see an audio ic (ALC650) on the backside.... Is this a hybrid analog /
digital device? To me, it looks like an analog-only device. The m9207 is
only handling USB traffic.

The MFPE05 tuner is not yet supported, but probably wont be difficult to add
support for.

...

It shouldnt be that difficult to get this device to work, but it will require
some more research into the items that I've mentioned above.

I do not think this device will receive digital television -- it seems to be
analog-only.

What are your thoughts?

Regards,

Michael Krufky

[hermann pitton]

Hi!
[snip]

Post by Michael Krufky
The MFPE05 tuner is not yet supported, but probably wont be difficult to add
support for.

Mike, we found the TCL MFPE05 on several Hauppauge devices already and
have it in tveeprom.c mapped to tuner=38. It has a tda9887.

Likely this revision here is also supported this way.

Cheers,
Hermann

[Michael Krufky]

Post by hermann pitton
Hi!
[snip]

Post by Michael Krufky
The MFPE05 tuner is not yet supported, but probably wont be difficult to add
support for.

Mike, we found the TCL MFPE05 on several Hauppauge devices already and
have it in tveeprom.c mapped to tuner=38. It has a tda9887.
Likely this revision here is also supported this way.

Oops, my bad. Thank you, Hermann.

Even still, Lucian did not answer my question. Is that device marketed as
an analog video capture device? ...or is it also supposed to have DVB
functionality? Looks to me like no DVB functionality, but that's why I am
asking you.

Cheers,

Michael Krufky

[hermann pitton]

Post by Michael Krufky

Post by hermann pitton
Hi!
[snip]

Post by Michael Krufky
The MFPE05 tuner is not yet supported, but probably wont be difficult to add
support for.

Mike, we found the TCL MFPE05 on several Hauppauge devices already and
have it in tveeprom.c mapped to tuner=38. It has a tda9887.
Likely this revision here is also supported this way.

Oops, my bad. Thank you, Hermann.
Even still, Lucian did not answer my question. Is that device marketed as
an analog video capture device? ...or is it also supposed to have DVB
functionality? Looks to me like no DVB functionality, but that's why I am
asking you.

Yes, that could be exactly the next question ;)

The known one has TCL MFPE05 2 on it, IIRC, and was analog only.
The TCL site is undergoing some reconstruction currently, seems nothing
useful in that direction at the moment.

Would need to search within my stuff, but if it is mucked up to some
hybrid device, there would be a third SAW filter within the IF tuner
compartment and the missing rest of a FMD1216.

Don't think so, but if in doubt Gunther has a picture of an opened FMD.

Cheers,
Hermann

[hermann pitton]

Hi!

Post by hermann pitton

Post by Michael Krufky

Post by hermann pitton
Hi!
[snip]

Post by Michael Krufky
The MFPE05 tuner is not yet supported, but probably wont be difficult to add
support for.

Mike, we found the TCL MFPE05 on several Hauppauge devices already and
have it in tveeprom.c mapped to tuner=38. It has a tda9887.
Likely this revision here is also supported this way.

Oops, my bad. Thank you, Hermann.
Even still, Lucian did not answer my question. Is that device marketed as
an analog video capture device? ...or is it also supposed to have DVB
functionality? Looks to me like no DVB functionality, but that's why I am
asking you.

Yes, that could be exactly the next question ;)
The known one has TCL MFPE05 2 on it, IIRC, and was analog only.
The TCL site is undergoing some reconstruction currently, seems nothing
useful in that direction at the moment.
Would need to search within my stuff, but if it is mucked up to some
hybrid device, there would be a third SAW filter within the IF tuner
compartment and the missing rest of a FMD1216.
Don't think so, but if in doubt Gunther has a picture of an opened FMD.

An FMD clone would not be enough, as you said, no channel decoder.

The prolink site is really incredible on this and suggests digital.
http://www.prolink.com.tw/english/products/multimedia/PlayTV_400USB.htm

As long as the 64pin U6 position underneath the tuner is not populated,
I'll take it for pure nonsense.

Cheers,
Hermann

[Arian Sigari]

Hello,
again me. I took photos of the device. www.sigari.de/00001.jpg and
www.sigari.de/00003.jpg . I got your megasky repro compiled and changed
the usb ids from the megasky device to mine. if i plug in dmesg says:

dvb-usb: found a 'MSI Mega Sky 580 DVB-T USB2.0' in cold state, will try
to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-megasky-02.fw'
dvb_usb_m920x: probe of 1-6:1.0 failed with error 64
usbcore: registered new driver dvb_usb_m920x

ok, well this is my third dvb-t device i hope we can adapt the driver so
it is able to run. i sold the other devices
due to complete linux incompability.

so if the photos are not good enough:
the third chip is labled as 8275AC1 P1W85 03 ePG06171 with a
philips logo.
the output of lsusb -vvv is:

Bus 001 Device 012: ID 0db0:5580 Micro Star International
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0db0 Micro Star International
idProduct 0x5580
bcdDevice 0.95
iManufacturer 1 ULi Electronics
iProduct 2 DTV USB MINI
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered

What can i do now? I am able to edit c sources, i can compile things...
please help
greetings from germany
arian sigari

Hi! Thanks for the reply. I thought I was already subscribed to the
Linux-dvb mailing list. I mean, isn't this how you got my mail and
replied? :-)
You will find towards the end of this message the output of lsusb -vvv
http://louis-nichols.uv.ro/tvtuner/IMG_7050.JPG
http://louis-nichols.uv.ro/tvtuner/IMG_7051.JPG
The chips can be seen in the photos. As you can see, there are no
Philips chips there Please tell me if any important info is not
visible, and I will open the case again.
Please tell me how I can be of further assistance
===========================================
Bus 003 Device 001: ID 0000:0000
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 12
Bus 002 Device 002: ID 046d:092c Logitech, Inc.
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0x092c
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
bLength 9
bDescriptorType 2
wTotalLength 233
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0080 1x 128 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0370 1x 880 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0280 1x 640 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0300 1x 768 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0380 1x 896 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 7
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ff 1x 1023 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 8
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0220 1x 544 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 9
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0290 1x 656 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 10
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x02c0 1x 704 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 11
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0360 1x 864 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 12
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03c0 1x 960 bytes
bInterval 1
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 13
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x034d 1x 845 bytes
bInterval 1
Bus 002 Device 001: ID 0000:0000
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Bus 001 Device 003: ID 0b10:2052 Pcally
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0b10 Pcally
idProduct 0x2052
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 80mA
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 52
** UNAVAILABLE **
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
Bus 001 Device 001: ID 0000:0000
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:a
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Lucian Iuga
tel: +40 - (0)744 63 0744
------------------------------------------------------------------------------
Get Thunderbird
Get Firefox!
I use them. I know you'll like them!
------------------------------------------------------------------------------

Post by Michael Krufky

Hello,
i followed the mailarchive through posts dealing with the m9206 chipset.
A few days ago i bought a cheap dvb-t reciver, its a DigiVox Mini II
from Msi. I opend it and saw that it contains an uli m9206 chip and an
phillips tda 10046a. and another phillips chip. i tried to load your rep
called megasky, but i was unable to compile due to errors in aci.*
files. do you think there ist a chance to get my device working? or
should i better return it to seller?
regards
arian sigari

There is a chance, but I will need for you to subscribe to the linux-dvb mailing
list in order to be able to help you with this.
To subscribe: http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Please subscribe BEFORE responding to this email (use reply-to-all).
The megasky tree will not yet work for your device, although you can help us to
add support for it.
I am helping to facilitate the development of this driver between a few other
developers of whom are also active on the mailing list. It would be helpful if
you could provide a list of every chip inside this device. Photos would also help,
in addition to output of "lsusb -vvv"
Most importantly, I need to know what the "other philips chip" is. If I were to
guess, I would think it might be a tda8290 silicon tuner.
Let us know.
Cheers,
Mike Krufky

[Aapo Tahkola]

On Fri, 17 Nov 2006 09:30:09 +0100 (MET)

Hello,
again me. I took photos of the device. www.sigari.de/00001.jpg and
www.sigari.de/00003.jpg . I got your megasky repro compiled and
changed the usb ids from the megasky device to mine. if i plug in
dvb-usb: found a 'MSI Mega Sky 580 DVB-T USB2.0' in cold state, will
try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-megasky-02.fw'
dvb_usb_m920x: probe of 1-6:1.0 failed with error 64
usbcore: registered new driver dvb_usb_m920x
ok, well this is my third dvb-t device i hope we can adapt the driver
so it is able to run. i sold the other devices
due to complete linux incompability.
the third chip is labled as 8275AC1 P1W85 03 ePG06171 with a
philips logo.

You will most likely need new firmware for your device.
Here are some suggestions on how to go about it:
1. get vmware player and recompile kernel with usbmon
2. install windows and drivers
3. rmmod ehci_hcd (vmware might freak out your computer otherwise)

You will probably need these and probably some more to get usbmon
working: (look up with google)
mount -t debugfs none_debugs /sys/kernel/debug
modprobe usbmon
mount -t usbfs none /proc/bus/usb
chmod -R a+rw /proc/bus/usb (security!!)

To fetch the firmware:
1. Unplug aerial cable so that no other data comes out of the device.
2. Kill/remove program called uremote.exe (if you have it) as it will
cause i2c traffic that's not very interesting.
3. Plug you device and look for something interesting data being sent
to the device. These should be control messages - look up usb spec for
more details.

It should get sent immediately after device is connected so you don't
have to start any dvb software. You will probably need to write another
script to turn that firmware into binary from.
Attached perl script should put some sense
to usbmon logs and m9206 i2c messages. Be aware though that it might
break easily. AFAIK, vmware does not seem to support isoch/bulk
transfers so you probably wont see any picture.