[linux-dvb] dvb_register_adapter vs dvb_register_device
Hi all, Does anyone of you know what's the difference between dvb_register_adapter and dvb_register_device? I can't really figure it out... Regards, Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] wintv nova-t stick, dib0700 and remote controllers..
No answer? Please could someone tell me if is it dangerous to call dib0700_rc_setup (from dib0700core.c) every 100ms to reset remote control data? Do you know any other method to reset data about last key received from the ir sensor? Thanks Filippo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] wintv nova-t stick, dib0700 and remote controllers..
I'm asking this because calling dib0700_rc_setup after each keypress poll resets the ir data into the device to 0 0 0 0. What I'd like to know since I know almost nothing about dvb devices if is this going to someway damage my device if called each 150ms (period of the poll). If not I'll write a patch to support some of my remotes as well repeated keys events as soon I'll have some spare time. Does any of you know a different method to erase last received data from the device? 2008/2/14, Filippo Argiolas [EMAIL PROTECTED]: No answer? Please could someone tell me if is it dangerous to call dib0700_rc_setup (from dib0700core.c) every 100ms to reset remote control data? Do you know any other method to reset data about last key received from the ir sensor? Thanks Filippo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nova-T-500 disconnect issues
Hi. I have been following the discussion regarding the mt2060 I2C read / write failed errors. I am running Ubuntu and get the same behaviour since I upgraded to the latest kernel (2.6.24.1) to resolve some wireless driver issues I was having. When I was running the standard Ubuntu kernel (2.6.22-14-generic) I never had the disconnect issues in 3 or 4 months of 24/7 usage. This was using the latest v4l- dvb sources as per the wiki. Perhaps this would suggest that the error is not with the dib0700 driver but elsewhere? So my dilemma is do I have a constant wireless connection but a dvb driver that drops out or a constant dvb driver with a wireless connection that drops out?! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing
Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: Hi, folks In my personal repository: http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/ you will find a driver that supports this card, DVB-T and DVB-S It might also work for - one section of the MD8800 - similar boards based on saa713x, tda10086, tda826x, isl6405 The board will show up as MD8800. According to Hermann, the configurations for analog TV and DVB-T are identical. If you want to use the board with DVB-S, you will need to load the saa7134-dvb module with the option use_frontend=1. The default 0 is DVB-T. For those who got the board from a second source: don't forget to connect the 12v (the floppy supply) connector. I don't have a dish, so i depend on your reports. To get the MD8800 running, i need a volunteer who does the testing for me. He should be able to apply patches, compile the driver and read kernel logs. Good luck Hartmut Hartmut, great job, thank you very much! Can't wait, result of a first voltage measurement on the md8800 Quad. The upper LNB connector associated to the second saa7134 16be:0008 device has correct voltage. Since my stuff is not in the original green PCI slot and I have only the first 16be:0007 device active, can't test much more for now here. People with the card in the original Medion PC could set options saa7134-dvb use_frontend=1 debug=1 in /etc/modprobe.conf and then do depmod -a. The Syntek v4l usb stkwebcam still produces a compilation error and needs to be disabled in make xconfig or something else. After make it is best to do make rmmod on top of your v4l-dvb-experimental first. Those new to the v4l-dvb development stuff might do also make rminstall and then check that no *.ko is left in /lib/modules/kernel_in_use/kernel/drivers/media/* Especially the old video_buf.ko in the video dir needs to be removed. Check with ls -R |grep .ko and then make install. Now I suggest to modprobe saa7134 card=117,96 In that case DVB-T is supported on the lower antenna connector and first adapter and DVB-S on the upper LNB connector and second adapter. Or to have it simple, it is safe to make rmmod and modprobe saa7134 card=5,96 tuner=54,54 This way on the first device is only analog TV enabled, don't forget to use it first to have good DVB-T reception later anyway, and the only frontend is the DVB-S one in question for testing. On the CTX948 voltage is OK AND Tuning to: Camera Deputati / autocount: 22 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 11804000 v 2750 inv:2 fecH:2 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 373 ms pipe opened xine pipe opened /root/.kaxtv.ts Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: Dubai Sports-1 / autocount: 23 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 11747000 h 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 18V, hiband (index 3) DiSEqC: e0 10 38 f3 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 374 ms xine pipe opened /root/.kaxtv1.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: ARD Das Erste / autocount: 24 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 11604000 h 2750 inv:2 fecH:5 DiSEqC: switch pos 0, 18V, loband (index 1) DiSEqC: e0 10 38 f2 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 379 ms xine pipe opened /root/.kaxtv.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: Abu Dhabi Sport / autocount: 25 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 12577000 h 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 18V, hiband (index 3) DiSEqC: e0 10 38 f3 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 379 ms xine pipe opened /root/.kaxtv1.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: BBC World / autocount: 26 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 12596000 v 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 ... LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 560 ms pipe opened xine pipe opened /root/.kaxtv.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: All Music / autocount: 38 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 10949000 v 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 13V, loband (index 0) DiSEqC: e0 10 38 f0 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 378 ms xine pipe opened /root/.kaxtv.ts pipe opened Congratulations! Cheers, Hermann ___ linux-dvb
Re: [linux-dvb] wintv nova-t stick, dib0700 and remote controllers..
On Thu, 2008-02-14 at 10:39 +0100, Filippo Argiolas wrote: I'm asking this because calling dib0700_rc_setup after each keypress poll resets the ir data into the device to 0 0 0 0. What I'd like to know since I know almost nothing about dvb devices if is this going to someway damage my device if called each 150ms (period of the poll). If not I'll write a patch to support some of my remotes as well repeated keys events as soon I'll have some spare time. Does any of you know a different method to erase last received data from the device? 2008/2/14, Filippo Argiolas [EMAIL PROTECTED]: No answer? Please could someone tell me if is it dangerous to call dib0700_rc_setup (from dib0700core.c) every 100ms to reset remote control data? Do you know any other method to reset data about last key received from the ir sensor? Thanks Filippo, From a user point of view I can tell you that this topic interests me and that the tread is flagged in my email client. As for the technical side, I'm a clueless human being about this and can't help. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T-500 disconnect issues
On 14/02/2008, General [EMAIL PROTECTED] wrote: Hi. I have been following the discussion regarding the mt2060 I2C read / write failed errors. I am running Ubuntu and get the same behaviour since I upgraded to the latest kernel (2.6.24.1) to resolve some wireless driver issues I was having. When I was running the standard Ubuntu kernel (2.6.22-14-generic) I never had the disconnect issues in 3 or 4 months of 24/7 usage. This was using the latest v4l- dvb sources as per the wiki. Perhaps this would suggest that the error is not with the dib0700 driver but elsewhere? So my dilemma is do I have a constant wireless connection but a dvb driver that drops out or a constant dvb driver with a wireless connection that drops out?! Ah but you can get the latest wireless drivers for your current kernel: http://linuxwireless.org/en/users/Download Sim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T-500 disconnect issues
I will definently look in to this and will try to upgrade the kernel. (will prob. screw it up but anyways). Ps. Got a good kernel upgrade-how to for 7.10 ? Ds. On 2/14/08, Simeon Walker [EMAIL PROTECTED] wrote: On 14/02/2008, General [EMAIL PROTECTED] wrote: Hi. I have been following the discussion regarding the mt2060 I2C read / write failed errors. I am running Ubuntu and get the same behaviour since I upgraded to the latest kernel (2.6.24.1) to resolve some wireless driver issues I was having. When I was running the standard Ubuntu kernel (2.6.22-14-generic) I never had the disconnect issues in 3 or 4 months of 24/7 usage. This was using the latest v4l- dvb sources as per the wiki. Perhaps this would suggest that the error is not with the dib0700 driver but elsewhere? So my dilemma is do I have a constant wireless connection but a dvb driver that drops out or a constant dvb driver with a wireless connection that drops out?! Ah but you can get the latest wireless drivers for your current kernel: http://linuxwireless.org/en/users/Download Sim ___ 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] WinTV-CI from Hauppauge
Am Donnerstag 20 Dezember 2007 20:20:46 schrieb Steven Toth: They won't be able to help, I can - but not for a few weeks. I'm expecting to release public USB protocol information during Jan 08 which would allow a GPL driver to be written. Right now I have nothing to give you. If you feel adventurous, feel free to start now by reverse engineering the protocol with a windows software USB sniffer, it won't be wasted work. The device is Cypress FX2 based (which Linux has lots of examples for) and it loads custom firmware (which Linux has lots of examples of) apart from that I think the protocol is very simple. How to integrate it with the kernel s/w demux would be an interesting debate. Let me know if I can help. Steve, what happened to this? Thanks, Julian ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T-500 disconnect issues
El Jueves, 14 de Febrero de 2008, Patrik Hansson escribió: I will definently look in to this and will try to upgrade the kernel. (will prob. screw it up but anyways). Ps. Got a good kernel upgrade-how to for 7.10 ? Ds. On 2/14/08, Simeon Walker [EMAIL PROTECTED] wrote: On 14/02/2008, General [EMAIL PROTECTED] wrote: Hi. I have been following the discussion regarding the mt2060 I2C read / write failed errors. I am running Ubuntu and get the same behaviour since I upgraded to the latest kernel (2.6.24.1) to resolve some wireless driver issues I was having. When I was running the standard Ubuntu kernel (2.6.22-14-generic) I never had the disconnect issues in 3 or 4 months of 24/7 usage. This was using the latest v4l- dvb sources as per the wiki. Perhaps this would suggest that the error is not with the dib0700 driver but elsewhere? So my dilemma is do I have a constant wireless connection but a dvb driver that drops out or a constant dvb driver with a wireless connection that drops out?! I also have more disconnects with kernel 2.6.24. I found that disabling in kernel config the option: USB selective suspend/resume and wakeup (EXPERIMENTAL) -CONFIG_USB_SUSPEND have impact in the disconnects, althought I don't know exactily why, but with this option the Nova-T 500 hubs are constantly supend-resume. Jose Alberto Ah but you can get the latest wireless drivers for your current kernel: http://linuxwireless.org/en/users/Download Sim ___ 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] SkyStar rev 2.8A driver?
Hi, I searched linuxtv.org mailing list archive about SkyStar2 rev2.8A driver, or any suggestion, but I found nothing. The 2.6.22 kernel initialize B2C2 chip itself, but it could not identify the frontend for card. The chips used in this card for frontend are conexant cx24123 and cx24113 . I tried to load cx24123 module exists in the kernel, but later I found it is not defined for b2c2-flexcop module to use it, and hence it is not useful. Could anybody help me? j. Jikman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing
Hi, Am Donnerstag, den 14.02.2008, 12:01 +0100 schrieb hermann pitton: Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: Hi, folks In my personal repository: http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/ you will find a driver that supports this card, DVB-T and DVB-S It might also work for - one section of the MD8800 - similar boards based on saa713x, tda10086, tda826x, isl6405 The board will show up as MD8800. According to Hermann, the configurations for analog TV and DVB-T are identical. If you want to use the board with DVB-S, you will need to load the saa7134-dvb module with the option use_frontend=1. The default 0 is DVB-T. For those who got the board from a second source: don't forget to connect the 12v (the floppy supply) connector. I don't have a dish, so i depend on your reports. To get the MD8800 running, i need a volunteer who does the testing for me. He should be able to apply patches, compile the driver and read kernel logs. Good luck Hartmut Hartmut, great job, thank you very much! Can't wait, result of a first voltage measurement on the md8800 Quad. The upper LNB connector associated to the second saa7134 16be:0008 device has correct voltage. Since my stuff is not in the original green PCI slot and I have only the first 16be:0007 device active, can't test much more for now here. back on the machine and thinking about it twice ... The Quad works for me as well on the upper LNB connector, despite of that I previously used the lower one successfully with RF loopthrough from an external receiver. So, in case of the Quad, just let it be autodetected and try on the first adapter and upper LNB connector. Even more fun :) Cheers, Hermann People with the card in the original Medion PC could set options saa7134-dvb use_frontend=1 debug=1 in /etc/modprobe.conf and then do depmod -a. The Syntek v4l usb stkwebcam still produces a compilation error and needs to be disabled in make xconfig or something else. After make it is best to do make rmmod on top of your v4l-dvb-experimental first. Those new to the v4l-dvb development stuff might do also make rminstall and then check that no *.ko is left in /lib/modules/kernel_in_use/kernel/drivers/media/* Especially the old video_buf.ko in the video dir needs to be removed. Check with ls -R |grep .ko and then make install. Now I suggest to modprobe saa7134 card=117,96 In that case DVB-T is supported on the lower antenna connector and first adapter and DVB-S on the upper LNB connector and second adapter. Or to have it simple, it is safe to make rmmod and modprobe saa7134 card=5,96 tuner=54,54 This way on the first device is only analog TV enabled, don't forget to use it first to have good DVB-T reception later anyway, and the only frontend is the DVB-S one in question for testing. On the CTX948 voltage is OK AND Tuning to: Camera Deputati / autocount: 22 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 11804000 v 2750 inv:2 fecH:2 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 373 ms pipe opened xine pipe opened /root/.kaxtv.ts Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: Dubai Sports-1 / autocount: 23 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 11747000 h 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 18V, hiband (index 3) DiSEqC: e0 10 38 f3 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 374 ms xine pipe opened /root/.kaxtv1.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: ARD Das Erste / autocount: 24 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 11604000 h 2750 inv:2 fecH:5 DiSEqC: switch pos 0, 18V, loband (index 1) DiSEqC: e0 10 38 f2 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 379 ms xine pipe opened /root/.kaxtv.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: Abu Dhabi Sport / autocount: 25 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 12577000 h 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 18V, hiband (index 3) DiSEqC: e0 10 38 f3 00 00 . LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 379 ms xine pipe opened /root/.kaxtv1.ts pipe opened Asked to stop pipe closed Live stopped dvbstream::run() end dvbEvents 0:0 ended fdDvr closed Frontend closed Tuning to: BBC World / autocount: 26 Using DVB device 0:0 Philips TDA10086 DVB-S tuning DVB-S to 12596000 v 2750 inv:2 fecH:3 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 ... LOCKED. NOUT: 1 dvbEvents 0:0 started Tuning delay: 560 ms pipe opened
Re: [linux-dvb] SkyStar rev 2.8A driver?
Ali H.M. Hoseini wrote: Hi, I searched linuxtv.org http://linuxtv.org/ mailing list archive about SkyStar2 rev2.8A driver, or any suggestion, but I found nothing. The 2.6.22 kernel initialize B2C2 chip itself, but it could not identify the frontend for card. The chips used in this card for frontend are conexant cx24123 and cx24113 . I tried to load cx24123 module exists in the kernel, but later I found it is not defined for b2c2-flexcop module to use it, and hence it is not useful. Could anybody help me? See: http://marc.info/?l=linux-dvbm=120042808124927w=2 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Emtec 810S DVB-T Stick (164:2efc)
Hi, I've something interesting in the unstability issue for my Emtec 810S DVB-T Stick When the kaffeine TV screen freezes, the dmesg indicates that the USB device is disconnected and syslog continus to report that i2c-adapter is used : master_xfer[0] W or [1] R, addr= 0x40, len=2 Best regards, Alain Le lundi 4 février 2008 22:33, Alain Roos a écrit : Hi, Are you interested to update the dib0700 driver to record that above mentionned YUAN device is working ? Do you have any advice how to improve stability ? Thanks, Alain Le vendredi 1 février 2008 18:11, Alain Roos a écrit : Hi, - At the time of doing hg clone, the head was : changeset: 7115:3f704aa9d92e tag: tip date:Tue Jan 29 16:32:35 2008 -0200 - The patch is attached (if you don't like attachments in this mailing list, all my apologies) I'm running linux kernel 2.6.23.14, using distro Debian Etch, kaffeine as a TV viewer. The only issue is that after some channel zapping or even immediately, the tuner does no longer respond, kaffeine hangs, modules cannot be unloaded even with rmmod -f (the dongle being disconnected). The lsusb command hangs also. Only rebooting helps (and sucks). The chips on the board are : DIBcom 7070PB1-AXGXba-G-a and DIBcom 0700C-XCXXa-G I would be most grateful if someone has an idea about improving the stability of the driver. Also I've found in the archives a thread : http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015525.html involving Patrick Boettcher and Michael Wünscher about a similar device That ID was 1164:1efc (I had the same driver information under Windows). Alain Roos (Alsace / France) ___ 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] [ANNOUNCE] linux-next and V4L/DVB linux-next
A recent announce at LKML introduced a new concept of integrated development
between the several subsystem trees, called linux-next.
The basic idea is to have a common tree that merges all development efforts,
helping to solve merge conflicts before arising at Linus main tree. More
details can be seen at the original announce [1].
With this concept, what happens is that a new patch will mature at the
development branches and at linux-next. At the release of a new kernel (let's
say 2.6.25), a merge window will open to the next kernel (2.6.26). The patches
for the next kernel will be submitted by each subsystem maintainer. Since those
patches were already tested on linux-next tree, the merging process will
become easier and the newer kernel will become more stable.
So, linux-next contains the patches for 2.6.25, plus the patches expected to be
added at kernel 2.6.26.
For this to happen, I've created a newer -git tree, containing the committed
changesets that are expected to appear at the next kernel. It contains
basically the same patches already present on -hg and v4l-dvb.git trees, plus
the base patches from linux-next (at 'stable' branch). Another branch
('master') will contain also the merged patches from the other subsystems.
For those brave enough to test it, the tree is available at [2]. Please be
warned to use this on a testing system, since patches at core subsystems
(ext2, vfs, etc) may be broken there.
In order have a single point where all trees are listed, I've updated
README.patches file, and the main tree at http://linuxtv.org/hg with the newer
tree. I've also added a link to README.patches there.
[1] http://lkml.org/lkml/2008/2/11/512
[2]
http://www.kernel.org/git/?p=linux/kernel/git/mchehab/linux-next.git;a=summary
Cheers,
Mauro
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Terratec Cinergy T USB XE
Hello, I have a Terratec Cinergy T USB XE, 0ccd:0069 and have been trying to compile from site: http://www.jusst.de/hg/af901x/ My kernel is 2.6.22.5-31-x86_64. I get the following error/warning messages when compiling: CC [M] /usr/build/af901x/v4l/af9015.o /usr/build/af901x/v4l/af9015.c: In function 'af901x_read_snr': /usr/build/af901x/v4l/af9015.c:477: warning: array subscript is above array bounds /usr/build/af901x/v4l/af9015.c: In function 'af901x_attach': /usr/build/af901x/v4l/af9015.c:1608: warning: 'fw_ver' may be used uninitialized in this function CC [M] /usr/build/af901x/v4l/af9015_biu.o /usr/build/af901x/v4l/af9015_biu.c: In function 'af9015_read_eeprom': /usr/build/af901x/v4l/af9015_biu.c:463: warning: unused variable 'eeprom_reg' /usr/build/af901x/v4l/af9015_biu.c: In function 'af9015_get_biu_config': /usr/build/af901x/v4l/af9015_biu.c:685: warning: label 'exit' defined but not used /usr/build/af901x/v4l/af9015_biu.c: In function 'af9015_epconfig_mode_15': /usr/build/af901x/v4l/af9015_biu.c:817: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:822: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:829: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:834: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:841: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:848: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c: In function 'af9015_epconfig_mode_17': /usr/build/af901x/v4l/af9015_biu.c:963: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:968: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c:974: warning: overflow in implicit constant conversion /usr/build/af901x/v4l/af9015_biu.c: In function 'af9015_tuner_attach': /usr/build/af901x/v4l/af9015_biu.c:1096: warning: unused variable 'err' /usr/build/af901x/v4l/af9015_biu.c: In function 'af9015_usb_probe': /usr/build/af901x/v4l/af9015_biu.c:1167: warning: unused variable 'biu' /usr/build/af901x/v4l/af9015_biu.c: At top level: /usr/build/af901x/v4l/af9015_biu.c:1138: warning: 'af9015_biu_epconfig' defined but not used When I connect the stick it is recognised, firmware is downloaded and the tuner is attached according to the messages, but when trying to scan dvb-t the tuning fails. Do I need another kernel? I have tried 2.6.24 but it did not seem to work at all with http://www.jusst.de/hg/af901x/ Is the support for Terratec Cinergy T USB XE, 0ccd:0069 and the Freescale tuner going to http://linuxtv.org/hg/ for all kernels? Is there anything I can do to solve this? Thank you in advance ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [ANNOUNCE] linux-next and V4L/DVB linux-next
On Thu, Feb 14, 2008 at 04:40:12PM -0200, Mauro Carvalho Chehab wrote: Great idea, do I understand right that it miss multiproto ? Thank, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [OT] request_firmware()
Hello I know this is the wrong list to ask, but you use this function (see subject) and I think somebody can answer my question. Why does request_firmware need a device as parameter? int request_firmware(const struct firmware **fw, const char *name, struct device *device); I thought request_firmware just loads the firmware in the struct firmware? Thanks, Thomas -- http://www.kaiser-linux.li ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] support Cinergy HT USB XE (0ccd:0058)
Hi I've been trying to load the tunner-xc2028 module in debug mode. I send the results, there's the same error and also some things when loading the firmware. Hans could you send me your firmware to check that it's not an error of that (I mean, when I scan there's no signal or SNR, perhaps this could be something related to it)? Thanks. Albert [ 2219.804000] usb 6-1: new high speed USB device using ehci_hcd and address 4 [ 2219.94] usb 6-1: configuration #1 chosen from 1 choice [ 2219.94] dvb-usb: found a 'Pinnacle Expresscard 320cx' in cold state, will try to load a firmware [ 2219.956000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' [ 2220.156000] dib0700: firmware started successfully. [ 2220.66] dvb-usb: found a 'Pinnacle Expresscard 320cx' in warm state. [ 2220.66] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 2220.66] DVB: registering new adapter (Pinnacle Expresscard 320cx) [ 2221.032000] DVB: registering frontend 0 (DiBcom 7000PC)... [ 2221.032000] xc2028: Xcv2028/3028 init called! [ 2221.032000] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 2221.032000] xc2028 4-0061: xc2028_set_config called [ 2221.032000] input: IR-receiver inside an USB DVB receiver as /class/input/input10 [ 2221.032000] dvb-usb: schedule remote query interval to 150 msecs. [ 2221.032000] dvb-usb: Pinnacle Expresscard 320cx successfully initialized and connected. [ 2251.856000] xc2028 4-0061: xc2028_sleep called [ 2251.856000] xc2028 4-0061: Error on line 1063: -5 [ 2282.436000] xc2028 4-0061: xc2028_set_params called [ 2282.436000] xc2028 4-0061: generic_set_freq called [ 2282.436000] xc2028 4-0061: should set frequency 402000 kHz [ 2282.436000] xc2028 4-0061: check_firmware called [ 2282.436000] xc2028 4-0061: load_all_firmwares called [ 2282.436000] xc2028 4-0061: Reading firmware xc3028-v27.fw [ 2282.48] xc2028 4-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 [ 2282.48] xc2028 4-0061: Reading firmware type BASE F8MHZ (3), id 0, size=8718. [ 2282.48] xc2028 4-0061: Reading firmware type BASE F8MHZ MTS (7), id 0, size=8712. [ 2282.48] xc2028 4-0061: Reading firmware type BASE FM (401), id 0, size=8562. [ 2282.48] xc2028 4-0061: Reading firmware type BASE FM INPUT1 (c01), id 0, size=8576. [ 2282.48] xc2028 4-0061: Reading firmware type BASE (1), id 0, size=8706. [ 2282.48] xc2028 4-0061: Reading firmware type BASE MTS (5), id 0, size=8682. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 10007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 10007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 20007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 20007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 40007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 40007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 80007, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 80007, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 300e0, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 300e0, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id c00e0, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id c00e0, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 20, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 20, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 400, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 400, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV6 ATSC (10030), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV6 QAM (68), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV6 QAM (70), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV7 (88), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV7 (90), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV78 (108), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV78 (110), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2620 DTV8 (208), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type D2633 DTV8 (210), id 0, size=149. [ 2282.48] xc2028 4-0061: Reading firmware type FM (400), id 0, size=135. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 10, size=161. [ 2282.48] xc2028 4-0061: Reading firmware type MTS (4), id 10, size=169. [ 2282.48] xc2028 4-0061: Reading firmware type (0), id 100040, size=169. [ 2282.48] xc2028 4-0061: Reading
Re: [linux-dvb] [OT] request_firmware()
Michael Krufky wrote: On Thu, Feb 14, 2008 at 3:37 PM, Thomas Kaiser [EMAIL PROTECTED] wrote: Hello I know this is the wrong list to ask, but you use this function (see subject) and I think somebody can answer my question. Why does request_firmware need a device as parameter? int request_firmware(const struct firmware **fw, const char *name, struct device *device); I thought request_firmware just loads the firmware in the struct firmware? IIRC, when the device is destroyed, it is a signal for the memory used to store the firmware to be freed if not done already. -Mike So, that means when the pointer to device gets null the memory which holds the firmware is freed? Thanks, Thomas -- http://www.kaiser-linux.li ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [OT] request_firmware()
On Thu, Feb 14, 2008 at 3:37 PM, Thomas Kaiser [EMAIL PROTECTED] wrote: Hello I know this is the wrong list to ask, but you use this function (see subject) and I think somebody can answer my question. Why does request_firmware need a device as parameter? int request_firmware(const struct firmware **fw, const char *name, struct device *device); I thought request_firmware just loads the firmware in the struct firmware? IIRC, when the device is destroyed, it is a signal for the memory used to store the firmware to be freed if not done already. -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Pinnacle PCTV Dual Hybrid Pro PCI Express under Linux?
Hello, I've buyed a Pinnacle PCTV Dual Hybrid Pro PCI Express, and I'd like to know the current state of Linux support for this card, because on the page: http://www.linuxtv.org/wiki/index.php/DVB-T_PCIe_Cards this card is listed as Unsupported dvd-t pcie cards. How can I help with support development if I'm not a developer? Thanks. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing
Hi, Hermann I am a bit confused hermann pitton schrieb: Hi, Am Donnerstag, den 14.02.2008, 12:01 +0100 schrieb hermann pitton: Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: Hi, folks In my personal repository: http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/ you will find a driver that supports this card, DVB-T and DVB-S It might also work for - one section of the MD8800 - similar boards based on saa713x, tda10086, tda826x, isl6405 The board will show up as MD8800. According to Hermann, the configurations for analog TV and DVB-T are identical. If you want to use the board with DVB-S, you will need to load the saa7134-dvb module with the option use_frontend=1. The default 0 is DVB-T. For those who got the board from a second source: don't forget to connect the 12v (the floppy supply) connector. I don't have a dish, so i depend on your reports. To get the MD8800 running, i need a volunteer who does the testing for me. He should be able to apply patches, compile the driver and read kernel logs. Good luck Hartmut Hartmut, great job, thank you very much! Can't wait, result of a first voltage measurement on the md8800 Quad. The upper LNB connector associated to the second saa7134 16be:0008 device has correct voltage. Since my stuff is not in the original green PCI slot and I have only the first 16be:0007 device active, can't test much more for now here. back on the machine and thinking about it twice ... The Quad works for me as well on the upper LNB connector, despite of that I previously used the lower one successfully with RF loopthrough from an external receiver. So, in case of the Quad, just let it be autodetected and try on the first adapter and upper LNB connector. So this one works as well, great! But which one is it? Please tell me the minor device id. I need to use it to separate the 2 sections. i will need to control the other one in a very different way. Even more fun :) Cheers, Hermann People with the card in the original Medion PC could set options saa7134-dvb use_frontend=1 debug=1 in /etc/modprobe.conf and then do depmod -a. The Syntek v4l usb stkwebcam still produces a compilation error and needs to be disabled in make xconfig or something else. Hm, i didn't have any compile problems ... After make it is best to do make rmmod on top of your v4l-dvb-experimental first. Those new to the v4l-dvb development stuff might do also make rminstall and then check that no *.ko is left in /lib/modules/kernel_in_use/kernel/drivers/media/* Especially the old video_buf.ko in the video dir needs to be removed. Check with ls -R |grep .ko and then make install. Now I suggest to modprobe saa7134 card=117,96 In that case DVB-T is supported on the lower antenna connector and first adapter and DVB-S on the upper LNB connector and second adapter. Or to have it simple, it is safe to make rmmod and modprobe saa7134 card=5,96 tuner=54,54 This way on the first device is only analog TV enabled, don't forget to use it first to have good DVB-T reception later anyway, and the only frontend is the DVB-S one in question for testing. Why? the cards should be autodetected. Or is there a variant of the 948 with a device id different from 16be:000d? It should be possible to give a list to the use_frontend=xx option. Something like use_frontend=0,1,0 which should select DVB-S only for the 2nd instance. Am i wrong? Of corse you will need to select the right frontend which is not easy with some applications. snip But thank you for your fast reporting! Another issue: You have some patches waiting for integration. We can use my other repository for this. Best regards Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Dual Hybrid Pro PCI Express under Linux?
Mara kaid wrote: Hello, I've buyed a Pinnacle PCTV Dual Hybrid Pro PCI Express, and I'd like to know the current state of Linux support for this card, because on the page: http://www.linuxtv.org/wiki/index.php/DVB-T_PCIe_Cards this card is listed as Unsupported dvd-t pcie cards. How can I help with support development if I'm not a developer? Thanks. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb See: http://marc.info/?l=linux-dvbm=120049536116546w=2 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing
Hi Hartmut, Am Donnerstag, den 14.02.2008, 22:59 +0100 schrieb Hartmut Hackmann: Hi, Hermann I am a bit confused hermann pitton schrieb: Hi, Am Donnerstag, den 14.02.2008, 12:01 +0100 schrieb hermann pitton: Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: Hi, folks In my personal repository: http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/ you will find a driver that supports this card, DVB-T and DVB-S It might also work for - one section of the MD8800 - similar boards based on saa713x, tda10086, tda826x, isl6405 The board will show up as MD8800. According to Hermann, the configurations for analog TV and DVB-T are identical. If you want to use the board with DVB-S, you will need to load the saa7134-dvb module with the option use_frontend=1. The default 0 is DVB-T. For those who got the board from a second source: don't forget to connect the 12v (the floppy supply) connector. I don't have a dish, so i depend on your reports. To get the MD8800 running, i need a volunteer who does the testing for me. He should be able to apply patches, compile the driver and read kernel logs. Good luck Hartmut Hartmut, great job, thank you very much! Can't wait, result of a first voltage measurement on the md8800 Quad. The upper LNB connector associated to the second saa7134 16be:0008 device has correct voltage. Since my stuff is not in the original green PCI slot and I have only the first 16be:0007 device active, can't test much more for now here. back on the machine and thinking about it twice ... The Quad works for me as well on the upper LNB connector, despite of that I previously used the lower one successfully with RF loopthrough from an external receiver. So, in case of the Quad, just let it be autodetected and try on the first adapter and upper LNB connector. So this one works as well, great! But which one is it? Please tell me the minor device id. I need to use it to separate the 2 sections. i will need to control the other one in a very different way. Seems default is some RF loopthrough. I'll need to measure too against loopthrough conditions, but for sure voltage is only on the upper connector and previously with the RF feed from the external receiver the lower connector was fine enough. No voltage in any previous testing and the 12Volts were always connected. Both slightly different Quads from different fabs work as well as the CTX948. In my case it is the 16be:0007 and to the 16be:0008 I have no access. Even more fun :) Cheers, Hermann People with the card in the original Medion PC could set options saa7134-dvb use_frontend=1 debug=1 in /etc/modprobe.conf and then do depmod -a. The Syntek v4l usb stkwebcam still produces a compilation error and needs to be disabled in make xconfig or something else. Hm, i didn't have any compile problems ... This happens on an almost given up FC5 with some 2.6.20 ... After make it is best to do make rmmod on top of your v4l-dvb-experimental first. Those new to the v4l-dvb development stuff might do also make rminstall and then check that no *.ko is left in /lib/modules/kernel_in_use/kernel/drivers/media/* Especially the old video_buf.ko in the video dir needs to be removed. Check with ls -R |grep .ko and then make install. Now I suggest to modprobe saa7134 card=117,96 In that case DVB-T is supported on the lower antenna connector and first adapter and DVB-S on the upper LNB connector and second adapter. Or to have it simple, it is safe to make rmmod and modprobe saa7134 card=5,96 tuner=54,54 This way on the first device is only analog TV enabled, don't forget to use it first to have good DVB-T reception later anyway, and the only frontend is the DVB-S one in question for testing. Why? the cards should be autodetected. Or is there a variant of the 948 with a device id different from 16be:000d? It should be possible to give a list to the use_frontend=xx option. Something like use_frontend=0,1,0 which should select DVB-S only for the 2nd instance. Am i wrong? Of corse you will need to select the right frontend which is not easy with some applications. snip This was all about first ideas on the Quads. On the CTX948 there is no problem _at all_! For the Quad I took my first idea back and said, just let it be auto detected and take the first frontend then and the upper LNB connector. Sorry for confusion, but it is still a little ... But thank you for your fast reporting! Another issue: You have some patches waiting for integration. We can use my other repository for this. We might be already through here and you might like to commit first ;) Best regards Hartmut Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing
Hi, again snip So this one works as well, great! But which one is it? Please tell me the minor device id. I need to use it to separate the 2 sections. i will need to control the other one in a very different way. Seems default is some RF loopthrough. I'll need to measure too against loopthrough conditions, but for sure voltage is only on the upper connector and previously with the RF feed from the external receiver the lower connector was fine enough. No voltage in any previous testing and the 12Volts were always connected. Both slightly different Quads from different fabs work as well as the CTX948. In my case it is the 16be:0007 and to the 16be:0008 I have no access. Perfect, that's what i needed to know. snip We might be already through here and you might like to commit first ;) Indeed. I should also announce this status for the md8800... What's your opinion on this: According to the hints i got, the isl6405 is visible only on one section of the md8800. The other section has control over the voltage through a GPIO port. So unless i do something very dirty, there will either be the restriction - that the DVB-S decoder of the 16be:0007 section needs to be selected first. Otherwise the other DVB-S part will not work - or i will need to always fire up the LNB supply of the 0008 section as soon as DVB is initialized. The second approach has the advantage that it has little effect for the end user while the first needs to be explained. But i am not sure whether the isl6405 is fully short circuit proof. I will read the datasheet again... Best regards Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
