* [linux-dvb] leadtek dtv dongle @ 2008-03-23 12:35 ptay1685 2008-03-23 22:43 ` Antti Palosaari 0 siblings, 1 reply; 9+ messages in thread From: ptay1685 @ 2008-03-23 12:35 UTC (permalink / raw) To: linux-dvb [-- Attachment #1.1: Type: text/plain, Size: 154 bytes --] Any news about the new version of the dtv dongle? Still does not work with the latest v4l sources. Anyone know whats happening? Many thanks, Phil T. [-- Attachment #1.2: Type: text/html, Size: 652 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] leadtek dtv dongle 2008-03-23 12:35 [linux-dvb] leadtek dtv dongle ptay1685 @ 2008-03-23 22:43 ` Antti Palosaari 2008-03-26 1:37 ` ptay1685 0 siblings, 1 reply; 9+ messages in thread From: Antti Palosaari @ 2008-03-23 22:43 UTC (permalink / raw) To: ptay1685; +Cc: linux-dvb ptay1685 wrote: > > Any news about the new version of the dtv dongle? Still does not work > with the latest v4l sources. Anyone know whats happening? > > Many thanks, > > Phil T. Can you say what is usb-id of your device? Also lsusb -v could be nice to see. regards Antti -- http://palosaari.fi/ _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] leadtek dtv dongle 2008-03-23 22:43 ` Antti Palosaari @ 2008-03-26 1:37 ` ptay1685 2008-03-26 2:03 ` John 0 siblings, 1 reply; 9+ messages in thread From: ptay1685 @ 2008-03-26 1:37 UTC (permalink / raw) To: Antti Palosaari; +Cc: linux-dvb How do I tell the usb-id? Tried to do a lsusb -v but the command is unrecognised. Note that the Leadtek device is not actually recognised by the kernel (shown via dmesg). The following is from a previous conversation on this mailing list and might give you the info you need: _______________________________________________________________________________ Hi, How do I get a patch incorporated into the dvb kernel section ? After recently purchasing a LeadTek WinFast DTV Dongle I rapidly discovered it was the variant that was not recognized in the kernel i.e. as previously reported at: http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022373.html http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023175.html its device ids are: (lsusb) ID 0413:6f01 Leadtek Research, Inc. Rather than make the changes suggested by previous posters I set about making a script and associated kernel patches to automatically do this. My motivation was simple: I use a laptop with an ATI graphics card and fedora 8. I find the best drivers for this card are currently from Livna and are updated monthly (and changes are significant at the moment i.e. see the phoronix forum). So I would need to do this repeatedly. In my patch I add an identifier (USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) and modify the table appropriately When I plug it in I now see in my messages log kernel: usb 1-4: new high speed USB device using ehci_hcd and address 9 kernel: usb 1-4: configuration #1 chosen from 1 choice kernel: dib0700: loaded with support for 2 different device-types kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' in cold state, will try to load a firmware kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' kernel: dib0700: firmware started successfully. kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' in warm state. kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. kernel: DVB: registering new adapter (Leadtek Winfast DTV Dongle B (STK7700P based)) kernel: DVB: registering frontend 0 (DiBcom 7000PC)... kernel: MT2060: successfully identified (IF1 = 1220) kernel: dvb-usb: Leadtek Winfast DTV Dongle B (STK7700P based) successfully initialized and connected. kernel: usbcore: registered new interface driver dvb_usb_dib0700 My kernel patch ( other scripts to patch the Fedora 8 src rpm's available on request) ---------------- --- a/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 10:05:13.000000000 +1100 +++ b/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 10:22:16.000000000 +1100 @@ -280,6 +280,7 @@ struct usb_device_id dib0700_usb_id_tabl { USB_DEVICE(USB_VID_LEADTEK, USB_PID_WINFAST_DTV_DONGLE_STK7700P) }, { USB_DEVICE(USB_VID_HAUPPAUGE, USB_PID_HAUPPAUGE_NOVA_T_STICK_2) }, { USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_VOLAR_2) }, + { USB_DEVICE(USB_VID_LEADTEK, USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) }, { } /* Terminating entry */ }; MODULE_DEVICE_TABLE(usb, dib0700_usb_id_table); @@ -321,7 +322,7 @@ struct dvb_usb_device_properties dib0700 }, }, - .num_device_descs = 6, + .num_device_descs = 7, .devices = { { "DiBcom STK7700P reference design", { &dib0700_usb_id_table[0], &dib0700_usb_id_table[1] }, @@ -346,6 +347,10 @@ struct dvb_usb_device_properties dib0700 { "Leadtek Winfast DTV Dongle (STK7700P based)", { &dib0700_usb_id_table[8], NULL }, { NULL }, + }, + { "Leadtek Winfast DTV Dongle B (STK7700P based)", + { &dib0700_usb_id_table[11], NULL }, + { NULL }, } } }, { DIB0700_DEFAULT_DEVICE_PROPERTIES, --- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 10:05:13.000000000 +1100 +++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 10:18:00.000000000 +1100 @@ -148,6 +148,7 @@ #define USB_PID_WINFAST_DTV_DONGLE_COLD 0x6025 #define USB_PID_WINFAST_DTV_DONGLE_WARM 0x6026 #define USB_PID_WINFAST_DTV_DONGLE_STK7700P 0x6f00 +#define USB_PID_WINFAST_DTV_DONGLE_STK7700P_B 0x6f01 #define USB_PID_GENPIX_8PSK_COLD 0x0200 #define USB_PID_GENPIX_8PSK_WARM 0x0201 #define USB_PID_SIGMATEK_DVB_110 0x6610 _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ----- Original Message ----- From: "Antti Palosaari" <crope@iki.fi> To: "ptay1685" <ptay1685@Bigpond.net.au> Cc: <linux-dvb@linuxtv.org> Sent: Monday, March 24, 2008 9:43 AM Subject: Re: [linux-dvb] leadtek dtv dongle > ptay1685 wrote: >> >> Any news about the new version of the dtv dongle? Still does not work >> with the latest v4l sources. Anyone know whats happening? >> >> Many thanks, >> >> Phil T. > > Can you say what is usb-id of your device? Also lsusb -v could be nice > to see. > > regards > Antti > -- > http://palosaari.fi/ > > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] leadtek dtv dongle 2008-03-26 1:37 ` ptay1685 @ 2008-03-26 2:03 ` John [not found] ` <002301c88ee9$fd998500$6e00a8c0@barny1e59e583e> 0 siblings, 1 reply; 9+ messages in thread From: John @ 2008-03-26 2:03 UTC (permalink / raw) To: ptay1685; +Cc: linux-dvb [-- Attachment #1.1: Type: text/plain, Size: 7413 bytes --] As I originally posted the quoted email below, I might be able to help you. firstly: lsusb is located in the usbutils package so you may need to install it, or you need to prefix the command with its location i.e. /sbin/lsusb. Please try this first and post the result back to the list. (with the -v option please) secondly in reference to my patch below. I never heard anything more from the list about it and I have no reason to believe it was ever incorporated as a patch. I suspect this dongle is a variant sold only in Australia (where you and I are from obviously) and so the demand is relatively small - thus no one else was interested. I posted more for people like yourself for whom my fix may help. The only thing this patch did is add an extra identifier so that the dongle was recognized. Now that said, I suspect there is an even more recent variant released in the last 2/3 months (right after I bought mine :( ) which may have a different identifier again. So the result of lsusb is even more important. Unfortunately I got distracted after I got my dongle recognized and haven't made it fully work yet (with MythTv) - but if you are interested I might have another go at it. I also note the large number of dibcom related posts in recent months which will have a direct bearing on this dongle. So recent versions of the dvb code are essential. Cheers, J ptay1685 wrote: > How do I tell the usb-id? Tried to do a lsusb -v but the command is > unrecognised. > > Note that the Leadtek device is not actually recognised by the kernel (shown > via dmesg). > > The following is from a previous conversation on this mailing list and might > give you the info you need: > _______________________________________________________________________________ > > Hi, > > How do I get a patch incorporated into the dvb kernel section ? > > After recently purchasing a LeadTek WinFast DTV Dongle I rapidly > discovered it was the variant that was not recognized in the kernel > > i.e. as previously reported at: > http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022373.html > http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023175.html > > its device ids are: (lsusb) > ID 0413:6f01 Leadtek Research, Inc. > > Rather than make the changes suggested by previous posters I set about > making a script and associated kernel patches to automatically do this. > My motivation was simple: I use a laptop with an ATI graphics card and > fedora 8. I find the best drivers for this card are currently from Livna > and are updated monthly (and changes are significant at the moment i.e. > see the phoronix forum). So I would need to do this repeatedly. > > In my patch I add an identifier (USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) > and modify the table appropriately > > When I plug it in I now see in my messages log > kernel: usb 1-4: new high speed USB device using ehci_hcd and address 9 > kernel: usb 1-4: configuration #1 chosen from 1 choice > kernel: dib0700: loaded with support for 2 different device-types > kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' > in cold state, will try to load a firmware > kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' > kernel: dib0700: firmware started successfully. > kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' > in warm state. > kernel: dvb-usb: will pass the complete MPEG2 transport stream to the > software demuxer. > kernel: DVB: registering new adapter (Leadtek Winfast DTV Dongle B > (STK7700P based)) > kernel: DVB: registering frontend 0 (DiBcom 7000PC)... > kernel: MT2060: successfully identified (IF1 = 1220) > kernel: dvb-usb: Leadtek Winfast DTV Dongle B (STK7700P based) > successfully initialized and connected. > kernel: usbcore: registered new interface driver dvb_usb_dib0700 > > > My kernel patch ( other scripts to patch the Fedora 8 src rpm's > available on request) > ---------------- > --- a/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 > 10:05:13.000000000 +1100 > +++ b/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 > 10:22:16.000000000 +1100 > @@ -280,6 +280,7 @@ struct usb_device_id dib0700_usb_id_tabl > { USB_DEVICE(USB_VID_LEADTEK, > USB_PID_WINFAST_DTV_DONGLE_STK7700P) }, > { USB_DEVICE(USB_VID_HAUPPAUGE, > USB_PID_HAUPPAUGE_NOVA_T_STICK_2) }, > { USB_DEVICE(USB_VID_AVERMEDIA, > USB_PID_AVERMEDIA_VOLAR_2) }, > + { USB_DEVICE(USB_VID_LEADTEK, > USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) }, > { } /* Terminating entry */ > }; > MODULE_DEVICE_TABLE(usb, dib0700_usb_id_table); > @@ -321,7 +322,7 @@ struct dvb_usb_device_properties dib0700 > }, > }, > > - .num_device_descs = 6, > + .num_device_descs = 7, > .devices = { > { "DiBcom STK7700P reference design", > { &dib0700_usb_id_table[0], > &dib0700_usb_id_table[1] }, > @@ -346,6 +347,10 @@ struct dvb_usb_device_properties dib0700 > { "Leadtek Winfast DTV Dongle (STK7700P > based)", > { &dib0700_usb_id_table[8], NULL }, > { NULL }, > + }, > + { "Leadtek Winfast DTV Dongle B (STK7700P > based)", > + { &dib0700_usb_id_table[11], NULL }, > + { NULL }, > } > } > }, { DIB0700_DEFAULT_DEVICE_PROPERTIES, > --- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 > 10:05:13.000000000 +1100 > +++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 > 10:18:00.000000000 +1100 > @@ -148,6 +148,7 @@ > #define USB_PID_WINFAST_DTV_DONGLE_COLD 0x6025 > #define USB_PID_WINFAST_DTV_DONGLE_WARM 0x6026 > #define USB_PID_WINFAST_DTV_DONGLE_STK7700P 0x6f00 > +#define USB_PID_WINFAST_DTV_DONGLE_STK7700P_B 0x6f01 > #define USB_PID_GENPIX_8PSK_COLD 0x0200 > #define USB_PID_GENPIX_8PSK_WARM 0x0201 > #define USB_PID_SIGMATEK_DVB_110 0x6610 > > > > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > ----- Original Message ----- > From: "Antti Palosaari" <crope@iki.fi> > To: "ptay1685" <ptay1685@Bigpond.net.au> > Cc: <linux-dvb@linuxtv.org> > Sent: Monday, March 24, 2008 9:43 AM > Subject: Re: [linux-dvb] leadtek dtv dongle > > > >> ptay1685 wrote: >> >>> Any news about the new version of the dtv dongle? Still does not work >>> with the latest v4l sources. Anyone know whats happening? >>> >>> Many thanks, >>> >>> Phil T. >>> >> Can you say what is usb-id of your device? Also lsusb -v could be nice >> to see. >> >> regards >> Antti >> -- >> http://palosaari.fi/ >> >> _______________________________________________ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > > > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > [-- Attachment #1.2: Type: text/html, Size: 8772 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <002301c88ee9$fd998500$6e00a8c0@barny1e59e583e>]
* Re: [linux-dvb] leadtek dtv dongle [not found] ` <002301c88ee9$fd998500$6e00a8c0@barny1e59e583e> @ 2008-03-26 2:48 ` John 2008-03-26 2:53 ` ptay1685 2008-03-27 14:05 ` [linux-dvb] leadtek dtv dongle lsusb ptay1685 0 siblings, 2 replies; 9+ messages in thread From: John @ 2008-03-26 2:48 UTC (permalink / raw) To: ptay1685; +Cc: linux-dvb [-- Attachment #1.1: Type: text/plain, Size: 9942 bytes --] please respond to the list - ptay1685 wrote: > Thanks. > > Just my luck. First off I get a Nebula usb DigiTV which never worked > owing to an problem with ny nforce2 usb controller (i found out when > it was too late), and which came with suspect WIndows software. So > before I bought my two Leadtek dongles I checked the DVB wikipedia to > make sure I got a fully Linux supported device. Now I have two new usb > dongles neither of which work with Linux. You can't bloody win can > you? At least they come with great WIndows software, which is more > than you can say for the Nebula. > > I can now use the Nebula with Linux but the leadtek software under > WIndows is so good, that now I simply boot Windows to do my DVB stuff, > and sometimes use Linux to author the DVD's (DeVeDe). > > I guess this situation will persist until hardware vendors decide to > support Linux. Unfortunately I will probably be six feet under by then. > > I would certainly be interested in a fix for this situation but its > hardly worth anyone putting in a lot of effort for just one person or > at most a handful of people. But if you are able / willing to do > something to remedy this problem I will certainly be very grateful. > > Or perhaps one day I will work up the motivation to patch the code as > you did - but i dare not hold my breath waiting for that to happen! > 1) the fix is simple and someone on the list will be able to push through a simple patch, if all that is involved is added another identifier to recognise your device. 2) we still need your lsusb -v to confirm this. if you can do even a few minutes of effort to determine the required information, you might be surprised to find others in your situation and/or those capable of helping. > > > firstly: lsusb is located in the usbutils package so you may need > to install it, or you need to prefix the command with its location > i.e. /sbin/lsusb. Please try this first and post the result back > to the list. (with the -v option please) > > secondly in reference to my patch below. > I never heard anything more from the list about it and I have no > reason to believe it was ever incorporated as a patch. I suspect > this dongle is a variant sold only in Australia (where you and I > are from obviously) and so the demand is relatively small - thus > no one else was interested. I posted more for people like yourself > for whom my fix may help. > > The only thing this patch did is add an extra identifier so that > the dongle was recognized. Now that said, I suspect there is an > even more recent variant released in the last 2/3 months (right > after I bought mine :( ) which may have a different identifier > again. So the result of lsusb is even more important. > > Unfortunately I got distracted after I got my dongle recognized > and haven't made it fully work yet (with MythTv) - but if you are > interested I might have another go at it. > > I also note the large number of dibcom related posts in recent > months which will have a direct bearing on this dongle. So recent > versions of the dvb code are essential. > > Cheers, > J > > ptay1685 wrote: >> How do I tell the usb-id? Tried to do a lsusb -v but the command is >> unrecognised. >> >> Note that the Leadtek device is not actually recognised by the kernel (shown >> via dmesg). >> >> The following is from a previous conversation on this mailing list and might >> give you the info you need: >> _______________________________________________________________________________ >> >> Hi, >> >> How do I get a patch incorporated into the dvb kernel section ? >> >> After recently purchasing a LeadTek WinFast DTV Dongle I rapidly >> discovered it was the variant that was not recognized in the kernel >> >> i.e. as previously reported at: >> http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022373.html >> http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023175.html >> >> its device ids are: (lsusb) >> ID 0413:6f01 Leadtek Research, Inc. >> >> Rather than make the changes suggested by previous posters I set about >> making a script and associated kernel patches to automatically do this. >> My motivation was simple: I use a laptop with an ATI graphics card and >> fedora 8. I find the best drivers for this card are currently from Livna >> and are updated monthly (and changes are significant at the moment i.e. >> see the phoronix forum). So I would need to do this repeatedly. >> >> In my patch I add an identifier (USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) >> and modify the table appropriately >> >> When I plug it in I now see in my messages log >> kernel: usb 1-4: new high speed USB device using ehci_hcd and address 9 >> kernel: usb 1-4: configuration #1 chosen from 1 choice >> kernel: dib0700: loaded with support for 2 different device-types >> kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' >> in cold state, will try to load a firmware >> kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' >> kernel: dib0700: firmware started successfully. >> kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' >> in warm state. >> kernel: dvb-usb: will pass the complete MPEG2 transport stream to the >> software demuxer. >> kernel: DVB: registering new adapter (Leadtek Winfast DTV Dongle B >> (STK7700P based)) >> kernel: DVB: registering frontend 0 (DiBcom 7000PC)... >> kernel: MT2060: successfully identified (IF1 = 1220) >> kernel: dvb-usb: Leadtek Winfast DTV Dongle B (STK7700P based) >> successfully initialized and connected. >> kernel: usbcore: registered new interface driver dvb_usb_dib0700 >> >> >> My kernel patch ( other scripts to patch the Fedora 8 src rpm's >> available on request) >> ---------------- >> --- a/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 >> 10:05:13.000000000 +1100 >> +++ b/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 >> 10:22:16.000000000 +1100 >> @@ -280,6 +280,7 @@ struct usb_device_id dib0700_usb_id_tabl >> { USB_DEVICE(USB_VID_LEADTEK, >> USB_PID_WINFAST_DTV_DONGLE_STK7700P) }, >> { USB_DEVICE(USB_VID_HAUPPAUGE, >> USB_PID_HAUPPAUGE_NOVA_T_STICK_2) }, >> { USB_DEVICE(USB_VID_AVERMEDIA, >> USB_PID_AVERMEDIA_VOLAR_2) }, >> + { USB_DEVICE(USB_VID_LEADTEK, >> USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) }, >> { } /* Terminating entry */ >> }; >> MODULE_DEVICE_TABLE(usb, dib0700_usb_id_table); >> @@ -321,7 +322,7 @@ struct dvb_usb_device_properties dib0700 >> }, >> }, >> >> - .num_device_descs = 6, >> + .num_device_descs = 7, >> .devices = { >> { "DiBcom STK7700P reference design", >> { &dib0700_usb_id_table[0], >> &dib0700_usb_id_table[1] }, >> @@ -346,6 +347,10 @@ struct dvb_usb_device_properties dib0700 >> { "Leadtek Winfast DTV Dongle (STK7700P >> based)", >> { &dib0700_usb_id_table[8], NULL }, >> { NULL }, >> + }, >> + { "Leadtek Winfast DTV Dongle B (STK7700P >> based)", >> + { &dib0700_usb_id_table[11], NULL }, >> + { NULL }, >> } >> } >> }, { DIB0700_DEFAULT_DEVICE_PROPERTIES, >> --- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 >> 10:05:13.000000000 +1100 >> +++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 >> 10:18:00.000000000 +1100 >> @@ -148,6 +148,7 @@ >> #define USB_PID_WINFAST_DTV_DONGLE_COLD 0x6025 >> #define USB_PID_WINFAST_DTV_DONGLE_WARM 0x6026 >> #define USB_PID_WINFAST_DTV_DONGLE_STK7700P 0x6f00 >> +#define USB_PID_WINFAST_DTV_DONGLE_STK7700P_B 0x6f01 >> #define USB_PID_GENPIX_8PSK_COLD 0x0200 >> #define USB_PID_GENPIX_8PSK_WARM 0x0201 >> #define USB_PID_SIGMATEK_DVB_110 0x6610 >> >> >> >> _______________________________________________ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> >> ----- Original Message ----- >> From: "Antti Palosaari" <crope@iki.fi> >> To: "ptay1685" <ptay1685@Bigpond.net.au> >> Cc: <linux-dvb@linuxtv.org> >> Sent: Monday, March 24, 2008 9:43 AM >> Subject: Re: [linux-dvb] leadtek dtv dongle >> >> >> >>> ptay1685 wrote: >>> >>>> Any news about the new version of the dtv dongle? Still does not work >>>> with the latest v4l sources. Anyone know whats happening? >>>> >>>> Many thanks, >>>> >>>> Phil T. >>>> >>> Can you say what is usb-id of your device? Also lsusb -v could be nice >>> to see. >>> >>> regards >>> Antti >>> -- >>> http://palosaari.fi/ >>> >>> _______________________________________________ >>> linux-dvb mailing list >>> linux-dvb@linuxtv.org >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>> >> >> >> _______________________________________________ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > [-- Attachment #1.2: Type: text/html, Size: 11738 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] leadtek dtv dongle 2008-03-26 2:48 ` John @ 2008-03-26 2:53 ` ptay1685 2008-03-26 4:41 ` Jarryd Beck 2008-03-27 14:05 ` [linux-dvb] leadtek dtv dongle lsusb ptay1685 1 sibling, 1 reply; 9+ messages in thread From: ptay1685 @ 2008-03-26 2:53 UTC (permalink / raw) To: linux-dvb [-- Attachment #1.1: Type: text/plain, Size: 907 bytes --] Dont mind the effort per se, its the lack of knowledge which usually leads to hours of frustration when things don't work that put me off - e.g. the current example where someone asks me to do a lsusb but its not on my system, and no easy way of knowing which package its in, etc. etc. Im an ex IT person suffering from burn out and stress, and to me a small effort is a huge one. But I will give it my best shot. As I said, I would like to help if possible. Will let you know as soon as i get the lsusb working. Regards, Phil T, ----- Original Message ----- From: John To: ptay1685 if you can do even a few minutes of effort to determine the required information, you might be surprised to find others in your situation and/or those capable of helping. linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb [-- Attachment #1.2: Type: text/html, Size: 2125 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] leadtek dtv dongle 2008-03-26 2:53 ` ptay1685 @ 2008-03-26 4:41 ` Jarryd Beck 0 siblings, 0 replies; 9+ messages in thread From: Jarryd Beck @ 2008-03-26 4:41 UTC (permalink / raw) To: ptay1685; +Cc: linux-dvb 2008/3/26 ptay1685 <ptay1685@bigpond.net.au>: > > > Dont mind the effort per se, its the lack of knowledge which usually leads > to hours of frustration when things don't work that put me off - e.g. the > current example where someone asks me to do a lsusb but its not on my > system, and no easy way of knowing which package its in, etc. etc. Im an ex > IT person suffering from burn out and stress, and to me a small effort is a > huge one. > > But I will give it my best shot. As I said, I would like to help if > possible. Will let you know as soon as i get the lsusb working. > > Regards, > > Phil T, > > ----- Original Message ----- > From: John > To: ptay1685 > if you can do even a few minutes of effort to determine the required > information, you might be surprised to find others in your situation and/or > those capable of helping. > > > > > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > lsusb is in /sbin which isn't usually in a normal users' path, so that could be the problem. Jarryd. _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] leadtek dtv dongle lsusb 2008-03-26 2:48 ` John 2008-03-26 2:53 ` ptay1685 @ 2008-03-27 14:05 ` ptay1685 [not found] ` <1206776111.18375.11.camel@localhost.localdomain> 1 sibling, 1 reply; 9+ messages in thread From: ptay1685 @ 2008-03-27 14:05 UTC (permalink / raw) To: linux-dvb [-- Attachment #1.1: Type: text/plain, Size: 22559 bytes --] Here is the output from lsusb -v: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Bus 005 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: 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 002 Device 003: ID 0413:6f01 Leadtek Research, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0413 Leadtek Research, Inc. idProduct 0x6f01 bcdDevice 0.02 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Bus 002 Device 002: ID 0413:6f01 Leadtek Research, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0413 Leadtek Research, Inc. idProduct 0x6f01 bcdDevice 0.02 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Bus 002 Device 001: ID 0000:0000 Device Descriptor: 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 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: 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 12 Bus 004 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: 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 001: ID 0000:0000 Device Descriptor: 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 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: 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 12 Bus 003 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x045e Microsoft Corp. idProduct 0x0053 Optical Mouse bcdDevice 3.00 iManufacturer 1 iProduct 3 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 72 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: 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 003 Device 004: ID 045e:002b Microsoft Corp. Internet Keyboard Pro Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x045e Microsoft Corp. idProduct 0x002b Internet Keyboard Pro bcdDevice 1.14 iManufacturer 0 iProduct 1 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 1 bmAttributes 0xa0 Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 1 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 54 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 1 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 50 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0003 1x 3 bytes bInterval 10 Bus 003 Device 003: ID 0451:1446 Texas Instruments, Inc. TUSB2040/2070 Hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 8 idVendor 0x0451 Texas Instruments, Inc. idProduct 0x1446 TUSB2040/2070 Hub bcdDevice 1.10 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 UNRECOGNIZED: 09 29 04 09 00 32 64 00 1e Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 255 Bus 003 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: 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 ----- Original Message ----- From: John To: ptay1685 Cc: linux-dvb@linuxtv.org Sent: Wednesday, March 26, 2008 1:48 PM Subject: Re: [linux-dvb] leadtek dtv dongle please respond to the list - ptay1685 wrote: Thanks. Just my luck. First off I get a Nebula usb DigiTV which never worked owing to an problem with ny nforce2 usb controller (i found out when it was too late), and which came with suspect WIndows software. So before I bought my two Leadtek dongles I checked the DVB wikipedia to make sure I got a fully Linux supported device. Now I have two new usb dongles neither of which work with Linux. You can't bloody win can you? At least they come with great WIndows software, which is more than you can say for the Nebula. I can now use the Nebula with Linux but the leadtek software under WIndows is so good, that now I simply boot Windows to do my DVB stuff, and sometimes use Linux to author the DVD's (DeVeDe). I guess this situation will persist until hardware vendors decide to support Linux. Unfortunately I will probably be six feet under by then. I would certainly be interested in a fix for this situation but its hardly worth anyone putting in a lot of effort for just one person or at most a handful of people. But if you are able / willing to do something to remedy this problem I will certainly be very grateful. Or perhaps one day I will work up the motivation to patch the code as you did - but i dare not hold my breath waiting for that to happen! 1) the fix is simple and someone on the list will be able to push through a simple patch, if all that is involved is added another identifier to recognise your device. 2) we still need your lsusb -v to confirm this. if you can do even a few minutes of effort to determine the required information, you might be surprised to find others in your situation and/or those capable of helping. firstly: lsusb is located in the usbutils package so you may need to install it, or you need to prefix the command with its location i.e. /sbin/lsusb. Please try this first and post the result back to the list. (with the -v option please) secondly in reference to my patch below. I never heard anything more from the list about it and I have no reason to believe it was ever incorporated as a patch. I suspect this dongle is a variant sold only in Australia (where you and I are from obviously) and so the demand is relatively small - thus no one else was interested. I posted more for people like yourself for whom my fix may help. The only thing this patch did is add an extra identifier so that the dongle was recognized. Now that said, I suspect there is an even more recent variant released in the last 2/3 months (right after I bought mine :( ) which may have a different identifier again. So the result of lsusb is even more important. Unfortunately I got distracted after I got my dongle recognized and haven't made it fully work yet (with MythTv) - but if you are interested I might have another go at it. I also note the large number of dibcom related posts in recent months which will have a direct bearing on this dongle. So recent versions of the dvb code are essential. Cheers, J ptay1685 wrote: How do I tell the usb-id? Tried to do a lsusb -v but the command is unrecognised. Note that the Leadtek device is not actually recognised by the kernel (shown via dmesg). The following is from a previous conversation on this mailing list and might give you the info you need: _______________________________________________________________________________ Hi, How do I get a patch incorporated into the dvb kernel section ? After recently purchasing a LeadTek WinFast DTV Dongle I rapidly discovered it was the variant that was not recognized in the kernel i.e. as previously reported at: http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022373.html http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023175.html its device ids are: (lsusb) ID 0413:6f01 Leadtek Research, Inc. Rather than make the changes suggested by previous posters I set about making a script and associated kernel patches to automatically do this. My motivation was simple: I use a laptop with an ATI graphics card and fedora 8. I find the best drivers for this card are currently from Livna and are updated monthly (and changes are significant at the moment i.e. see the phoronix forum). So I would need to do this repeatedly. In my patch I add an identifier (USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) and modify the table appropriately When I plug it in I now see in my messages log kernel: usb 1-4: new high speed USB device using ehci_hcd and address 9 kernel: usb 1-4: configuration #1 chosen from 1 choice kernel: dib0700: loaded with support for 2 different device-types kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' in cold state, will try to load a firmware kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' kernel: dib0700: firmware started successfully. kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)' in warm state. kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. kernel: DVB: registering new adapter (Leadtek Winfast DTV Dongle B (STK7700P based)) kernel: DVB: registering frontend 0 (DiBcom 7000PC)... kernel: MT2060: successfully identified (IF1 = 1220) kernel: dvb-usb: Leadtek Winfast DTV Dongle B (STK7700P based) successfully initialized and connected. kernel: usbcore: registered new interface driver dvb_usb_dib0700 My kernel patch ( other scripts to patch the Fedora 8 src rpm's available on request) ---------------- --- a/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 10:05:13.000000000 +1100 +++ b/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13 10:22:16.000000000 +1100 @@ -280,6 +280,7 @@ struct usb_device_id dib0700_usb_id_tabl { USB_DEVICE(USB_VID_LEADTEK, USB_PID_WINFAST_DTV_DONGLE_STK7700P) }, { USB_DEVICE(USB_VID_HAUPPAUGE, USB_PID_HAUPPAUGE_NOVA_T_STICK_2) }, { USB_DEVICE(USB_VID_AVERMEDIA, USB_PID_AVERMEDIA_VOLAR_2) }, + { USB_DEVICE(USB_VID_LEADTEK, USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) }, { } /* Terminating entry */ }; MODULE_DEVICE_TABLE(usb, dib0700_usb_id_table); @@ -321,7 +322,7 @@ struct dvb_usb_device_properties dib0700 }, }, - .num_device_descs = 6, + .num_device_descs = 7, .devices = { { "DiBcom STK7700P reference design", { &dib0700_usb_id_table[0], &dib0700_usb_id_table[1] }, @@ -346,6 +347,10 @@ struct dvb_usb_device_properties dib0700 { "Leadtek Winfast DTV Dongle (STK7700P based)", { &dib0700_usb_id_table[8], NULL }, { NULL }, + }, + { "Leadtek Winfast DTV Dongle B (STK7700P based)", + { &dib0700_usb_id_table[11], NULL }, + { NULL }, } } }, { DIB0700_DEFAULT_DEVICE_PROPERTIES, --- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 10:05:13.000000000 +1100 +++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13 10:18:00.000000000 +1100 @@ -148,6 +148,7 @@ #define USB_PID_WINFAST_DTV_DONGLE_COLD 0x6025 #define USB_PID_WINFAST_DTV_DONGLE_WARM 0x6026 #define USB_PID_WINFAST_DTV_DONGLE_STK7700P 0x6f00 +#define USB_PID_WINFAST_DTV_DONGLE_STK7700P_B 0x6f01 #define USB_PID_GENPIX_8PSK_COLD 0x0200 #define USB_PID_GENPIX_8PSK_WARM 0x0201 #define USB_PID_SIGMATEK_DVB_110 0x6610 _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ----- Original Message ----- From: "Antti Palosaari" <crope@iki.fi> To: "ptay1685" <ptay1685@Bigpond.net.au> Cc: <linux-dvb@linuxtv.org> Sent: Monday, March 24, 2008 9:43 AM Subject: Re: [linux-dvb] leadtek dtv dongle ptay1685 wrote: Any news about the new version of the dtv dongle? Still does not work with the latest v4l sources. Anyone know whats happening? Many thanks, Phil T. Can you say what is usb-id of your device? Also lsusb -v could be nice to see. regards Antti -- http://palosaari.fi/ _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb [-- Attachment #1.2: Type: text/html, Size: 29326 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <1206776111.18375.11.camel@localhost.localdomain>]
* Re: [linux-dvb] leadtek dtv dongle lsusb [not found] ` <1206776111.18375.11.camel@localhost.localdomain> @ 2008-03-29 15:57 ` ptay1685 0 siblings, 0 replies; 9+ messages in thread From: ptay1685 @ 2008-03-29 15:57 UTC (permalink / raw) To: linux-dvb; +Cc: Antti Palosaari, k.bannister Here is the info as requested: ___________________________________________________________________________________ [barny@localhost ~]$ /sbin/lsusb -v -d 0413:6f01 Bus 002 Device 003: ID 0413:6f01 Leadtek Research, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0413 Leadtek Research, Inc. idProduct 0x6f01 bcdDevice 0.02 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted Bus 002 Device 002: ID 0413:6f01 Leadtek Research, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0413 Leadtek Research, Inc. idProduct 0x6f01 bcdDevice 0.02 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted ----- Original Message ----- From: "J" <bitumen.surfer@gmail.com> To: "ptay1685" <ptay1685@Bigpond.net.au> Cc: <k.bannister@ieee.org>; "Antti Palosaari" <crope@iki.fi> Sent: Saturday, March 29, 2008 6:35 PM Subject: Re: [linux-dvb] leadtek dtv dongle lsusb > Hi Phil, > > that's a good listing, I haven't had a chance to try Antti's patch yet > (will do so soon), been busy solving AIX headaches. So I can't say if it > fixes the issue's that Keith and myself were experiencing > > However, would you be able to do one thing for me. I noticed a slight > discrepancy between your lsusb listing and mine. While yours appears to > have the same USB id's it does have at least one field different > (bmAttributes). For reference, Keith has published an identical listing > to mine here: > http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022373.html > > Could you run this command (as root) and publish the result. > "/sbin/lsusb -v -d 0413:6f01" > > Thanks, > > John > _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-03-30 2:58 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-23 12:35 [linux-dvb] leadtek dtv dongle ptay1685
2008-03-23 22:43 ` Antti Palosaari
2008-03-26 1:37 ` ptay1685
2008-03-26 2:03 ` John
[not found] ` <002301c88ee9$fd998500$6e00a8c0@barny1e59e583e>
2008-03-26 2:48 ` John
2008-03-26 2:53 ` ptay1685
2008-03-26 4:41 ` Jarryd Beck
2008-03-27 14:05 ` [linux-dvb] leadtek dtv dongle lsusb ptay1685
[not found] ` <1206776111.18375.11.camel@localhost.localdomain>
2008-03-29 15:57 ` ptay1685
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox