[linux-dvb] Open letter - Linux Support for WinTV -T-500 DVB-T TV card
To: Hauppauge, manufacturer of complete TV solutions To: Microtune and Dibcom, manufacturers of discrete elements used in the above solutions Copy: Linuxtv.org DVB mailing list, representing the linux users of above equipment, and the current developers of drivers I am a user of an Hauppauge WinTV-T-500 DVB-T dual tuner card. I am also a Linux user, trying to build a home-made Home Theater PC (HTPC). This letter is an individual effort, not reflecting the official policy of any other group or body of persons. Nevertheless, I hope that other users will make the effort of sending you equivalent requests. The WinTV-500-T is a very attractive piece of hardware with a feature set that matches many of the needs of HTPC builders, especially due to its dual-tuners capabilities. It has become very popular. Unfortunately, the current drivers available, developed by individual efforts, through reverse engineering or limited corporate efforts are still not fully working and are not completely usable, due primarily to disconnecting USB devices or tuning difficulties. Such problems could easily be corrected if efforts were made by the manufacturers, both of the card (Hauppauge) and of the components (Dibcom and Microtune). I understand that the Linux users of your equipment are still a fringe of your user base, but please keep in mind that this situation is rapidly evolving, with the growing success of the platform itself, partly driven by the growing popularity of custom HTPC applications. I am sure that a solid and vendor-supported set of drivers would only accelerate the success of Linux around the TV applications. Please, take a look at the situation and assign official and sufficient resources (humans, coders, development hardware and lab, multi-parties communications, time, money, salaries) in order to achieve complete and solid support for your hardware under the Linux kernel. These efforts wil allow you to grab a reward, the capture of a fast-growing market where you would be the first to grab an audience. The Linux users and developers community will certainly be eager to support these efforts and provide all the feedback you may need. Nicolas Will ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Cinergy HT USB XE
Hi all, as far as I am able to understand the existing code, there should be a kund of tuner interface for the tuner driver. (I'm on work, I don't have the code here...there were methods like get...TunerInterface) I think we need to write such a method for any (partly) existing driver - am I right? Holger Am Donnerstag, 6. September 2007 22:01 schrieb Aidan Thornton: On 9/6/07, root [EMAIL PROTECTED] wrote: I think the device is based on the STK7700-PH component by Dibcom. The STK7700-PH family is based on the following components: - a Dibcom demodulator with an integrated USB interface (Dib7700) - a tuner and analog decoder which are provided by a third party partner (Xceive XC3028 and Conextant CX25843) The dib0700 driver seems to support the STK7700-P, STK7700-D, STK7700-PD, but not the STK7700-PH wich is the only one using the XC3028. It seems we have to add the xc3028 driver to the existing one. Ref: www1.dibcom.info/Images/Upload/pdf/DiBcom_PC_Notebooks_0702.pdf Hope it helps. Ivan Hi, That could be interesting. (There are several xc3028 drivers, and unfortunately the one in trunk is analog-only and incomplete. There's mrec's drivers, which support analog and digital but either require changes to core code that'll never be merged or involve a weird userspace tuner interface that's currently unmerged - I'm not sure how compatible the latter is with trunk now. There's also digital-only code lying around somewhere. Finally, I have a port of mrec's kernel-space driver to the hybrid tuner framework in trunk, but it's untested with digital and with anything other than the original HVR-900. The last one is also not currently publicly available.) The xc3028 has some odd requirements in itself - it seems to need GPIO twiddling to tune, amongst other things. (Sorry about the duplicate e-mail - I accidentally replied to sender instead of to all.) Aidan. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kworld ATSC-110 : No NTSC Cable Signal
I'm having a problem with my Kworld ATSC-110's NTSC cable interface (/dev/video0) not locking on any signal. I just upgraded v4l from linux kernel 2.6.22.4 modules - current v4l-dvb kernel modules (v4l-dvb-0c3e99a3f31c). This was suggested by Mike Krufky to fix the rf input switching I was noticing with the 2.6.22.4 kernel. The DVB interface is working perfectly on the lower port. I patched the v4l code to add the Kworld remote. My system: Asus Pendant P1-AH2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ 1 GB RAM Kworld ATSC-110 WinTV-PVR 250 Ubuntu 7.10 Linux 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux What I have tried: I have tried scanning with MythTV and TVTime, no channels are found. The dev interface (/dev/video0) is being created and logged in dmesg and working. Prevented the saa7134-dvb module from loading, to make sure that the card wasn't being accessed by both turners at once. Thank you for any help. Nathan. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Open letter - Linux Support for WinTV -T-500 DVB-T TV card
On Fri, 2007-09-07 at 12:13 +0200, Eduard Huguet wrote: Good try! I don't know if this will be even remotely helpful, but at least you tried. Well, then add your own layer and send a similar email to the same list of companies. Complaining here will only take you so far... It's really a pity that the support for this card is still incomplete these days. Specially having in mind that (I think) we are very close to have a fully functional driver, as the USB disconnects (without plugin in the remote captor) are really very marginal. Once more, complaining here will only take you so far... However, plugin in and using the remote controller is a total different story, a nightmare I'd even say: system locks, frequent disconnects (not solvable by restarting the mythbackend - I need to do a full poweroff and even unplug the power cord to force a firmware reload on the card sometimes...), etc... Is there any possibility that we get a better support for the Nova-T 500 remote any day? Complain to the right people, which is not here. It'd really be the perfect card if only this issue were solved... True, tell them that. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kworld ATSC-110 : No NTSC Cable Signal
Nathan Faust wrote: I'm having a problem with my Kworld ATSC-110's NTSC cable interface (/dev/video0) not locking on any signal. I just upgraded v4l from linux kernel 2.6.22.4 modules - current v4l-dvb kernel modules (v4l-dvb-0c3e99a3f31c). This was suggested by Mike Krufky to fix the rf input switching I was noticing with the 2.6.22.4 kernel. The DVB interface is working perfectly on the lower port. You were trying to pull the NTSC cable signal in from the lower RF input, correct? Regardless of what RF input you currently have it attached to, did you attempt the same by switching to the other RF input? Try that too and see what happens. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Open letter - Linux Support for WinTV -T-500 DVB-T TV card
Good try! I don't know if this will be even remotely helpful, but at least you tried. It's really a pity that the support for this card is still incomplete these days. Specially having in mind that (I think) we are very close to have a fully functional driver, as the USB disconnects (without plugin in the remote captor) are really very marginal. However, plugin in and using the remote controller is a total different story, a nightmare I'd even say: system locks, frequent disconnects (not solvable by restarting the mythbackend - I need to do a full poweroff and even unplug the power cord to force a firmware reload on the card sometimes...), etc... Is there any possibility that we get a better support for the Nova-T 500 remote any day? It'd really be the perfect card if only this issue were solved... Kind regards, Eduard Huguet Barcelona (Spain) -- Missatge reenviat -- From: Nicolas Will [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Fri, 07 Sep 2007 08:03:18 +0100 Subject: [linux-dvb] Open letter - Linux Support for WinTV -T-500 DVB-T TV card To: Hauppauge, manufacturer of complete TV solutions To: Microtune and Dibcom, manufacturers of discrete elements used in the above solutions Copy: Linuxtv.org DVB mailing list, representing the linux users of above equipment, and the current developers of drivers I am a user of an Hauppauge WinTV-T-500 DVB-T dual tuner card. I am also a Linux user, trying to build a home-made Home Theater PC (HTPC). This letter is an individual effort, not reflecting the official policy of any other group or body of persons. Nevertheless, I hope that other users will make the effort of sending you equivalent requests. The WinTV-500-T is a very attractive piece of hardware with a feature set that matches many of the needs of HTPC builders, especially due to its dual-tuners capabilities. It has become very popular. Unfortunately, the current drivers available, developed by individual efforts, through reverse engineering or limited corporate efforts are still not fully working and are not completely usable, due primarily to disconnecting USB devices or tuning difficulties. Such problems could easily be corrected if efforts were made by the manufacturers, both of the card (Hauppauge) and of the components (Dibcom and Microtune). I understand that the Linux users of your equipment are still a fringe of your user base, but please keep in mind that this situation is rapidly evolving, with the growing success of the platform itself, partly driven by the growing popularity of custom HTPC applications. I am sure that a solid and vendor-supported set of drivers would only accelerate the success of Linux around the TV applications. Please, take a look at the situation and assign official and sufficient resources (humans, coders, development hardware and lab, multi-parties communications, time, money, salaries) in order to achieve complete and solid support for your hardware under the Linux kernel. These efforts wil allow you to grab a reward, the capture of a fast-growing market where you would be the first to grab an audience. The Linux users and developers community will certainly be eager to support these efforts and provide all the feedback you may need. Nicolas Will ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kworld ATSC-110 : No NTSC Cable Signal
You were trying to pull the NTSC cable signal in from the lower RF input, correct? Regardless of what RF input you currently have it attached to, did you attempt the same by switching to the other RF input? Try that too and see what happens. My goal is the have both NTSC and QAM cable on the same RF input, I don't care which one that is. I'm also hoping that the 8VBS is on the other RF input. I forgot to mention that I did try switching between both RF inputs while testing for NTSC signal, but thanks for suggesting that. Nathan. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] STB0899 frontend support
Hi, I'm working on a DVB-S2 decoder with an STB0899 frontend. I had a look at the dvb sources and didn't find any support for it. I saw that Manu wrote a driver last april but it gave me several errors when compiling it as a module inside a 2.6.17 kernel and it hasn't been included in the official repository. Do you know the status of this driver or any alternatives/hints to make it work? Thanks. Regards, -- Pedro Aguilar ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] STB0899 frontend support
Hi, take a look at this: http://www.linuxtv.org/pipermail/linux-dvb/2007-July/019299.html works with TT3200 (SAA7146/STB0899) roman On Fri, Sep 07, 2007 at 10:32:06AM +0200, Pedro Aguilar wrote: Hi, I'm working on a DVB-S2 decoder with an STB0899 frontend. I had a look at the dvb sources and didn't find any support for it. I saw that Manu wrote a driver last april but it gave me several errors when compiling it as a module inside a 2.6.17 kernel and it hasn't been included in the official repository. Do you know the status of this driver or any alternatives/hints to make it work? Thanks. Regards, -- Pedro Aguilar -- -- ,''`. [benco] | mailto: [EMAIL PROTECTED] | silc: /msg benco : :' : - `. `' GPG publickey: http://www.acid.sk/pubkey.asc `- KF = 388E 43D9 7316 A4D4 A0EB C4F2 E769 64EB DEB3 7CF1 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
hermann pitton wrote: Can not reproduce your problem on a 32bit machine with the Asus P7131 Dual. If I fake frequencies out of range in my tzap channels.conf, the error behavior is OK, also I can still tune to the valid frequencies. YEP YEP YEP SOLVED I want to thank you all. Lot of you asked me to check my channels.conf. That is what put me on the right direction. The card was working fine on my WinXP machine so it wasn't an hardware problem. The reported error was in dmesg so I had only two alternatives: a driver problem or a buggy software launched at start time. Damn... a daemon... or a server... I checked all my channels.conf: they were right and all the programs using channels.conf (vdr, tzap, mplayer) were not launched at boot time. Mmmm... MythTv-backend was the only one started in background during startup... ... so I removed it and... TA-DA everything works fine again. It's a mystery why Mythtv-backend was trying to use the driver: there was no scheduled activities... ... and it's a mystery (for me) why it wasn't possible to use the driver after that buggy activity. Radio doesn't work for you. Are you sure you have still gpio 0x020 for radio and not 0x000 ? It wasn't possible to use anything after the mythtv backend activity. Just noise on radio and jumping images with a lot of noise with anolog tv. But now everything is going fine. ## ACTUAL SITUATION ## 1) patched v4l with your patches so dvb-t is binded to the same analog-tv antenna. (cannot understand why I have to patch also saa7134-cards.c with gpi=0x000 bit I did it, LOL) 2) analog tv: perfect 3) Couldn't make the patch cable working. Still have to use aplay or sox 4) kaffeine on dvb-t perfect 5) mplayer with analog tv: perfect 6) mplayer with dvb-t: solved now! It doesn't like all those auto in channels.conf. Changed them and mplayer started working. So the only problem now is with the patch cable. Thanks again to all of you for helping me to solve this problem. ciao paolo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Port of em28xx and xc3028 to new hybrid tuner framework.
Hi, In the hope of having a driver that fits better with the v4l-dvb trunk than the currently available options, I've ported the analog parts of Markus Rechberger's em28xx and xc3028 drivers to the new hybrid tuner framework. (The analog bits are similar enough to his framework that this was fairly easy.) It hasn't been tested with anything other than the analog TV in on my HVR-900 (USB ID 2040:6500), so YMMV. The repository is at http://www.makomk.com/hg/v4l-dvb-makomk for anyone feeling brave. Digital is not supported as yet - I haven't even tried to get em2880_dvb working, and the xc3028 support is probably broken. (I'm unsure how to get the bandwidth setting in xc3028 and how to tell if the client wants DVB-T, ATSC or something else.) Any suggestions and comments are welcome. Thanks, Aidan Thornton ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Port of em28xx and xc3028 to new hybrid tuner framework.
Aidan Thornton wrote: Hi, In the hope of having a driver that fits better with the v4l-dvb trunk than the currently available options, I've ported the analog parts of Markus Rechberger's em28xx and xc3028 drivers to the new hybrid tuner framework. (The analog bits are similar enough to his framework that this was fairly easy.) It hasn't been tested with anything other than the analog TV in on my HVR-900 (USB ID 2040:6500), so YMMV. The repository is at http://www.makomk.com/hg/v4l-dvb-makomk for anyone feeling brave. Digital is not supported as yet - I haven't even tried to get em2880_dvb working, and the xc3028 support is probably broken. (I'm unsure how to get the bandwidth setting in xc3028 and how to tell if the client wants DVB-T, ATSC or something else.) Any suggestions and comments are welcome. Please take a look at the xc3028-fe.c file in the following patch: http://www.linuxtv.org/~mkrufky/xc-bluebird.patch You can use the logic used in that patch to determine ATSC / DVB-T / etc ...we might want to change this after multiproto is merged (if that happens anytime soon), because better options may be available at that point. I was thinking of redoing that xc3028-fe module to include analog support soon, but if you're going to to work on it instead, it makes life easier for me :-) Cheers, Mike Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Port of em28xx and xc3028 to new hybrid tuner framework.
On 9/7/07, Michael Krufky [EMAIL PROTECTED] wrote: Aidan Thornton wrote: Hi, In the hope of having a driver that fits better with the v4l-dvb trunk than the currently available options, I've ported the analog parts of Markus Rechberger's em28xx and xc3028 drivers to the new hybrid tuner framework. (The analog bits are similar enough to his framework that this was fairly easy.) It hasn't been tested with anything other than the analog TV in on my HVR-900 (USB ID 2040:6500), so YMMV. The repository is at http://www.makomk.com/hg/v4l-dvb-makomk for anyone feeling brave. Digital is not supported as yet - I haven't even tried to get em2880_dvb working, and the xc3028 support is probably broken. (I'm unsure how to get the bandwidth setting in xc3028 and how to tell if the client wants DVB-T, ATSC or something else.) Any suggestions and comments are welcome. Please take a look at the xc3028-fe.c file in the following patch: http://www.linuxtv.org/~mkrufky/xc-bluebird.patch You can use the logic used in that patch to determine ATSC / DVB-T / etc ...we might want to change this after multiproto is merged (if that happens anytime soon), because better options may be available at that point. I was thinking of redoing that xc3028-fe module to include analog support soon, but if you're going to to work on it instead, it makes life easier for me :-) I acknowlidge what you're doing there although the driver itself will use the userland drivers even for upcoming versions which use different i2c clientchips as the em28xx does at the moment. All the upcoming drivers will be opensourced, just to avoid any doubts. This also has to be concerned about backward compatibility: http://mcentral.de/wiki/index.php/Bugtracker#i2c_dev_problem this is also a problem about the inkernel hybrid design, the em28xx uses the userland implementation since the current xceive reference drivers use floating point algorithms. Since those reference drivers also include sample board configurations for different boards I'll moreover use these ones and work on other things instead of reinventing the wheel. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Please help
Hi my name is Roberto, I have been trying to install my ADS tech TV tuner. My Linux is a kubuntu, kernel 2.6.20-16-generic on a DELL Latitude D610. I followed all instructions in linuxtv.org but I still have problems with the following items: I couldn't started: crc32 firmware_class (I think this is important to load my firmware) dib3000-common The others are OK i2c_core dvb-core dvb-pll dib3000mb dvb-usb dvb-usb-dibusb-common dvb-usb-dibusb-mb My device use dvb-usb-adstech-usb2-02.fw firmware and is located in /lib/firmware. Device description at: http://www.adstech.com/latam/Espn/products/USBAV-704/productintro.asp thaks. __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.espanol.yahoo.com/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Port of em28xx and xc3028 to new hybrid tuner framework.
On Fri, 2007-09-07 at 14:22 -0400, Michael Krufky wrote: I was thinking of redoing that xc3028-fe module to include analog support soon, but if you're going to to work on it instead, it makes life easier for me :-) as they might say on friends: like i didn't see that coming :-) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Port of em28xx and xc3028 to new hybrid tuner framework.
Any suggestions and comments are welcome. Please take a look at the xc3028-fe.c file in the following patch: http://www.linuxtv.org/~mkrufky/xc-bluebird.patch You can use the logic used in that patch to determine ATSC / DVB-T / etc The tm6000 has a tuner-xc2028 driver that actually works also with xc3028, for tm6000. It contains both DVB and V4L logic, although yet not ported to the hybrid driver approach. IMO, shouldn't be hard to port though. Cheers, Mauro. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [RFC] TUV1236d / dvb-pll: rf input switching via module option
David Engel wrote: The standard driver as of Linux v2.6.21 does analog and 8VSB on the top input and QAM on the bottom input. My desired behavior is analog and QAM on one input and 8VSB on the other. No problem. It was an easy enough driver hack to make it do what I wanted. Others might be interested in this change too, so is there any willingness from the core DVB maintainers to accept a patch to make this configurable via a module parameter? If so, would you like one global setting for all cards or one setting for each card? I know I took a while with this... I was working on tuner refactoring and didn't have time. Meanwhile, if we do any kind of module option for rf input selection, it must be one setting for each card. Please test the following mercurial tree: http://linuxtv.org/hg/~mkrufky/dvb-pll After building installing the new modules, do: modinfo dvb-pll ...to view the new module options. If you have only one card in the system, you may do: modprobe dvb-pll input=1 ... then: modprobe cx88-dvb -or- modprobe saa7134-dvb After doing the above, your card will use input #1 regardless of whether you are using VSB or QAM. If, however, you have multiple cards in the system, and the ATSC11[05] / HDTV Wonder is the second DVB card, then instead do: modprobe dvb-pll input=0,2 ...to specify that the dvb-pll module should autoselect the input used for the first card, and use input #2 for the second card. Unfortunately, this does not allow for REVERSING the input selection -- this will only force it to use one or the other in digital mode. If anybody has some ideas as to how to reverse the default selection in a clean way, I am open to suggestions. If this works correctly, (and I have no doubt that it will) I can add the same option to the tuner-simple module, to allow the user to choose the rf input used for analog tv as well. Please also note: Pass debug=1 to dvb-pll, in order for dvb-pll to show you the instance ID of the tuv1236d. If you have multiple cards in the system, this will be helpful to determine the order of the input option array to pass via modprobe. debug output will look like this: [ 3023.695903] dvb-pll[0] 0-0061: id# 11 (LG TDVS-H06xF) attached, autodetected I also added a module option to force dvb-pll to use a dvb_pll_desc other than the one picked by default. This is useful in some cases, where the vendor may release an alternate revision of the hardware using a different tuner, but without changing the pci subsystem / usb device ids. This option should be used for debugging purposes, ONLY. Please provide some feedback after testing this tree. The changes in question are: http://linuxtv.org/hg/~mkrufky/dvb-pll - dvb-pll: pass fe pointer into dvb_pll_configure() and set() functions - dvb-pll: store instance ID in dvb_pll_priv structure - dvb-pll: add module option to specify rf input - dvb-pll: add module option to force dvb-pll desc id (for debug use only) dvb-pll.c | 145 +- 1 file changed, 102 insertions(+), 43 deletions(-) Cheers, Mike Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kernelspace floating pointer - was Re: Port of em28xx and xc3028 to new hybrid tuner framework.
Markus wrote: the em28xx uses the userland implementation since the current xceive reference drivers use floating point algorithms. The usage of FP on DVB drivers is something that have been discussed for quite a long time at the community. I've asked Linus about the possibility of having a kernelspace driver using floating point. This may eventually happen (and, in fact, it already happens on a few drivers). There are, however, two points to consider: a) care should be taken to preserve FP state by the driver, since kernel won't do this by itself. This probably means that this may not be so fast as userspace calculation (although I suspect that it will be faster enough for the current needs); b) FP is processor dependent. So, old 80386 processors without FP instructions shouldn't work (IMO, this is not an issue ). Also, maybe we may have some troubles on a few non-x86 architectures (ARM ?). Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kernelspace floating pointer - was Re: Port of em28xx and xc3028 to new hybrid tuner framework.
On 9/8/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Markus wrote: the em28xx uses the userland implementation since the current xceive reference drivers use floating point algorithms. The usage of FP on DVB drivers is something that have been discussed for quite a long time at the community. I've asked Linus about the possibility of having a kernelspace driver using floating point. This may eventually happen (and, in fact, it already happens on a few drivers). There are, however, two points to consider: a) care should be taken to preserve FP state by the driver, since kernel won't do this by itself. This probably means that this may not be so fast as userspace calculation (although I suspect that it will be faster enough for the current needs); b) FP is processor dependent. So, old 80386 processors without FP instructions shouldn't work (IMO, this is not an issue ). Also, maybe we may have some troubles on a few non-x86 architectures (ARM ?). As you know the userspace tuner framework is capable of solving this and even more problems. http://mcentral.de/wiki/index.php/Userspace_tuner Although I'm waiting for an ack from several companies to reuse their tuner sample drivers without doing much conversion (so far there's an Ack for Quantek tuners) In case of the userspace framework better see the em28xx driver as a field test I won't submit an Ack for something else since I'm doing ongoing support for newer silicons (which are not only limited to Xceive based devices) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
Hi Paolo, Am Freitag, den 07.09.2007, 10:15 +0200 schrieb Paolo Dell'Aquila: hermann pitton wrote: Can not reproduce your problem on a 32bit machine with the Asus P7131 Dual. If I fake frequencies out of range in my tzap channels.conf, the error behavior is OK, also I can still tune to the valid frequencies. YEP YEP YEP SOLVED I want to thank you all. Lot of you asked me to check my channels.conf. That is what put me on the right direction. The card was working fine on my WinXP machine so it wasn't an hardware problem. fine, at least no hardware damage yet. The reported error was in dmesg so I had only two alternatives: a driver problem or a buggy software launched at start time. Damn... a daemon... or a server... I checked all my channels.conf: they were right and all the programs using channels.conf (vdr, tzap, mplayer) were not launched at boot time. Mmmm... MythTv-backend was the only one started in background during startup... ... so I removed it and... TA-DA everything works fine again. It's a mystery why Mythtv-backend was trying to use the driver: there was no scheduled activities... ... and it's a mystery (for me) why it wasn't possible to use the driver after that buggy activity. The application developers will see it the other way round. These are buggy drivers. Radio doesn't work for you. Are you sure you have still gpio 0x020 for radio and not 0x000 ? It wasn't possible to use anything after the mythtv backend activity. Just noise on radio and jumping images with a lot of noise with anolog tv. But now everything is going fine. ## ACTUAL SITUATION ## 1) patched v4l with your patches so dvb-t is binded to the same analog-tv antenna. (cannot understand why I have to patch also saa7134-cards.c with gpi=0x000 bit I did it, LOL) I told you, if you want to use DVB-T at once with an external s-video or composite input, like from a VCR, you need this not to lose DVB-T. 2) analog tv: perfect 3) Couldn't make the patch cable working. Still have to use aplay or sox 4) kaffeine on dvb-t perfect 5) mplayer with analog tv: perfect 6) mplayer with dvb-t: solved now! It doesn't like all those auto in channels.conf. Changed them and mplayer started working. So the only problem now is with the patch cable. Since I don't have the card and digging into all postings is lost of life time, find someone with the same card to confirm the unexpected. Thanks again to all of you for helping me to solve this problem. ciao paolo Have some fun. ciao hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asys P7131 Hybrid: DVB out of range
Hi Paolo, Am Freitag, den 07.09.2007, 10:15 +0200 schrieb Paolo Dell'Aquila: hermann pitton wrote: Can not reproduce your problem on a 32bit machine with the Asus P7131 Dual. If I fake frequencies out of range in my tzap channels.conf, the error behavior is OK, also I can still tune to the valid frequencies. YEP YEP YEP SOLVED I want to thank you all. Lot of you asked me to check my channels.conf. That is what put me on the right direction. The card was working fine on my WinXP machine so it wasn't an hardware problem. fine, at least no hardware damage yet. The reported error was in dmesg so I had only two alternatives: a driver problem or a buggy software launched at start time. Damn... a daemon... or a server... I checked all my channels.conf: they were right and all the programs using channels.conf (vdr, tzap, mplayer) were not launched at boot time. Mmmm... MythTv-backend was the only one started in background during startup... ... so I removed it and... TA-DA everything works fine again. It's a mystery why Mythtv-backend was trying to use the driver: there was no scheduled activities... ... and it's a mystery (for me) why it wasn't possible to use the driver after that buggy activity. The application developers will see it the other way round. These are buggy drivers. Radio doesn't work for you. Are you sure you have still gpio 0x020 for radio and not 0x000 ? It wasn't possible to use anything after the mythtv backend activity. Just noise on radio and jumping images with a lot of noise with anolog tv. But now everything is going fine. ## ACTUAL SITUATION ## 1) patched v4l with your patches so dvb-t is binded to the same analog-tv antenna. (cannot understand why I have to patch also saa7134-cards.c with gpi=0x000 bit I did it, LOL) I told you, if you want to use DVB-T at once with an external s-video or composite input, like from a VCR, you need this not to lose DVB-T. 2) analog tv: perfect 3) Couldn't make the patch cable working. Still have to use aplay or sox 4) kaffeine on dvb-t perfect 5) mplayer with analog tv: perfect 6) mplayer with dvb-t: solved now! It doesn't like all those auto in channels.conf. Changed them and mplayer started working. So the only problem now is with the patch cable. Since I don't have the card and digging into all postings is lost life time, find someone with the same card to confirm the unexpected. Thanks again to all of you for helping me to solve this problem. ciao paolo Have some fun. ciao hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] optimizing QT1010 driver was Re: Kernelspace floating pointer
Markus Rechberger wrote: As you know the userspace tuner framework is capable of solving this and even more problems. http://mcentral.de/wiki/index.php/Userspace_tuner Although I'm waiting for an ack from several companies to reuse their tuner sample drivers without doing much conversion (so far there's an Ack for Quantek tuners) Do you have a written reply from someone at reasonable high position at Transcom ? (I mean not from some FAE or a normal programmer) If so, can you provide a copy of the reply ? of course you may mask the addresses. The reason why i ask is this: We can optimize the existing qt1010 kernel driver if you have reached an agreement (all this while they never agreed for the same) with them and hence my question. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kernelspace floating pointer - was Re: Port of em28xxand xc3028 to new hybrid tuner framework.
Mauro Carvalho Chehab wrote: Markus wrote: the em28xx uses the userland implementation since the current xceive reference drivers use floating point algorithms. Hauppauge removed the floating point code and I expect to put that into the upcoming linux driver. - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
