[linux-dvb] Regarding LLCI(Low Level CI) HLCI(High Level CI)
Hi, nbsp;nbsp; Can anybody please explain me brief about, Low level CI (LLCI) and High level CI(HLCI) Regards,\Santosh\___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DTV-TER 3028 support?
On 25/04/07, Anders Nordahl [EMAIL PROTECTED] wrote: Will the twinhan 3028 be supported by the mantis driver? Would patching the pciids to use the 3030 settings work? I tried copying the 3030 files, changing them as appropriate. It all compiled fine but fails when trying to talk to the frontend end. It seems like some i2c problem, the frontend module probes for the chip but fails. Sim Regards /Anders ___ 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
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
Finally some promising news for Australian Dual Digital 4 users. Many, many hours later it turns out to be fairly simple and I don't think we need to touch anything other than the tuner but I'm sticking with my hacked code which spews out register values galore until it's confirmed. It would have been nice to get my name in the source code again but I don't think it's warranted. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. There are still some tuning issues. The frequency offset in the xc3028 file needs to be changed from 275 to 225 which will break it for the rest of the world using 7MHz bandwidth so again only AU users please. Also this still doesn't quite map into the actual numbers we need to send to the tuner so you'll find anything below 190MHz may require you to increase the frequency by 100kHz or so to lock properly. Ideally I need 184.5MHz (channel 7) to map to 0x2D98 but instead it's 0x2D90. 212.5MHz (channel 10) goes to 0x3490 which is correct. UHF frequencies may be right out and may even require different firmware but I now know what to look for so we can probably fix it. Hobart digital TV is transmitted on channels 7,8,9A,10 and 11 so I'm somewhat limited in my sampling ability. After having my brain in gigabytes of log files, device driver code and the user manual for the CE6231 (similar to the ZL10353/CE6353 and VERY useful) for the past three days I think I'll take the rest of the evening off. :) Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
Finally some promising news for Australian Dual Digital 4 users. Well done, Roger. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. OK, I'm ready to volunteer. I'm in Adelaide. And if you still need someone to host the file, I can do that (using my Bigpond account). Just let me know what you want done. Petey. Send instant messages to your online friends http://au.messenger.yahoo.com ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
I am a complete newby with this however I have a divco Dual Digital 4 which i would like to make work with Ubuntu. I live in Lismore NSW and if I can be of help please explain what you would like me to do. Ubuntu Edgy does not even recognize the card in dmesg. Cheers Stuart [EMAIL PROTECTED] wrote: --- Michael Krufky [EMAIL PROTECTED] wrote: I am quite sure that you are correct. In my xc-bluebird patch, the zl10353 is configured with the same settings that work with the xc3028 inside the em2880 driver. the zl10353 driver itself *is* working for other devices in Australia using tuners other than the xc3028. All evidence points to the pact that we're missing the correct firmware for use in AU. If you can capture that firmware, try to get the driver to use it, with the code as-is after applying the xc-bluebird patch. If it works, then you'll have some happy list readers. Let me know how it turns out. I just spent the last two hours trying to get the firmware out of the usb logs without success. Everytime I checked the STATUS_0 register on the ZL10353 I ended up with nothing whereas at least with the v3 firmware I had the AGC_LOCK and SYM_LOCK bits set. To cut a long story short I went back to the v3 software and got a full lock coming out of the status registers: 0=0xef 1=0x33 2=0x00 3=0x57. I've also been messing around with the data being sent to the XC3028 so I just have to figure out what I did but it's looking like we may have success. Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ 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
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
Hi Roger, It's great to see some progress with this card. I'm in Perth and would love to help test it. Andrew [EMAIL PROTECTED] wrote: Finally some promising news for Australian Dual Digital 4 users. Many, many hours later it turns out to be fairly simple and I don't think we need to touch anything other than the tuner but I'm sticking with my hacked code which spews out register values galore until it's confirmed. It would have been nice to get my name in the source code again but I don't think it's warranted. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. There are still some tuning issues. The frequency offset in the xc3028 file needs to be changed from 275 to 225 which will break it for the rest of the world using 7MHz bandwidth so again only AU users please. Also this still doesn't quite map into the actual numbers we need to send to the tuner so you'll find anything below 190MHz may require you to increase the frequency by 100kHz or so to lock properly. Ideally I need 184.5MHz (channel 7) to map to 0x2D98 but instead it's 0x2D90. 212.5MHz (channel 10) goes to 0x3490 which is correct. UHF frequencies may be right out and may even require different firmware but I now know what to look for so we can probably fix it. Hobart digital TV is transmitted on channels 7,8,9A,10 and 11 so I'm somewhat limited in my sampling ability. After having my brain in gigabytes of log files, device driver code and the user manual for the CE6231 (similar to the ZL10353/CE6353 and VERY useful) for the past three days I think I'll take the rest of the evening off. :) Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ 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
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
I currently have access to one of these cards in Melbourne for further testing, and can provide another file mirror if necessary. Congrats on the work Roger. [EMAIL PROTECTED] wrote: Finally some promising news for Australian Dual Digital 4 users. Many, many hours later it turns out to be fairly simple and I don't think we need to touch anything other than the tuner but I'm sticking with my hacked code which spews out register values galore until it's confirmed. It would have been nice to get my name in the source code again but I don't think it's warranted. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. There are still some tuning issues. The frequency offset in the xc3028 file needs to be changed from 275 to 225 which will break it for the rest of the world using 7MHz bandwidth so again only AU users please. Also this still doesn't quite map into the actual numbers we need to send to the tuner so you'll find anything below 190MHz may require you to increase the frequency by 100kHz or so to lock properly. Ideally I need 184.5MHz (channel 7) to map to 0x2D98 but instead it's 0x2D90. 212.5MHz (channel 10) goes to 0x3490 which is correct. UHF frequencies may be right out and may even require different firmware but I now know what to look for so we can probably fix it. Hobart digital TV is transmitted on channels 7,8,9A,10 and 11 so I'm somewhat limited in my sampling ability. After having my brain in gigabytes of log files, device driver code and the user manual for the CE6231 (similar to the ZL10353/CE6353 and VERY useful) for the past three days I think I'll take the rest of the evening off. :) Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ 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
Re: [linux-dvb] TT-3200
Oliver Bardenheier (obardenh) wrote: Hello Manu, I don't know if You already have the information for the SkyStar HD, so here's the output from lspci -vvv 01:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Unknown device 1019 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 10 Region 0: Memory at e9cffc00 (32-bit, non-prefetchable) [size=512] need anything else ?? Thanks, wouldn't be needing anything more for now ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Regarding LLCI HLCI
Santosh wrote: Hiii, Can anybody explain me in brief about,LLCI and HLCI. linux/Documentation/dvb/ci.txt should give a precise description ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Satelco DVB-S2 board
laasa wrote: So when I adapt some lines in budget-av.c and budget.h the driver found the board but when using the device (e.g. with _old_ szap) I get undelivering system messages. will have an updated snapshot of the apps soon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TwinhanDTV Cab-CI (mantis vp-2033) remote controller patch
Marko Ristola wrote: Hi, I tested with VDR. VDR responded for the remote control! I used /dev/input/eventX as a VDR remote control device. At least the numerical buttons worked for me. I didn't have to do almost any code changes to make it compilable and workable for me. Only thing was: ln -s /lib/modules/2.6.20-1.2944.fc6 /lib/modules/2.6.20 Cool, nice to know that it works ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DTV-TER 3028 support?
Simeon Walker wrote: On 25/04/07, *Anders Nordahl* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Will the twinhan 3028 be supported by the mantis driver? Would patching the pciids to use the 3030 settings work? No, it wouldn't. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DTV-TER 3028 support?
Anders Nordahl wrote: Will the twinhan 3028 be supported by the mantis driver? Right now unsupported, but status will change in future Would patching the pciids to use the 3030 settings work? Don't think that would help ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TwinhanDTV Cab-CI (mantis vp-2033) remote controller patch
Manu Abraham wrote: Marko Ristola wrote: Hi, I tested with VDR. VDR responded for the remote control! I used /dev/input/eventX as a VDR remote control device. At least the numerical buttons worked for me. I didn't have to do almost any code changes to make it compilable and workable for me. Only thing was: ln -s /lib/modules/2.6.20-1.2944.fc6 /lib/modules/2.6.20 Cool, nice to know that it works Yep. Manu: Any estimations for the CI support? -- Krisu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TwinhanDTV Cab-CI (mantis vp-2033) remote controller patch
Kristian Slavov wrote: Manu Abraham wrote: Marko Ristola wrote: Hi, I tested with VDR. VDR responded for the remote control! I used /dev/input/eventX as a VDR remote control device. At least the numerical buttons worked for me. I didn't have to do almost any code changes to make it compilable and workable for me. Only thing was: ln -s /lib/modules/2.6.20-1.2944.fc6 /lib/modules/2.6.20 Cool, nice to know that it works Yep. Manu: Any estimations for the CI support? Some amount of work do exist now, quite experimental (no descrambling yet) Have been it touch with the chip designer in an area where i am stuck up. There were some restructuring within the organizations, so replies are a bit quite slow. Will post details on it , once through. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Compro VideoMate T100 - saa7130HL + qt1010 + MT352
Hello All, I am interested in support for the Compro VideoMate T100 DVB-T PCI card. The T200, T200A and T300 are already supported, so I hoping that T100 support is already in the works. If it is not, I would like to offer my services to get this device supported. By way of introduction, I am a Software Engineer of some 10 years experience. I have worked on Linux device drivers in the past, but that was some 9 years ago! I feel I have the skills to contribute something useful to this group; I may just need some guidance to get started. Spare time is scarce at the moment, so my contributions may also be slow coming. The chips of interest on the card that I can see are saa7130HL, qt1010 and MT352. All of which seem well supported in the latest kernel, so this should be straight forward enough... The card is auto-detected as the Compro VideoMate T200 by the saa7134 driver in the 2.6.21-rc7 kernel, so I expect that it uses the same vendor/device IDs in the same way that the T200A does. Although not tested, the analog video capture port and even the IR remote control port are found by the current unmodified driver. Any advice or guidance appreciated! Cheers, Dan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
Well done roger, nice work. Let us know when you have a patch. Im interested to see what exactly you did. Is it inappropriate to have the firmware uploaded to this ML? On Thu, 26 Apr 2007, [EMAIL PROTECTED] wrote: Finally some promising news for Australian Dual Digital 4 users. Many, many hours later it turns out to be fairly simple and I don't think we need to touch anything other than the tuner but I'm sticking with my hacked code which spews out register values galore until it's confirmed. It would have been nice to get my name in the source code again but I don't think it's warranted. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. There are still some tuning issues. The frequency offset in the xc3028 file needs to be changed from 275 to 225 which will break it for the rest of the world using 7MHz bandwidth so again only AU users please. Also this still doesn't quite map into the actual numbers we need to send to the tuner so you'll find anything below 190MHz may require you to increase the frequency by 100kHz or so to lock properly. Ideally I need 184.5MHz (channel 7) to map to 0x2D98 but instead it's 0x2D90. 212.5MHz (channel 10) goes to 0x3490 which is correct. UHF frequencies may be right out and may even require different firmware but I now know what to look for so we can probably fix it. Hobart digital TV is transmitted on channels 7,8,9A,10 and 11 so I'm somewhat limited in my sampling ability. After having my brain in gigabytes of log files, device driver code and the user manual for the CE6231 (similar to the ZL10353/CE6353 and VERY useful) for the past three days I think I'll take the rest of the evening off. :) Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ 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
Re: [linux-dvb] 2.6.20 with latest hg drivers and dib0700
So i've been testing various scenarios since my last post, none of which have improved matters to any extent with my Hauppage WinTV Nova-T 500 PCI. I thought I'd go back to latest v4l drivers against 2.6.20, but with these.. nothing locks on MythTV. I'm just getting constant (L_s) Partial Locks on every single channel I have. This is with both dvb-usb-dib0700-01.fw and dvb-usb-dib0700-02-rc1.fw. The only way I can get picture back is to revert to the kernel drivers against either the old firmware or the rc1 firmware (which both work.. for a while). Is there light at the end of the Nova-T 500 PCI card tunnel? Thanks, Chris Chris Murton wrote: Hi, I upgraded to the latest hg drivers against a 2.6.20 kernel for my Nova-T 500 USB and whilst the Oopses went away, the driver now appears to disconnect more frequently than it did before - I'm also seeing more frequent partial locks in MythTV (L_s instead of LMS). Apr 21 10:44:46 basil kernel: usb 2-1: USB disconnect, address 2 Apr 21 10:46:44 basil kernel: dvb-usb: could not submit URB no. 0 - get them all back Apr 21 10:46:44 basil kernel: dvb-usb: error while enabling fifo. Apr 21 10:50:10 basil kernel: dvb-usb: error while stopping stream. I tried the latest firmware that I could find (dvb-usb-dib0700-02-rc1.fw) and that gave me similar results with no noticeable improvement. I'm now trying a different approach, using the 2.6.20 kernel drivers with the latest firmware.. the partial locks have gone away and no disconnects yet but it's only been running for 30 minutes! Also, I don't know if anyone else has had this but when the USB disconnects occur it does not reconnect, but as soon as I reboot something must trigger the USB device to come back on as I can see it being re-probed and brought online as the box is going down - any thoughts? Thanks Chris ___ 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
[linux-dvb] Initial Scan File for Athens - Greece
Hello there, I think this might come in handy to those who are interested in the DVB-T channels by ERT Digital here in Greece. # Initial scan config for Digital DVB-T (Ert) in Athens Greece # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 69000 8MHz 3/4 NONE QAM64 8k 1/8 NONE m0bius ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] begining work on a hauppauge wintv-hvr-1600 driver
Hello DVB list members, I would like to start work or contribute my help for a driver for the Hauppauge HVR-1600 ATSC/NTSC dual tuner. Can someone please tell me if I'm using the right list to discuss development. I wasn't sure if I should be on the DVB list or another V4L list. I found a cx2314x.c file in the CVS tarball i downloaded. It sat in the v4l-dvb-520f7d68c8b4\linux\drivers\media\video directory. Should I use this file as a starting point? Any help would be appreciated. Also I've posted as much information about the card as I could at the mythtv wiki. http://www.mythtv.org/wiki/index.php/Hauppauge_HVR-1600 - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: linux-dvb@linuxtv.org Sent: Thursday, April 26, 2007 5:48:48 AM Subject: linux-dvb Digest, Vol 27, Issue 86 Send linux-dvb mailing list submissions to linux-dvb@linuxtv.org To subscribe or unsubscribe via the World Wide Web, visit http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of linux-dvb digest... Today's Topics: 1. Re: Australia and the DViCO Dual Digital 4 (Petey Leinonen) 2. Re: Australia and the DViCO Dual Digital 4 (Stuart Cosh) 3. Re: Australia and the DViCO Dual Digital 4 (Andrew Kennan) 4. Re: Australia and the DViCO Dual Digital 4 (Peter Fern) 5. Re: TT-3200 (Manu Abraham) 6. Re: Regarding LLCI HLCI (Manu Abraham) 7. Re: Satelco DVB-S2 board (Manu Abraham) 8. Re: TwinhanDTV Cab-CI (mantis vp-2033) remote controller patch (Manu Abraham) 9. Re: Twinhan DTV-TER 3028 support? (Manu Abraham) 10. Re: Twinhan DTV-TER 3028 support? (Manu Abraham) -- Message: 1 Date: Thu, 26 Apr 2007 20:55:11 +1000 (EST) From: Petey Leinonen [EMAIL PROTECTED] Subject: Re: [linux-dvb] Australia and the DViCO Dual Digital 4 To: [EMAIL PROTECTED], linux-dvb@linuxtv.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Finally some promising news for Australian Dual Digital 4 users. Well done, Roger. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. OK, I'm ready to volunteer. I'm in Adelaide. And if you still need someone to host the file, I can do that (using my Bigpond account). Just let me know what you want done. Petey. Send instant messages to your online friends http://au.messenger.yahoo.com -- Message: 2 Date: Thu, 26 Apr 2007 21:51:59 +1000 From: Stuart Cosh [EMAIL PROTECTED] Subject: Re: [linux-dvb] Australia and the DViCO Dual Digital 4 To: [EMAIL PROTECTED], linux-dvb@linuxtv.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed I am a complete newby with this however I have a divco Dual Digital 4 which i would like to make work with Ubuntu. I live in Lismore NSW and if I can be of help please explain what you would like me to do. Ubuntu Edgy does not even recognize the card in dmesg. Cheers Stuart [EMAIL PROTECTED] wrote: --- Michael Krufky [EMAIL PROTECTED] wrote: I am quite sure that you are correct. In my xc-bluebird patch, the zl10353 is configured with the same settings that work with the xc3028 inside the em2880 driver. the zl10353 driver itself *is* working for other devices in Australia using tuners other than the xc3028. All evidence points to the pact that we're missing the correct firmware for use in AU. If you can capture that firmware, try to get the driver to use it, with the code as-is after applying the xc-bluebird patch. If it works, then you'll have some happy list readers. Let me know how it turns out. I just spent the last two hours trying to get the firmware out of the usb logs without success. Everytime I checked the STATUS_0 register on the ZL10353 I ended up with nothing whereas at least with the v3 firmware I had the AGC_LOCK and SYM_LOCK bits set. To cut a long story short I went back to the v3 software and got a full lock coming out of the status registers: 0=0xef 1=0x33 2=0x00 3=0x57. I've also been messing around with the data being sent to the XC3028 so I just have to figure out what I did but it's looking like we may have success. Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Message: 3 Date: Thu, 26 Apr 2007 20:13:04 +0800 From: Andrew Kennan
Re: [linux-dvb] begining work on a hauppauge wintv-hvr-1600 driver
Dan Morgan wrote: Hello DVB list members, I would like to start work or contribute my help for a driver for the Hauppauge HVR-1600 ATSC/NTSC dual tuner. Can someone please tell me if I'm using the right list to discuss development. I wasn't sure if I should be on the DVB list or another V4L list. I found a cx2314x.c file in the CVS tarball i downloaded. It sat in the v4l-dvb-520f7d68c8b4\linux\drivers\media\video directory. Should I use this file as a starting point? Any help would be appreciated. Also I've posted as much information about the card as I could at the mythtv wiki. http://www.mythtv.org/wiki/index.php/Hauppauge_HVR-1600 Support for the cx23418 mpeg encoder / DVB/ATSC pass-thru / pci bridge chipset is already underway. It is a work in progress, and not yet ready. The cx2341x module will be used as part of this driver. Currently, the cx2341x module is mainly used for the mpeg controls. This module, in addition to some glue code, already works for the cx23417, but additional work is needed for the pci bridge functionality. An announcement will be made when the project has matured enough for testing. I'm not the guy working on this, in case you're wondering. ...that's all I can say about it right now. Regards, Michael Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVBWorld DVB-S 2102 USB2.0 and clones
I have Acorp DS120, which is DVBWorld DVB-S 2102 USB2.0 clone (USB ID 04B4:2102). The card is pretty like Opera, but without Xilinx chip. I think firmware already contained in Atmel903 24c02n chip, which i see on board. So, maybe someone knows, how to check it. I have UsbSniff log and photos of my card. I'd like to see logs and photos of Opera PCB to compare. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb After some time spent with Usbsnoop.log , I extract firmware from windows driver for DVBWorld DVB-S 2102 USB2.0 (DVBUSBS2102.sys). It appears 8192 bytes long with many AA's at end - like Pvrusb2 firmware for Cypress CPU. I replaced opera1.fw with extracted by me firmware and changed USB ID in opera1.c. Now I get error: dvb-usb: firmware download failed at 8134 with -22 Why was that? ...stripped -- URB_FUNCTION_VENDOR_DEVICE: TransferFlags = (USBD_TRANSFER_DIRECTION_OUT, ~USBD_SHORT_TRANSFER_OK) TransferBufferLength = 0001 TransferBuffer = f88cd9d8 TransferBufferMDL= : 01 UrbLink = RequestTypeReservedBits = Request = 00a0 Value = e600 Index = [628 ms] UsbSnoop - MyInternalIOCTLCompletion(f87f3db0) : fido=, Irp=81e63e70, Context=82087748, IRQL=2 [628 ms]URB 6 coming back -- URB_FUNCTION_CONTROL_TRANSFER: PipeHandle = 81efd570 TransferFlags= 000a (USBD_TRANSFER_DIRECTION_OUT, USBD_SHORT_TRANSFER_OK) TransferBufferLength = 0001 TransferBuffer = f88cd9d8 TransferBufferMDL= 820f83c0 UrbLink = SetupPacket = : 40 a0 00 e6 00 00 01 00 SET RESET BIT ASSERTS RESET (HALT CPU) [628 ms] UsbSnoop - DispatchAny(f87f2610) : IRP_MJ_INTERNAL_DEVICE_CONTROL [628 ms] UsbSnoop - MyDispatchInternalIOCTL(f87f3e80) : fdo=817067c0, Irp=81e63e70, IRQL=0 [628 ms]URB 7 going down -- URB_FUNCTION_VENDOR_DEVICE: TransferFlags = (USBD_TRANSFER_DIRECTION_OUT, ~USBD_SHORT_TRANSFER_OK) TransferBufferLength = 0040 TransferBuffer = f87fe7c0 TransferBufferMDL= : 02 08 5d 00 01 02 02 03 03 04 04 05 05 12 07 bc 0010: 02 0c 59 02 07 b8 c0 e0 c0 83 c0 82 90 e6 b5 e0 0020: 44 01 f0 d2 01 12 0a 09 74 01 f0 d0 82 d0 83 d0 0030: e0 32 32 02 00 4e 8f 31 8d 32 8a 33 8b 34 d3 22 UrbLink = RequestTypeReservedBits = Request = 00a0 Value = Index = [629 ms] UsbSnoop - MyInternalIOCTLCompletion(f87f3db0) : fido=, Irp=81e63e70, Context=81f31bc8, IRQL=2 [629 ms]URB 7 coming back -- URB_FUNCTION_CONTROL_TRANSFER: PipeHandle = 81efd570 TransferFlags= 000a (USBD_TRANSFER_DIRECTION_OUT, USBD_SHORT_TRANSFER_OK) TransferBufferLength = 0040 TransferBuffer = f87fe7c0 TransferBufferMDL= 820f83c0 UrbLink = SetupPacket = : 40 a0 00 00 00 00 40 00 START DOWNLOADING FIRMWARE TO ADDR= CHUNK LENGTH=40 ...stripped___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] 2.6.20 with latest hg drivers and dib0700
The disconnect problem is the exact same problem I keep getting. I've tried to ask on the linux-usb lists, but I was told that i had faulty hardware if I keep getting disconnects - I don't think so as a lot of us Nova-T users seem to be getting the exact same disconnect problem. Hope someone comes up with a fix soon, or at least can help us figure out what's causing it! Cheers, Mike Chris Murton wrote: So i've been testing various scenarios since my last post, none of which have improved matters to any extent with my Hauppage WinTV Nova-T 500 PCI. I thought I'd go back to latest v4l drivers against 2.6.20, but with these.. nothing locks on MythTV. I'm just getting constant (L_s) Partial Locks on every single channel I have. This is with both dvb-usb-dib0700-01.fw and dvb-usb-dib0700-02-rc1.fw. The only way I can get picture back is to revert to the kernel drivers against either the old firmware or the rc1 firmware (which both work.. for a while). Is there light at the end of the Nova-T 500 PCI card tunnel? Thanks, Chris Chris Murton wrote: Hi, I upgraded to the latest hg drivers against a 2.6.20 kernel for my Nova-T 500 USB and whilst the Oopses went away, the driver now appears to disconnect more frequently than it did before - I'm also seeing more frequent partial locks in MythTV (L_s instead of LMS). Apr 21 10:44:46 basil kernel: usb 2-1: USB disconnect, address 2 Apr 21 10:46:44 basil kernel: dvb-usb: could not submit URB no. 0 - get them all back Apr 21 10:46:44 basil kernel: dvb-usb: error while enabling fifo. Apr 21 10:50:10 basil kernel: dvb-usb: error while stopping stream. I tried the latest firmware that I could find (dvb-usb-dib0700-02-rc1.fw) and that gave me similar results with no noticeable improvement. I'm now trying a different approach, using the 2.6.20 kernel drivers with the latest firmware.. the partial locks have gone away and no disconnects yet but it's only been running for 30 minutes! Also, I don't know if anyone else has had this but when the USB disconnects occur it does not reconnect, but as soon as I reboot something must trigger the USB device to come back on as I can see it being re-probed and brought online as the box is going down - any thoughts? Thanks Chris ___ 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 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVBWorld DVB-S 2102 USB2.0 and clones
I have Acorp DS120, which is DVBWorld DVB-S 2102 USB2.0 clone (USB ID 04B4:2102). The card is pretty like Opera, but without Xilinx chip. I think firmware already contained in Atmel903 24c02n chip, which i see on board. So, maybe someone knows, how to check it. I have UsbSniff log and photos of my card. I'd like to see logs and photos of Opera PCB to compare. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb After some time spent with Usbsnoop.log , I extract firmware from windows driver for DVBWorld DVB-S 2102 USB2.0 (DVBUSBS2102.sys). It appears 8192 bytes long with many AA's at end - like Pvrusb2 firmware for Cypress CPU. I replaced opera1.fw with extracted by me firmware and changed USB ID in opera1.c. Now I get error: dvb-usb: firmware download failed at 8134 with -22 Why was that? The same thing with ttusb2 driver. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] fmd1216me integration
Here's my latest patch for fmd1216me integration into dvb-pll. It's little changed from when I posted it three weeks ago, except for cxusb which is now part of the patch. I'm going to try to get it into mainline soon for the 2.6.22 window, so if there are comments now is the time. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] fmd1216me integration (fwd)
Include the patch this time
-- Forwarded message --
Date: Thu, 26 Apr 2007 12:02:59 -0700 (PDT)
From: Trent Piepho [EMAIL PROTECTED]
To: Linux DVB linux-dvb@linuxtv.org
Cc: Hartmut Hackmann [EMAIL PROTECTED]
Subject: fmd1216me integration
Here's my latest patch for fmd1216me integration into dvb-pll. It's little
changed from when I posted it three weeks ago, except for cxusb which is
now part of the patch.
I'm going to try to get it into mainline soon for the 2.6.22 window, so if
there are comments now is the time.
-
Integrate all users of the fmd1216 tuner with dvb-pll
From: Trent Piepho [EMAIL PROTECTED]
Enhance the dvb-pll definition of the fmd1216 tuner by adding an init sequence
and a sleep sequence.
The init sequence sets the AGC control register to 0xa0, selecting the fast
time constant and 112 dBuV take-over point. This the recommended value for
DVB-T operation.
The sleep sequence sets bit P4 (which is believed to turn the analog
demodulator on), turns off the tuning voltage, and sets the AGC control
register to 0x60 (external AGC voltage, the recommended value for analog
operation).
The existing dvb-pll users in the cx88 driver, listed below, will gain these
init and sleep sequences.
CX88_BOARD_HAUPPAUGE_HVR1100Hauppauge WinTV-HVR1100 DVB-T/Hybrid
CX88_BOARD_HAUPPAUGE_HVR1100LP Hauppauge WinTV-HVR1100 DVB-T/Hybrid (Low Profi
CX88_BOARD_WINFAST_DTV2000H WinFast DTV2000 H
CX88_BOARD_HAUPPAUGE_HVR3000Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DV
CX88_BOARD_HAUPPAUGE_HVR1300Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encod
This non-dvb-pll user in the cx88 driver should only gain the sleep sequence,
as it already had an equivalent init sequence. The non-dvb-pll code for this
user is removed.
X88_BOARD_DNTV_LIVE_DVB_T_PRO digitalnow DNTV Live! DVB-T Pro
In these saa7134 driver, these non-dvb-pll users are converted to use dvb-pll:
SAA7134_BOARD_MD7134Medion 7134
SAA7134_BOARD_ASUS_EUROPA2_HYBRID Asus Europa2 OEM
The saa7134 functions philips_fmd1216_tuner_init(),
philips_fmd1216_tuner_sleep(), and philips_fmd1216_tuner_set_params() are
deleted and the dvb-pll versions are used.
This should result in equivalent sleep, init, and tuning sequences being sent
to the tuner.
For the cxusb driver, only one board is effected:
USB_PID_MEDION_MD95700 Medion MD95700
This board used dvb_usb_tuner_init_i2c() and dvb_usb_tuner_set_params_i2c()
for init and tuning, respectively. These functions are effectively the same
as the dvb-pll versions. They call a tuner pass control function defined at
the dvb-usb level, but this does not matter, as this card does not have a
tuner pass control function (only the dib3000mb does). This board will gain
the sleep sequence, while init and tuning should be unchanged.
Signed-off-by: Trent Piepho [EMAIL PROTECTED]
diff --git a/linux/drivers/media/dvb/dvb-usb/cxusb.c
b/linux/drivers/media/dvb/dvb-usb/cxusb.c
--- a/linux/drivers/media/dvb/dvb-usb/cxusb.c
+++ b/linux/drivers/media/dvb/dvb-usb/cxusb.c
@@ -354,14 +354,8 @@ static struct mt352_config cxusb_mt352_c
/* Callbacks for DVB USB */
static int cxusb_fmd1216me_tuner_attach(struct dvb_usb_adapter *adap)
{
- u8 bpll[4] = { 0x0b, 0xdc, 0x9c, 0xa0 };
- adap-pll_addr = 0x61;
- memcpy(adap-pll_init, bpll, 4);
- adap-pll_desc = dvb_pll_fmd1216me;
-
- adap-fe-ops.tuner_ops.init = dvb_usb_tuner_init_i2c;
- adap-fe-ops.tuner_ops.set_params = dvb_usb_tuner_set_params_i2c;
-
+ dvb_attach(dvb_pll_attach, adap-fe, 0x61, adap-dev-i2c_adap,
+ dvb_pll_fmd1216me);
return 0;
}
diff --git a/linux/drivers/media/dvb/frontends/dvb-pll.c
b/linux/drivers/media/dvb/frontends/dvb-pll.c
--- a/linux/drivers/media/dvb/frontends/dvb-pll.c
+++ b/linux/drivers/media/dvb/frontends/dvb-pll.c
@@ -38,6 +38,12 @@
0x50 = AGC Take over point = 103 dBuV */
static u8 tua603x_agc103[] = { 2, 0x80|0x40|0x18|0x06|0x01, 0x00|0x50 };
+/* 0x04 = 166.67 kHz divider
+
+ 0x80 = AGC Time constant 50ms Iagc = 9 uA
+ 0x20 = AGC Take over point = 112 dBuV */
+static u8 tua603x_agc112[] = { 2, 0x80|0x40|0x18|0x04|0x01, 0x80|0x20 };
+
struct dvb_pll_desc dvb_pll_thomson_dtt7579 = {
.name = Thomson dtt7579,
.min = 17700,
@@ -282,6 +288,8 @@ struct dvb_pll_desc dvb_pll_fmd1216me =
.max = 85800,
.iffreq= 36125000,
.setbw = fmd1216me_bw,
+ .initdata = tua603x_agc112,
+ .sleepdata = (u8[]){ 4, 0x9c, 0x60, 0x85, 0x54 },
.count = 7,
.entries = {
{ 14387, 17, 0xbc, 0x41 },
diff --git a/linux/drivers/media/video/cx88/cx88-dvb.c
b/linux/drivers/media/video/cx88/cx88-dvb.c
--- a/linux/drivers/media/video/cx88/cx88-dvb.c
+++ b/linux/drivers/media/video/cx88/cx88-dvb.c
@@ -224,64 +224,6 @@ static int dntv_live_dvbt_pro_demod_init
return 0;
}
-static int
Re: [linux-dvb] 2.6.20 with latest hg drivers and dib0700
I´ve been asking this before, but ... Does anyone know if the problem occurs in windows to or is it a linux exclusive, if it´s ok in windows it´s fixabel. Also does anyone know if the hauppage driver includes it own, as in special USB controller driver for the onboard usb controller ? Someone mentioned that the revision of the usb controller on the card is very old, maybe it has a hardware bug that needs special attention ? /Henrik On 4/26/07, Mike H [EMAIL PROTECTED] wrote: The disconnect problem is the exact same problem I keep getting. I've tried to ask on the linux-usb lists, but I was told that i had faulty hardware if I keep getting disconnects - I don't think so as a lot of us Nova-T users seem to be getting the exact same disconnect problem. Hope someone comes up with a fix soon, or at least can help us figure out what's causing it! Cheers, Mike Chris Murton wrote: So i've been testing various scenarios since my last post, none of which have improved matters to any extent with my Hauppage WinTV Nova-T 500 PCI. I thought I'd go back to latest v4l drivers against 2.6.20, but with these.. nothing locks on MythTV. I'm just getting constant (L_s) Partial Locks on every single channel I have. This is with both dvb-usb-dib0700-01.fw and dvb-usb-dib0700-02-rc1.fw. The only way I can get picture back is to revert to the kernel drivers against either the old firmware or the rc1 firmware (which both work.. for a while). Is there light at the end of the Nova-T 500 PCI card tunnel? Thanks, Chris Chris Murton wrote: Hi, I upgraded to the latest hg drivers against a 2.6.20 kernel for my Nova-T 500 USB and whilst the Oopses went away, the driver now appears to disconnect more frequently than it did before - I'm also seeing more frequent partial locks in MythTV (L_s instead of LMS). Apr 21 10:44:46 basil kernel: usb 2-1: USB disconnect, address 2 Apr 21 10:46:44 basil kernel: dvb-usb: could not submit URB no. 0 - get them all back Apr 21 10:46:44 basil kernel: dvb-usb: error while enabling fifo. Apr 21 10:50:10 basil kernel: dvb-usb: error while stopping stream. I tried the latest firmware that I could find (dvb-usb-dib0700-02-rc1.fw) and that gave me similar results with no noticeable improvement. I'm now trying a different approach, using the 2.6.20 kernel drivers with the latest firmware.. the partial locks have gone away and no disconnects yet but it's only been running for 30 minutes! Also, I don't know if anyone else has had this but when the USB disconnects occur it does not reconnect, but as soon as I reboot something must trigger the USB device to come back on as I can see it being re-probed and brought online as the box is going down - any thoughts? Thanks Chris ___ 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 ___ 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
[linux-dvb] udev problem
All,
I have a problem whereby I need to pin a specific PCI card (slot) to a dvb
node, otherwise it totally messes up my machine when a historic DVB-S node
becomes a DVB-T node or vice versa.
I have been playing with udev and have found how to identify cards etc. But
getting the (NAME) rule right is confusing me. I am running Fedora Core 5
and have the following standard rule in /etc/udev/rules.d/50-udev.rules -
SUBSYSTEM==dvb, PROGRAM=/bin/sh -c 'K=%k; K=$${K#dvb}; printf
dvb/adapter%%i/%%s $${K.*} $${K#*.}', NAME=%c, MODE=0660
The closest I got to getting things working was by substituting
dvb/adapter%%i/ with dvb/adapter5/, thus forcing the adapter to
/dev/dvb/adapter5, rule below -
BUS==pci, ID==:01:06.0, SYSFS{device}==0x7146,
SYSFS{vendor}==0x1131, PROGRAM=/bin/sh -c 'K=%k; K=$${K#dvb}; printf
dvb/adapter5/%%s $${K.*} $${K#*.}', NAME=%c, MODE=0660
Unfortunately that changed the tree structure from -
/dev/dvb/
`-- adapter5
|-- ca0
|-- demux0
|-- dvr0
|-- frontend0
`-- net0
To -
/dev/dvb/
`-- adapter5
|-- 0dvb
| `-- adapter5
| |-- ca0
| |-- demux0
| |-- dvr0
| |-- frontend0
| `-- net0
`-- event3dvb
`-- adapter5
`-- event3
Can anyone please advise on what the rule should look like?
Thanks in advance.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Small patch into opera1.c to make FPGA firmware load visible
Hi,
I thinks this patch should clean many problems with firmware upload when
device doesn't swith to warm state:
--- ./v4l-dvb/linux/drivers/media/dvb/dvb-usb/opera1.c 2007-04-25
22:29:52.0 +0200
+++ ./v4l-dvb/linux/drivers/media/dvb/dvb-usb/opera1.c 2007-04-26
17:58:24.0 +0200
@@ -448,7 +448,7 @@
u8 *b, *p;
int ret = 0, i;
u8 testval;
- info(start downloading fpga firmware);
+ printk(FPGA firmware download starts...\n);
if ((ret = request_firmware(fw, filename, dev-dev)) != 0) {
err(did not find the firmware file. (%s)
Signed-off-by: Michal CIJOML Semler [EMAIL PROTECTED]
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: Belkin USBView II
The process of capabilities discovery includes turning on isoc and the saa711x, and this results in a bunch of non-valid data packets David, you have load SAA7115 instead of the older SAA711X module right? I suspect the problem has shifted to where the chip is being asked to send more then the endpoint's actual packet size, or something in that area. Red herring? The packet size is this... #define USBVISION_MAX_ISOC_PACKET_SIZE 959 // NT1003 Specs Document says 1023 . It's true, the NT100x spec docs say 1023 is the max, but the snoopy logfiles did say only 959 with any device which we had a snoppy log file from. Try changing this to the 895 and see. I don't think it's going to help. But we should try it and see. As you did core_debug=36 (12 (DBG_ISOC) + 15 (DBG_FUNC)) you should see it. If not, this is a bug :) Do you have some windows usbsnoop dumps ? If so, we could analyze them to see which alternate is selected and which packet size is selected. The other devices have the similar packet size. Here is the URL. Looking through memory lane right now. http://sourceforge.net/forum/message.php?msg_id=3523937 Here is an example of some digging into the usb code. Updated to kernel 2.6.14. Still get the -90 error. This is with usbvision 0.9.3 dated November. Looking in the code for urb.c it looks like all the ways of getting that error have to do with the size of the transfer_buffer. The size being passed is 30688 bytes (32*959). I notice the max size is 0x7FF if (dev-speed == USB_SPEED_HIGH). This hardware only has USB1.1 so I am not sure if that has anything to do with it. The max limit on ISOC packet size being enforced by urb.c appears to come from hub.c doing some query against the hub. In my case the hub is the one on the VIA motherboard. It was working fine last year with a 2.4 kernel. So as an experiment I just commented out the check in the usb_submit_urb routine in urb.c. It worked! No more -90 errors and I can grab frames with videodog. But I have no idea about the long term viability of this quick fix. I don't have a set of 2.4 sources to compare with. The device did work in kernel 2.4.x and seemed to break in 2.6.x. Dwaine - Original Message From: David Warman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Dwaine Garden [EMAIL PROTECTED]; Thierry MERLE [EMAIL PROTECTED] Sent: Thursday, April 26, 2007 2:40:24 PM Subject: Re: Belkin USBView II Hi Thierry, No, that bit of code is correct, so my problem is not there. I think it is elsewhere entirely. The process of capabilities discovery includes turning on isoc and the saa711x, and this results in a bunch of non-valid data packets. I turned on camorama's debug facility also, and it is complaining about VIDEOCGCAPS failing. IIRC, that is a v4l1 ioctls request, and the current system I am building is v4l2. I thought there was a compatibility layer, but it seems not to be working for camorama. Or for vlc, which I just downloaded and looks for v4l-vdev=/dev/video0, and complains v4l demuxerls -al error: cannot get capabilities (inval;id argument). I am looking for another imager program I can trust. gqcam connects but displays all 0's for camera details, as if it also failed the caps collection but decided to run with the empty struct instead of failing out. xawtv doesn't run. I am about to test with ffmpeg + ffserver; tho that is a more complex setup I trust ffmpeg more. I have the feeling that once I get connected properly, the system will work. As always , thanks for your continuing help on this project. It looks like when I am done I may have a patch or two to submit. Regards, David Warman On Apr 25, 2007, at 9:56 PM, Thierry MERLE wrote: Hello David, David Warman a écrit : Implemented the changes mentioned, made a little bit of progress. Now, running camorama with the modprobe usbvision debug flags set (video_debug=4 core_debug=36), I get a stream of full size packets with bad status (len=895, status=FFB5 - EOVERFLOW?), then a few null packets and then about 42 empty packets before power off completes and camorama abandons the attempt to start up. More than the dmesg buffer can hold, so I do not have the start-up end of the trace. Earlier, in the older v4l1 code, I noticed that the value from the USBVISION_ALTER_REG register was used to compute the packet size for the isoch urbs, but that the computation resulted in a packet size 64 bytes too large (regValue needed -- to get the matching value) when checked against the max packet size reported in the endpoint alternate selected. That particular line of code is no longer in usbvision_init_isoc, and I am hunting down the allocation code now. I suspect the problem has shifted to where the chip is being asked to send more then the endpoint's actual packet size, or something in that area. Red herring? Any comments and/or
