thanks for your response. I'll try your patch ASAP. Here I send the trivial patch I made to autoload the m920x driver. I'm sorry but my programming skill doesn't let me go much further. With this patch, when I plug the device in, this is my syslog output:
Oct 27 18:37:07 inspiron kernel: usb 4-3: new high speed USB device using ehci_hcd and address 2
Oct 27 18:37:07 inspiron kernel: usb 4-3: configuration #1 chosen from 1 choice
Oct 27 18:37:08 inspiron kernel: usbcore: registered new driver dvb_usb_m920x
and nothing else. I suppose I need some kind of firmware. Where can I get it?
Thanks in advance.
PS: I bought the device in a local store in Seville, Spain.
2006/10/27, Michael Krufky <
mkrufky@xxxxxxxxxxx>:
Thorsten Scherler wrote:
> On Wed, 2006-10-25 at 17:20 +0200, Felipe A. Ortega García wrote:
>> Hi
>>
>> I have the same dvb-t adapter, and I've opened it to see the PCB. There
>> are 3 main chips:
>>
>> Zarlink ZL10353
>> Uli M9206 A1
>> MT2060f
>>
>> I think that the first and the third one are supported by the main
>> mercurial tree. The second one is supported by this tree:
>>
>> http://linuxtv.org/hg/~mkrufky/megasky
>>
>> I've compiled this, and when I plugged the adapter nothing happened,
>> something I had expected, because the USB_ID wasn't defined in any
>> driver. I patched the m920x driver with a couple of defines and adding a
>> USB_DEVICE definition, and when I plugged the adapter, the driver loaded
>> automatically, but nothing else. Neither zl10353.ko not mt2060.ko got
>> loaded, and don't know what else to do.
>>
>
> Cheers Felipe for the feedback. Did you get the card as well in Malaga
> on the OS conference (just being curious)?
>
> So, what you report is that you successfully patched the m920x driver
> (how?) and it get loaded but nothing really happens afterward, right?
>
> That gives the impression that the patch may have not really worked to
> well.
>
> Can somebody gives a tip that we may provide a driver implementation for
> the card?
I started to make a patch that I had planned to send in this thread for
the two of you to test... Things have come up and I haven't had time to
finish it.... Give me a few more days and I'll send you something to test.
Please keep in mind that my patch is totally based on guesswork, using
the information provided by you two in this thread. Most likely it wont
work, but it will at least give you a starting point for you to base new
changes from.
Cheers,
Michael Krufky
diff -Nurp megasky.orig/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h megasky/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
--- megasky.orig/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2006-10-27 18:02:44.000000000 +0200
+++ megasky/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2006-10-27 18:23:03.000000000 +0200
@@ -116,6 +116,7 @@
#define USB_PID_MSI_MEGASKY580_55801 0x5581
#define USB_PID_KYE_DVB_T_COLD 0x701e
#define USB_PID_KYE_DVB_T_WARM 0x701f
+#define USB_PID_KYE_TVGODVB_T02Q 0x702b
#define USB_PID_PCTV_200E 0x020e
#define USB_PID_PCTV_400E 0x020f
#define USB_PID_LITEON_DVB_T_COLD 0xf000
diff -Nurp megasky.orig/linux/drivers/media/dvb/dvb-usb/m920x.c megasky/linux/drivers/media/dvb/dvb-usb/m920x.c
--- megasky.orig/linux/drivers/media/dvb/dvb-usb/m920x.c 2006-10-27 18:02:44.000000000 +0200
+++ megasky/linux/drivers/media/dvb/dvb-usb/m920x.c 2006-10-27 18:26:02.000000000 +0200
@@ -422,6 +422,7 @@ static int m920x_probe(struct usb_interf
static struct usb_device_id m920x_table [] = {
{ USB_DEVICE(USB_VID_MSI, USB_PID_MSI_MEGASKY580) },
+ { USB_DEVICE(USB_VID_KYE, USB_PID_KYE_TVGODVB_T02Q) },
{ } /* Terminating entry */
};
MODULE_DEVICE_TABLE (usb, m920x_table);
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
