Re: [linux-dvb] How can I ever succeed using DVB-T on Gentoo Linux?
En/na Jesper Taxbøl ha escrit: A AGK stick (USB ID: 15a4:9020), that is recognized as an af9005 device, but it cant scan any services. Yes, this is a known problem, and unfortunately I don't have a solution (besides, I don't have a working af9005 anymore). However, if you manage to get a ready made channels.conf[*] it should work, albeit switching channel is slow (I suspect this is the reason that scanning fails) [*]When my stick worked, I used vdr with an incomplete channels.conf and it managed to find the remaining channels. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] ansonic branded dvb-t usb stick support in the af9005 driver
Hello,
a user (Marcos Melero, marcosmelero at gmail.com) reported he could make
his dvb-t usb stick work with the af9005 driver by changing the device
ids (10b9:6000).
The stick is branded Ansonic (one of the brands of a spanish chain of
supermarkets) with no other identification of the model.
Since neither Marcos nor me know the OEM for the stick, in the attached
patch I used Ansonic for the ids/description.
Feel free to change the ids or add to the description if you know the
real OEM.
Signed-off-by: Luca Olivetti [EMAIL PROTECTED]
Bye
--
Luca
diff -r 7564c110491e linux/drivers/media/dvb/dvb-usb/af9005.c
--- a/linux/drivers/media/dvb/dvb-usb/af9005.c Sun Jan 20 09:13:44 2008 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/af9005.c Sun Jan 20 21:42:48 2008 +0100
@@ -1026,6 +1026,7 @@ static struct usb_device_id af9005_usb_t
static struct usb_device_id af9005_usb_table[] = {
{USB_DEVICE(USB_VID_AFATECH, USB_PID_AFATECH_AF9005)},
{USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_CINERGY_T_USB_XE)},
+ {USB_DEVICE(USB_VID_ANSONIC, USB_PID_ANSONIC_DVBT_USB)},
{0},
};
@@ -1075,7 +1076,7 @@ static struct dvb_usb_device_properties
.rc_key_map_size = 0,
.rc_query = af9005_rc_query,
- .num_device_descs = 2,
+ .num_device_descs = 3,
.devices = {
{.name = Afatech DVB-T USB1.1 stick,
.cold_ids = {af9005_usb_table[0], NULL},
@@ -1083,6 +1084,10 @@ static struct dvb_usb_device_properties
},
{.name = TerraTec Cinergy T USB XE,
.cold_ids = {af9005_usb_table[1], NULL},
+ .warm_ids = {NULL},
+ },
+ {.name = Ansonic DVB-T USB1.1 stick,
+ .cold_ids = {af9005_usb_table[2], NULL},
.warm_ids = {NULL},
},
{NULL},
diff -r 7564c110491e linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Sun Jan 20 09:13:44 2008 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Sun Jan 20 18:07:31 2008 +0100
@@ -15,6 +15,7 @@
#define USB_VID_ALCOR_MICRO 0x058f
#define USB_VID_ALINK0x05e3
#define USB_VID_ANCHOR0x0547
+#define USB_VID_ANSONIC0x10b9
#define USB_VID_ANUBIS_ELECTRONIC 0x10fd
#define USB_VID_AVERMEDIA 0x07ca
#define USB_VID_COMPRO0x185b
@@ -53,6 +54,7 @@
#define USB_PID_ADSTECH_USB2_WARM 0xa334
#define USB_PID_AFATECH_AF90050x9020
#define USB_VID_ALINK_DTU0xf170
+#define USB_PID_ANSONIC_DVBT_USB 0x6000
#define USB_PID_AVERMEDIA_DVBT_USB_COLD 0x0001
#define USB_PID_AVERMEDIA_DVBT_USB_WARM 0x0002
#define USB_PID_AVERMEDIA_DVBT_USB2_COLD 0xa800
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] some questions on cx23885/xc3028
En/na Steven Toth ha escrit: Personally, I don't knw much about our USB v4l trees, or whether it will be simple enough to add (atleast analog) support. Looks like digital might be done via the AF9013, but that's a guess and I'm not familiar with it, I think this is an Auvitek part. afatech most probably. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with Hauppauge Nova-TD
Nicolas Will wrote: On Wed, 2007-12-12 at 22:49 +0100, Luca wrote: I have this DVB-T USB device: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick It seem supported by difference sources: http://cateee.net/lkddb/web-lkddb/DVB_USB_DIB0700.html (PCI ID 2040:9580). I tried to find the correct firmware, I loaded/unloaded drivers for all the day (dib0700 is the correct one, right?), but nothing happens: dmesg reports: ... Dec 12 22:02:25 sirius kernel: dib0700: loaded with support for 2 different device-types Dec 12 22:02:25 sirius kernel: usbcore: registered new interface driver dvb_usb_dib0700 ... The firmware name is dvb-usb-dib0700-01.fw and it's located to /lib/firmware/`uname -r`/... I'm not sure I have the correct firmware (I tried to get it from Windows driver installation and from web, but I didn't found anything intersting). I would strongly suggest that you follow the instructions there: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Making_it_work Make sure you follow the instructions in the note (get the 1.10 firmware). And then compile a v4l-dvb tree. Tell us what it does for you, but I think it should mostly sort you out. If it does, the -TD stick wiki page would need content. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick Nico Thank you for response... My dmesg is happy: ... dib0700: loaded with support for 5 different device-types dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) DVB: registering frontend 0 (DiBcom 7000PC)... MT2266: successfully identified dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input11 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity successfully initialized and connected. usbcore: registered new interface driver dvb_usb_dib0700 I have 2 adapters now in /dev/dvb. But (there's always a but!)... I tried to find out my channels.conf: At first, I've used the it-Varese, because I live there, but scan give me the following output: scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/it-Varese scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/it-Varese using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 22650 1 2 1 3 1 0 0 initial transponder 70600 0 2 1 3 1 0 0 initial transponder 60200 0 2 1 3 1 0 0 initial transponder 51400 0 2 1 3 1 0 0 initial transponder 61000 0 2 1 3 1 0 0 tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 tune to: 70600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 tune to: 60200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 60200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 51400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 51400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 61000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 61000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! dumping lists (0 services) Done. Since no channel was found, I've used w_scan binary, maybe my zone is not served as specified in it-Varese: ./w_scan w_scan version 20071209 Info: using DVB adapter auto detection. Found DVB-T frontend. Using adapter /dev/dvb/adapter0/frontend0 -_-_-_-_ Getting frontend capabilities-_-_-_-_ frontend DiBcom 7000PC supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ ... 226500: 474000: signal ok (I999B8C999D999M999T999G999Y999) 482000: ... 618000: 626000: signal ok
Re: [linux-dvb] Problem with Hauppauge Nova-TD
Well... the device seem working properly after I put the firmware in /lib/firmware... maybe before I was using the wrong one... mah! Now dib0700 module say me that loads the firmware at ... (really two different firmwares, 1.10 and 03-pre). I don't know if it can work with both antennas... I'm playing with them, because I think it's an antenna problems... Kaffein is awesome! But sadly I cannot find any channel... sigh... Still trying here. Thank! I will let you know... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem with Hauppauge Nova-TD
I have this DVB-T USB device: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick It seem supported by difference sources: http://cateee.net/lkddb/web-lkddb/DVB_USB_DIB0700.html (PCI ID 2040:9580). I tried to find the correct firmware, I loaded/unloaded drivers for all the day (dib0700 is the correct one, right?), but nothing happens: dmesg reports: ... Dec 12 22:02:25 sirius kernel: dib0700: loaded with support for 2 different device-types Dec 12 22:02:25 sirius kernel: usbcore: registered new interface driver dvb_usb_dib0700 ... The firmware name is dvb-usb-dib0700-01.fw and it's located to /lib/firmware/`uname -r`/... I'm not sure I have the correct firmware (I tried to get it from Windows driver installation and from web, but I didn't found anything intersting). I'm so sad... I don't know if it's a software bug, and wrong firmware or something else. I have installed a linux kernel 2.6.22-14. What am I missing? Many thanks to everyone. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linuxtv.org fell in the blacklists trap
En/na Johannes Stezenbach ha escrit: On Tue, Oct 30, 2007, Luca Olivetti wrote: El Tue, 30 Oct 2007 18:41:27 +0100 is the first complaint since I switched to safe.dnsbl.sorbs.net about one year ago) It doesn't surprise me, since those affected cannot contact you. It's the perfect system to avoid complaints ;-) Bullshit. Just a suggestion: If you run your own mailserver you should probably read RFC 2821. Frankly, I didn't check if linuxtv.org follows rfc2821 (and now that I'm delisted I cannot check), however most of the sites that blindly rely on flawed blacklists don't usually honour rfc2821 either (I suppose you refer to section 4.5.1). Or failing that, you could just ask someone else to forward a message for you, or ask Mauro or one of the other developers for help. Yes, there are workarounds for linuxtv.org. In other cases it may not be so simple to contact the administrador (see above). And, again, I shouldn't go through all this hassle: I did nothing wrong. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linuxtv.org fell in the blacklists trap
En/na Johannes Stezenbach ha escrit: Fighting spam is always a matter of effort. I didn't do the current setup (Ralf H. did), but I had to choose some replacement DNSBLs because those which were used originally went out of existance. if it's one I had to deal with, good riddance! (I don't remember the name, but I do remember that they didn't listen to you. I was very glad when I saw them disappear). It seemed to be popular in Germany, so maybe it's the same. Maybe there's a better replacement for safe.dnsbl.sorbs.net, I'll try to look into it at the weekend. But I don't have the time to change the whole setup now, and just installing spamd won't cut it as this thing eats too much CPU with the amount of spam that hits linuxtv.org. Greylisting and sender address verification don't suck too much cpu (though the latter may not be advisable on high traffic sites, and the former doesn't work with some broken senders). Both will let some spam through, though they don't give false positives. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] OT: Re: linuxtv.org fell in the blacklists trap
En/na David Santinoli ha escrit: On Wed, Oct 31, 2007 at 12:28:52AM +0100, Luca Olivetti wrote: Besides, one shouldn't have more or less rights to have an own mail server depending on the fact that the address is static or dynamic. Please get real. While you have all the right to choose to run a mail server on a dynamic IP address, you cannot force your policy on the recipients. Considering that the overwhelming majority of the SMTP connections from dynamic addresses are originated by spambots, it is perfectly advisable to refuse mail from such servers, as any sensible mail administrator knows. Oh, and any sensible mail administration (as you define it) knows, the overwhelming majority of the SMTP traffic originating from the US of A is spam, so you should block that too, shouldn't you? (Note that this is as flawed an argument as yours). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] linuxtv.org fell in the blacklists trap
[resending because I was also kicked off the list, so sorry for the, h, spam, but it's not my fault] In a misguided attempt to curb spam, someone at linuxtv.org decided to use the sorbs blacklist. Like most other blacklists out there, it is *not* accurate in its listings, in fact it listed my *static* ip address (with a rDNS that clearly indicates that is *static*) as a dynamic one. (besides, I don't think discriminating small, legitimate, servers for the type of address is a good idea, though I can understand that someone could think so without realizing the full consequences). This is the second times it happens in a few months, they have delisted me (again), but in the meanwhile I lost possibly some interesting messages[*]. Other blackists are even worse, since they don't even listen to you, I'll concede that to sorbs, still, the concept is a flawed one. I suppose I'm not the only one in this situation, and it's extremely annoying when you find that you cannot communicate effectively because someone decided to use some random blacklist, hence I think than blacklists (and moreso those using them) are part of the problem, not part of the solution, I'll even say that are evil, since they block more legitimate mail than spam. Please reconsider the decision of using blacklists, *any* blacklist, no matter how well maintained they are, they *will* from time to time block innocent bystanters (like me or you). You can tell me I should use my ISP mail server instead of my own, but that's like telling me not to write my own drivers and to just use windows or macos, where qualified professionals already did the job for me. If you decide to go on relying on blacklists, at least use the one listing confirmed sources of spam, not the broader one using arbitrary and flawed criteria (like all supposedly dynamic/residential/adsl addresses, or all the ip from china, etc.). [*]since I don't accept mail from addresses that won't accept mine[**], I wasn't receiving any mail from linuxtv.org. At first I thought things were strangely quiet, but then I saw in my logs the sorbs error messages. [**] this is the only way for the other party to know that their isp is blocking legitimate email (thrugh the bounce message). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linuxtv.org fell in the blacklists trap
El Tue, 30 Oct 2007 18:41:27 +0100 is the first complaint since I switched to safe.dnsbl.sorbs.net about one year ago) It doesn't surprise me, since those affected cannot contact you. It's the perfect system to avoid complaints ;-) it has very low priority for me, sorry. Well, I hope you reconsider. As I said I was wrongly listed. Twice. One day the same could happen to you, then you'll understand. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] OT: Re: linuxtv.org fell in the blacklists trap
En/na Jim Barber ha escrit: Sorbs will remove you from their list once you contact them and prove you have a static IP address though. Yes, they did, *twice*, since they wrongly listed my address *twice* (though I thought I already stated that) but I shouldn't go through all of this. Besides, one shouldn't have more or less rights to have an own mail server depending on the fact that the address is static or dynamic. And others blacklists don't even listen to you (and, again, even if they would, it's tiresome and shouldn't be necessary). The net result is that spammers simply hop from network to network and can send their shit with no problem, while non-spam is blocked. Good job. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy T USB XE, Rev. 2?
En/na [EMAIL PROTECTED] ha escrit: Luca Olivetti says on his page that rev. 2 of the terratec cinergy t usb xe does not use a af9005, and thus will not work with the af9005 firmware, of course; so I suspect I got one of these... What driver should I try next? Well, I don't know if the term rev.2 is actually correct, I was told that there are two models, one with the af9005 and one without. I don't have any of those, so I cannot say if is there some external identification to tell the difference. Anyway, I don't know the answer to your question :-( Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Fwd: making af9005 on ubuntu gutsy with 2.6.22-12-generic
En/na Markus Rechberger ha escrit: -- Forwarded message -- From: Joachim Neu [EMAIL PROTECTED] Date: Sat, 06 Oct 2007 11:01:23 +0200 Subject: making af9005 on ubuntu gutsy with 2.6.22-12-generic To: linux-dvb@linuxtv.org Cc: [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi everybody, i tried to make the af9005 on ubuntu gutsy (comes with 2.6.22-12-generic) but i got an error in /af9005/v4l/dvb_net.c on line 186. In function 'dvb_net_eth_type_trans': error: 'struct sk_buff' has no member named 'mac' i fixed the problem by just commenting out this line. after that it worked! maybe someone can fix this inside the source? thank you, you're doing a great job! since the af9005 has nothing to do with dvb_net.c I suppose he is using this repository http://linuxtv.org/hg/~manu/af9005/ and it's possible it has some problem compiling with newer kernels. The af9005 is now in the main dvb repository, so there's no need to use an old one. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech 9005 USB DVB-T Problems
En/na Lee and Vicki ha escrit: lsusb -v / messages and syslog are all uploaded here http://h0td.com/af9005/ in syslog.txt I only see messages for the connection and disconnection of the device, I don't see anything coming from the dvb modules. Are they automagically loaded? If so, are the debug messages disables or your syslogd is configured to send them somewhere else? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech 9005 USB DVB-T Problems
En/na Lee and Vicki ha escrit: Ignore that last bit, I was having a serious braindead moment, of course its /usr/src/2.6.22/ Oh, I've misinterpreted this Ignore and I ignored the whole message. Now I checked it and I see that in yout make.txt it isn't compiling the af9005 modules, so it's unsurprising that it doesn't work!. Why it doesn't compile them? I don't know, I just followed the instructions at http://linuxtv.org/repo/ and it compiles here Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech 9005 USB DVB-T Problems
En/na Lee and Vicki ha escrit: I don't see anything coming from the dvb modules. Are they automagically loaded? If so, are the debug messages disables or your syslogd is configured to How can I check this ? You can check that the modules are loaded, with lsmod (you should see, among the rest, dvb_usb_af9005). The debug at compile time is enabled with CONFIG_DVB_USB_DEBUG (check that it's set to y in v4l/.config, I think that's the default when you take the mercurial tree). And where the messages go is controlled by /etc/syslog.conf, usually /var/log/syslog has everything, but one newer knows. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AF9005 remote control
En/na Moisés Pérez ha escrit: [ 2953.248000] dvb_usb_af9005_lirc: Unknown symbol lirc_unregister_plugin [ 2953.248000] dvb_usb_af9005_lirc: Unknown symbol lirc_register_plugin My kernel version is 2.6.20-16-generic installed by apt-get from ubuntu repository. Lirc version is lirc-0.8.2, installed by apt-get too. Should it work if I compile lirc instead of using pre-compiled packages?¿ I suppose you just installed the userspace programs and are missing the kernel modules. I don't know the proper way to get/install lirc kernel modules under debian/ubuntu, under mandriva it works out of the box. Thank you very much for your help!! I thing that my remote is different of yours and it doesn't workneither with af9005-remote or with af9005-lirc (because I can't [don't know how] configure it. with the dvb-usb-af9005-lirc module it should work with any remote, it's only (much) more convoluted to setup. I see it!! But my remote ( see it on link http://img85.imageshack.us/my.php?image=p9160087cp0.jpg) doesn't work correctly with the af9005-remote driver provided by linux-dvb sources. It creates a input device that I can't get any input from it, or directly doesn't appear the just created devide on my /dev/input. as I said before, try to load the dvb-usb-af9005-remote module with debug=1 (hint, if modprobe ignores the parameter, you can echo 1 /sys/module/dvb_usb_af9005_remote/parameters/debug) and try to see where your syslogd is sending kernel messages (check /etc/syslog.conf). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AF9005 remote control
El Sun, 16 Sep 2007 15:37:33 +0200 Moisés Pérez [EMAIL PROTECTED] escribió: [please keep this on the list] 2007/9/15, Luca Olivetti [EMAIL PROTECTED]: En/na Moisés Pérez ha escrit: Searching on luca's web, I found a new Readme.lirc and a af9005-lirc.c. I tried build it as readme says and I got lots of make errors: I've modified the Makefile in correct folder and added the flag -I/usr/src/lirc-0.8.1/, just where I've decompressed the lirc sources. At the time I tried it with lirc 0.8.1 and lirc-0.6.6, so it should work I could compile it!! The Include was -I/usr/src/lirc- 0.8.2/, not -0.8.1 I erased the original module af9005-remote and put the new lines in Makefile.The compilation was succesfully. I have any questions: 1 - the dvb-usb-af9005-lirc module (if i can compile it) will be as a module of lirc defaults?? how is it used?? the module replaces the standard one (so make sure the standard one isn't found/loaded). The standard modules supplied with the driver decodes the ir code of a couple of remotes: the one I got with my card and one of another user. The standard modules emulates an input device (like all other remotes in linux-dvb do, since most devices don't give you the complete ir stream but decode it themselves in firmware): if it works you should try to press e.g. 1 and you should see a 1 on the console like you typed it on the keyboard. OTOH the lirc module doesn't try to decode the ir, but just massages it in a format that lirc understands, so you can use it like a lirc homebrew receiver. Now I can understand it. If I use the provided remote module, It would have to work writing in console as a input device (I have another remote recognized as HID usb that works so) yes But after compiling, dmesg insert the correct modules: $dmesg: [ 6912.376000] DVB: registering new adapter (Afatech DVB-T USB1.1 stick) [ 6912.384000] DVB: registering frontend 0 (AF9005 USB DVB-T)... [ 6912.384000] input: IR-receiver inside an USB DVB receiver as /class/input/input10 IIRC this message comes from the dvb-usb infrastructure when using the standard module, not the lirc one (but I may be wrong, it's been a while since I did this) [ 6912.384000] dvb-usb: schedule remote query interval to 200 msecs. [ 6912.384000] dvb-usb: Afatech DVB-T USB1.1 stick successfully initialized and connected. $ modprobe -l | grep af9005 /lib/modules/2.6.20-16-generic/kernel/drivers/media/dvb/dvb-usb/dvb- usb-af9005.ko /lib/modules/2.6.20-16-generic/kernel/drivers/media/dvb/dvb-usb/dvb- usb-af9005-lirc.ko the module is charged!! 2 - the remote module charged with v4l-dvb standards modules doesn't work?? Can't be used with lirc or another way?? It can be used with lirc but I lost the link where it explains how to convert the input device to a lirc device. Note that with the standard method it only recognizes the supplied remote anyway, so it's of limited use, while my alternative lirc module should work with any remote (once you configured it with irrecord). Now, with the af9005-lirc module charged, is it recognised as /dev/input/event10, but it doesn't be: no, with the lirc module you should configuire it with irrecord and use it with lircd, see the lirc documentation b$ ls /dev/input/e* /dev/input/event0 /dev/input/event3 /dev/input/event6 /dev/input/event9 /dev/input/event1 /dev/input/event4 /dev/input/event7 /dev/input/event2 /dev/input/event5 /dev/input/event8 I've read about inputlirc for configure lirc with the inputs from a device recognized as a device input (when it's a IR one). Either I can't make it work ¿How have to be used the af9005-irc module?? 3 - dmesg seems to recognize the IR-receiver inside of USB DVB receiver as /class/input/input11, can be lirc configured to use it?? On README.lirc he said he have a serial IR receiver, but can we use lirc with the IR-receiver inside of dongle?? if you want to use it with any remote, make sure the standard module isn't loaded and load the lirc one. Then look at lirc documentation on how to use it. OTOH if the standard remote is enough for you, try to see if the standard module works. If it does, you just have to configure your software to use the input device, if it doesn't probably your remote is different and we can try to discover its codes to put in the driver table. As I could understand, the standard module, if working, I could type in console directly with it. Using the new if9005-lirc module, I could use any remote with the receptor inside the dongle. Now only I have available the receptor's remote control, then, I could want make it work. Then, the new module get the complete IR string from IR dongle receptor (with any remote control) and send it to LIRC but, ¿How can i do to send it? It is recognized as an input device. again
Re: [linux-dvb] AF9005 remote control
En/na Moisés Pérez ha escrit: Searching on luca's web, I found a new Readme.lirc and a af9005-lirc.c. I tried build it as readme says and I got lots of make errors: I've modified the Makefile in correct folder and added the flag -I/usr/src/lirc-0.8.1/, just where I've decompressed the lirc sources. At the time I tried it with lirc 0.8.1 and lirc-0.6.6, so it should work I have any questions: 1 - the dvb-usb-af9005-lirc module (if i can compile it) will be as a module of lirc defaults?? how is it used?? the module replaces the standard one (so make sure the standard one isn't found/loaded). The standard modules supplied with the driver decodes the ir code of a couple of remotes: the one I got with my card and one of another user. The standard modules emulates an input device (like all other remotes in linux-dvb do, since most devices don't give you the complete ir stream but decode it themselves in firmware): if it works you should try to press e.g. 1 and you should see a 1 on the console like you typed it on the keyboard. OTOH the lirc module doesn't try to decode the ir, but just massages it in a format that lirc understands, so you can use it like a lirc homebrew receiver. 2 - the remote module charged with v4l-dvb standards modules doesn't work?? Can't be used with lirc or another way?? It can be used with lirc but I lost the link where it explains how to convert the input device to a lirc device. Note that with the standard method it only recognizes the supplied remote anyway, so it's of limited use, while my alternative lirc module should work with any remote (once you configured it with irrecord). 3 - dmesg seems to recognize the IR-receiver inside of USB DVB receiver as /class/input/input11, can be lirc configured to use it?? On README.lirc he said he have a serial IR receiver, but can we use lirc with the IR-receiver inside of dongle?? if you want to use it with any remote, make sure the standard module isn't loaded and load the lirc one. Then look at lirc documentation on how to use it. OTOH if the standard remote is enough for you, try to see if the standard module works. If it does, you just have to configure your software to use the input device, if it doesn't probably your remote is different and we can try to discover its codes to put in the driver table. Bye -- Luca ___ 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
En/na Markus Rechberger ha escrit: Hi, On 9/3/07, Holger Dehnhardt [EMAIL PROTECTED] wrote: [...] I searched this mailing list and after that tried to find the USB id (0ccd:0058 TerraTec Electronic GmbH) in the source code, but I couldn't fint [...] Maybe you should have a look at: http://ventoso.org/luca/af9005/ Not sure if that driver will work with your device although you might give it a try. I doubt it: the Terratec XE that has an af9005 onboard has the usb id 0ccd:0055 You know how these things work: the manufacturers always give the same name to completely different devices :-( Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] add read_signal_strength function to dvb_tuner_ops
En/na Mauro Carvalho Chehab ha escrit: Sorry for a late response. I was in transit to participate at Linux Conf And sorry if I piggiback on your reply, but what about finally defining what these values are supposed to mean (like they were in an older revision of the dvb api), so that driver developers know what they should return and application developers know what to display to the user? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problems with Afatech af9005
En/na Daniel Klose ha escrit: after a while it also shows this line: Quantek QT1010 successfully identified. but i cant really tell you after what time it shows this. when you first open the device it tries to access the tuner. scan -n -o zap -p /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane channels.conf gives me the following: scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 22650 1 3 9 3 1 1 0 initial transponder 17750 1 2 9 3 1 2 0 initial transponder 191625000 1 3 9 3 1 1 0 initial transponder 21950 1 3 9 3 1 1 0 initial transponder 585625000 1 2 9 3 1 2 0 tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 WARNING: filter timeout pid 0x0010 [] You're not the first one reporting problems with scan and the af9005, unfortunately I couldn't find if is there an error in the driver at the time, and I cannot test it now since my stick doesn't work (the manufacturer promised me a sample a couple of months ago but I haven't received it yet). *However* the device should work once you have a channels.conf. When it worked, I used it with vdr and it managed to pull the complete channel list from a few seed channels. Ps.: the vendor offered me to send it back and get an afatech af9015 instead ?? is this one better supported ? i read its driver is not finished yet. There's no released driver yet, but the af9015 is an usb2.0 device, so you could use it to get the whole TS or HD channels. You cannot do that with the af9005. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compiling dvb-usb-adapter module outside the kernel source.
En/na lwtbenben ha escrit: Hi, everyone Which header files should be include in the cxusb.c if I want to compile the module outside Linux kernel tree? The mercurial repository you can download from linuxtv.org *is* compilable out of the tree as is: http://linuxtv.org/repo/ Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compiling dvb-usb-adapter module outside the kernel source.
En/na [EMAIL PROTECTED] ha escrit: Thanks for the utterly useless answer. He wanted to know the steps to compile a module out of the kernel not a confirmation your shit works. Go, read again the OP question. Here's a useful link for you: http://tinyurl.com/33dk6p (though maybe it's too challenging for you) Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compiling dvb-usb-adapter module outside the kernel source.
En/na timecop ha escrit: On 8/1/07, Luca Olivetti [EMAIL PROTECTED] wrote: En/na [EMAIL PROTECTED] ha escrit: Stop fucking replying to my mail in foreign language. I don't give a shit your mail client shows up in greek, have common courtesy not to inject this AIDS-filled language into my mailbox. Now on to the original problem, Hi, everyone Which header files should be include in the cxusb.c if I want to compile the module outside Linux kernel tree? I found some module in file Documentation/kbuild/modules.txt, but it just needs many header files, but I have no idea, please give me some advice. If you paid even slightest attention to this individual, he's working/trying to hack together some modules for some unsupported chinese DVB card. Clearly he's not trying to compile your code or any of the filth from hg whatever that is. He just wants to know HOW TO SETUP THE BUILD ENVIRONMENT TO ALLOW COMPILING HIS CUSTOM MODULE OUTSIDE THE FUCKING KERNEL TREE. Silly me, I just thought he wanted to compile cxusb.c (which is included in the hg repository) outside the tree. Next time I'll let Grover explain you the difference between far and near. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] How to gather Signal Quality information from DVB drivers
En/na Morgan Tørvolt ha escrit: your real problem is not the quality part of this equation really. It is the fact that all drivers implement this differently. That's not surprising, since the current api specification doesn't tell what these values are supposed to mean An old version of the api did specify everythin, but various question here by me and others asking if the old specification is still valid (or if not how to fill these values) have remained unanswered. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [patch] af9005 fix tuner module unload
Hello,
this patch removes the useless tuner field and avoids a double free of
the tuner (either mt2060 or qt1010).
Signed-off-by: Luca Olivetti [EMAIL PROTECTED]
--
Luca
diff -r 76b92a337aec linux/drivers/media/dvb/dvb-usb/af9005-fe.c
--- a/linux/drivers/media/dvb/dvb-usb/af9005-fe.c Wed Jun 13 15:11:15 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/af9005-fe.c Fri Jun 15 01:26:16 2007 +0200
@@ -29,8 +29,6 @@
struct af9005_fe_state {
struct dvb_usb_device *d;
- struct dvb_frontend *tuner;
-
fe_status_t stat;
/* retraining parameters */
@@ -454,7 +452,7 @@ static int af9005_fe_read_status(struct
#endif
int ret;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
*stat = 0;
@@ -512,7 +510,7 @@ static int af9005_fe_read_ber(struct dvb
static int af9005_fe_read_ber(struct dvb_frontend *fe, u32 * ber)
{
struct af9005_fe_state *state = fe-demodulator_priv;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
af9005_fe_refresh_state(fe);
*ber = state-ber;
@@ -522,7 +520,7 @@ static int af9005_fe_read_unc_blocks(str
static int af9005_fe_read_unc_blocks(struct dvb_frontend *fe, u32 * unc)
{
struct af9005_fe_state *state = fe-demodulator_priv;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
af9005_fe_refresh_state(fe);
*unc = state-unc;
@@ -536,7 +534,7 @@ static int af9005_fe_read_signal_strengt
int ret;
u8 if_gain, rf_gain;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
ret =
af9005_read_ofdm_register(state-d, xd_r_reg_aagc_rf_gain,
@@ -827,11 +825,11 @@ static int af9005_fe_power(struct dvb_fr
#if 0
if (ret)
return ret;
- if (state-tuner != NULL) {
+ if (fe-ops.tuner_ops.init != NULL) {
if (on)
- ret = state-tuner-ops.tuner_ops.init(state-tuner);
+ ret = fe-ops.tuner_ops.init(fe);
else
- ret = state-tuner-ops.tuner_ops.sleep(state-tuner);
+ ret = fe-ops.tuner_ops.sleep(fe);
}
#endif
return ret;
@@ -1135,7 +1133,7 @@ static int af9005_fe_init(struct dvb_fro
return ret;
#endif
/* attach tuner and init */
- if (state-tuner == NULL) {
+ if (fe-ops.tuner_ops.release == NULL) {
/* read tuner and board id from eeprom */
ret = af9005_read_eeprom(adap-dev, 0xc6, buf, 2);
if (ret) {
@@ -1152,20 +1150,16 @@ static int af9005_fe_init(struct dvb_fro
return ret;
}
if1 = (u16) (buf[0] 8) + buf[1];
- state-tuner =
- dvb_attach(mt2060_attach, fe, adap-dev-i2c_adap,
- af9005_mt2060_config, if1);
- if (state-tuner == NULL) {
+ if (dvb_attach(mt2060_attach, fe, adap-dev-i2c_adap,
+ af9005_mt2060_config, if1) == NULL) {
deb_info(MT2060 attach failed\n);
return -ENODEV;
}
break;
case 3: /* QT1010 */
case 9: /* QT1010B */
- state-tuner =
- dvb_attach(qt1010_attach, fe, adap-dev-i2c_adap,
- af9005_qt1010_config);
- if (state-tuner == NULL) {
+ if (dvb_attach(qt1010_attach, fe, adap-dev-i2c_adap,
+ af9005_qt1010_config) ==NULL) {
deb_info(QT1010 attach failed\n);
return -ENODEV;
}
@@ -1174,7 +1168,7 @@ static int af9005_fe_init(struct dvb_fro
err(Unsupported tuner type %d, buf[0]);
return -ENODEV;
}
- ret = state-tuner-ops.tuner_ops.init(state-tuner);
+ ret = fe-ops.tuner_ops.init(fe);
if (ret)
return ret;
}
@@ -1212,7 +1206,7 @@ static int af9005_fe_set_frontend(struct
deb_info(af9005_fe_set_frontend freq %d bw %d\n, fep-frequency,
fep-u.ofdm.bandwidth);
- if (state-tuner == NULL) {
+ if (fe-ops.tuner_ops.release == NULL) {
err(Tuner not attached);
return -ENODEV;
}
@@ -1300,7 +1294,7 @@ static int af9005_fe_set_frontend(struct
#endif
/* set tuner */
deb_info(set tuner\n);
- ret = state-tuner-ops.tuner_ops.set_params(state-tuner, fep);
+ ret = fe-ops.tuner_ops.set_params(fe, fep);
if (ret)
return ret;
@@ -1576,12 +1570,6 @@ static void af9005_fe_release(struct dvb
{
struct af9005_fe_state *state =
(struct af9005_fe_state *)fe-demodulator_priv;
- if (state-tuner != NULL state-tuner-ops.tuner_ops.release != NULL) {
- state-tuner-ops.tuner_ops.release(state-tuner);
-#ifdef CONFIG_DVB_CORE_ATTACH
- symbol_put_addr(state-tuner-ops.tuner_ops.release);
-#endif
- }
kfree(state);
}
@@ -1599,7 +1587,6 @@ struct dvb_frontend *af9005_fe_attach(st
deb_info(attaching frontend af9005\n);
state-d = d;
- state-tuner = NULL;
state-opened = 0;
memcpy(state-frontend.ops, af9005_fe_ops,
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: Luca Olivetti wrote: A month and a half ago Luca Olivetti wrote: En/na Luca Olivetti ha escrit: En/na Trent Piepho ha escrit: But dvb_frontend_detach _does_ have fe-ops.tuner_ops.release(). Now I see it! It's mt2060_attach (or qt1010_attach) that fills tuner_ops. Duh, I missed that one. I'll make a patch tomorrow. Attached. and not applied yet to the master v4l repository :-( Bye Try to send it again, but this time with patch description, and sign-off. Yes, I realized that later. Already done and in the tree. Thank you -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
A month and a half ago Luca Olivetti wrote: En/na Luca Olivetti ha escrit: En/na Trent Piepho ha escrit: But dvb_frontend_detach _does_ have fe-ops.tuner_ops.release(). Now I see it! It's mt2060_attach (or qt1010_attach) that fills tuner_ops. Duh, I missed that one. I'll make a patch tomorrow. Attached. and not applied yet to the master v4l repository :-( Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Now and next info
En/na Peter Maersk-Moller ha escrit: Hi Does anyone have a link to specs on how to decode 'now and next' information available in a DVB stream ? Does anyone know if VDR can do this (yes it is more vdr question) ? Yes, it can (if the broadcaster is transmitting the information). Some (most?) german stations broadcast the epg for a full week, not only the now next. WinTV/Happauge have these popups that shows what is being whatch right now and what is coming next. Is any of the 'now and next' info precise enough to use for cutting clips or is precise with a couple of seconds/minutes ? it depends on the broadcaster. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap
En/na P. van Gaans ha escrit: Talking about that, could anybody tell me the minimal and maximal and/or possible values for status, signal, snr, ber and uncorrected? If I would know them I could try to make the numbers more human-readable (eg signal ranging from 0 to 99 or so). The range and meaning of these values was specified in an older revision of the dvb api. It's no longer specified, besides almost no driver followed the former specification. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Olaf Titz ha escrit: (Btw. once tuned, the actual hardware seems to not care about the tuner module at all, I can stop tzap, lose lock due to disconnected antenna, etc. and the demuxer doesn't stop streaming. Is this intentional, hardware limitation, or what?) I have no idea. I can only say that I have a af9005_fe_sleep function that supposedly turns off the tuner, though I never turn it on again and it still works. I also see from the reference code that there's a power control function that I didn't implement (don't ask me why, I don't remember). I can try to implement it but not today. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Luca Olivetti ha escrit:
En/na Olaf Titz ha escrit:
(Btw. once tuned, the actual hardware seems to not care about the tuner
module at all, I can stop tzap, lose lock due to disconnected antenna,
etc. and the demuxer doesn't stop streaming. Is this intentional,
hardware limitation, or what?)
I have no idea. I can only say that I have a af9005_fe_sleep function
that supposedly turns off the tuner, though I never turn it on again and
it still works.
I also see from the reference code that there's a power control function
that I didn't implement (don't ask me why, I don't remember). I can try
to implement it but not today.
Well, the reference code doesn't work at all: as soon as I write to any
of these register the usb communication stops (bulk timeout), and I
tried one by one. Here's the code for you to play with, disabled with an
#ifdef 0
Bye
--
Luca
diff -r 76b92a337aec linux/drivers/media/dvb/dvb-usb/af9005.c
--- a/linux/drivers/media/dvb/dvb-usb/af9005.c Wed Jun 13 15:11:15 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/af9005.c Fri Jun 15 21:17:34 2007 +0200
@@ -921,7 +921,73 @@ static int af9005_rc_query(struct dvb_us
static int af9005_power_ctrl(struct dvb_usb_device *d, int onoff)
{
-
+#if 0
+ /* as soon as any of these register is written to, either for powering
+ up or down, the sticks stops responding to usb bulk messages */
+ int ret;
+ u8 temp;
+ deb_info(af9005_power_ctrl %d\n, onoff);
+ if (onoff) {
+ /* resume OFSM clock */
+ ret = af9005_write_ofdm_register(d, xd_g_reg_ofsm_clk, 0);
+ if (ret)
+ return ret;
+ /* power on ADC */
+ ret = af9005_write_ofdm_register(d, 0xb200, 0xa1);
+ if (ret)
+ return ret;
+ /* release OFSM reset */
+ ret =
+ af9005_write_register_bits(d, xd_I2C_reg_ofdm_rst,
+ reg_ofdm_rst_pos,
+ reg_ofdm_rst_len, 0);
+ if (ret)
+ return ret;
+ /* disable OFDM reset */
+ ret =
+ af9005_write_register_bits(d, xd_I2C_reg_ofdm_rst_en,
+ reg_ofdm_rst_en_pos,
+ reg_ofdm_rst_en_len, 0);
+ if (ret)
+ return ret;
+
+ } else {
+ /* enable OFDM reset */
+ ret =
+ af9005_write_register_bits(d, xd_I2C_reg_ofdm_rst_en,
+ reg_ofdm_rst_en_pos,
+ reg_ofdm_rst_en_len, 1);
+ if (ret)
+ return ret;
+ /* OFSM reset */
+ ret = af9005_write_ofdm_register(d, 0xaeff, 0);
+ if (ret)
+ return ret;
+ */
+ /* wait for OFSM reset completed */
+ while (1) {
+ ret =
+ af9005_read_register_bits(d, xd_I2C_reg_ofdm_rst,
+ reg_ofdm_rst_pos,
+ reg_ofdm_rst_len, temp);
+ if (ret)
+return ret;
+ if (temp)
+break;
+ msleep(10);
+ }
+ /* power down ADC */
+ ret = af9005_write_ofdm_register(d, 0xb200, 0xa9);
+ if (ret)
+ return ret;
+ /* slow down OFSM clock */
+ printk(slow down ofsm clock);
+ ret = af9005_write_ofdm_register(d, xd_g_reg_ofsm_clk, 7);
+ if (ret)
+ return ret;
+ }
+ deb_info(af9005_power_ctrl ok\n);
+#endif
return 0;
}
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Olaf Titz ha escrit:
This sequence:
modprobe dvb_usb_af9005
sleep 60
modprobe -r dvb_usb_af9005
leaves the following residue:
Module Size Used by
mt2060 5572 4294967295
(the number is unsigned int for -1)
This is probably due to this code in af9005-fe.c:
static void af9005_fe_release(struct dvb_frontend *fe)
{
struct af9005_fe_state *state =
(struct af9005_fe_state *)fe-demodulator_priv;
if (state-tuner != NULL state-tuner-ops.tuner_ops.release
!= NULL) {
state-tuner-ops.tuner_ops.release(state-tuner);
#ifdef CONFIG_DVB_CORE_ATTACH
symbol_put_addr(state-tuner-ops.tuner_ops.release);
#endif
}
kfree(state);
}
specifically the symbol_put_addr, but this is the same thing I saw in
dvb_attach so I don't know why it doesn't work here (in fact I had no
such problem while testing, but some users reported it).
Subsequent re-loading of the modules succeeds but then accessing the
tuner fails, likely due to this error.
it shouldn't matter.
Bye
--
Luca
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: Why dont you just use dvb_frontend_detach? I retract that comment... The dvb-usb framework does this itself inside dvb-usb-dvb.c , inside dvb_usb_adapter_frontend_exit ... You should not have to do the symbol_put inside af9005-fe.c If you remove that code, does it fix the issue? Well, I'm doing the attach myself to attach the tuner to the frontend the first time it is opened, so if I remove the code there will be at least one reference to the mt2060 (or qt1010, depending on the model) so it cannot be unloaded. I couldn't use tuner_attach for some reason (I think it was called too early). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: I see that inside af9005_fe_init, you are reading from the eeprom to determine which tuner is present. Yes, the correct place for this would be inside the tuner_attach callback of af9005_properties ... You say that isn't working for you?? Exactly what happens when you do that? IIRC (that was back in december) I couldn't tune. I don't remember if I could talk to the tuner or not Is it possible that there are some initializations happening inside af9005-fe.c that is opening up access to the i2c bus, which you didnt have access to at the time of tuner_attach? If that's the case, then it can (and should) be fixed by moving the bus initialization code to a function that is callable from tuner_attach. I think I tried to separate what is (supposedly) the i2c initialization in af9005_fe_init somewhere else but it didn't work out. Maybe because I hadn't clear the exact sequence of events in the dvb-usb infrastructure. Perhaps there is an i2c gate being controlled by the demod? If that's the case, then the best way to take care of this is by creating an i2c_gate_ctrl function and add it to the frontend_ops struct, so that tuner_attach can call it from there, and it will be accessible from within the set_params function of the tuner module. I didn't do a full analysis of this driver yet, but these are some ideas that pop into my head at first glance. Alas, I cannot test anything since my stick died. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: :-/ ... Do you plan on getting a replacement? No Perhaps you may contact the vendor so that they may send you a sample at no charge? They should be send me a sample of the 9015 How did your stick die? Maybe the driver broke it? I don't think so, nobody else complained, and there isn't much difference between my driver and the windows one. In fact, looking around in various forums (of windows users), there are many complaints of this stick getting very hot. Anyway, if you feel you should retire the driver, do so, I won't complain. At leas I can consider it as feedback (which was sorely lacking until now). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Trent Piepho ha escrit: On Thu, 14 Jun 2007, Luca Olivetti wrote: En/na Michael Krufky ha escrit: Why dont you just use dvb_frontend_detach? I retract that comment... The dvb-usb framework does this itself inside dvb-usb-dvb.c , inside dvb_usb_adapter_frontend_exit ... You should not have to do the symbol_put inside af9005-fe.c If you remove that code, does it fix the issue? Well, I'm doing the attach myself to attach the tuner to the frontend the first time it is opened, so if I remove the code there will be at least one reference to the mt2060 (or qt1010, depending on the model) so it cannot be unloaded. The tuner gets attached once when you call dvb_attach() from af9005_fe_init. It will get detached once when dvb_frontend_detach() is called. Everything balanced. but dvb_frontent_detach doesnt' know anynthing about the tuner (since it's in the frontend private data), so if I don't do the put_symbol myself in af9005_fe_release (as I do the dvb_attach myself in af9005_fe_init) there will be a dangling reference count, yes? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: The driver will not be removed -- I apologize if my previous email was misinterpreted. I only stated that the driver should stay in the v4l-dvb mercurial master branch and not be pushed upstream until the issues are resolved. Don't worry :-) And I apologize for being so blunt and for not putting retire in quotes, since I did understand what you were saying and I just meant retire from upstream kernel submission. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: Luca Olivetti wrote: En/na Trent Piepho ha escrit: On Thu, 14 Jun 2007, Luca Olivetti wrote: En/na Michael Krufky ha escrit: Why dont you just use dvb_frontend_detach? I retract that comment... The dvb-usb framework does this itself inside dvb-usb-dvb.c , inside dvb_usb_adapter_frontend_exit ... You should not have to do the symbol_put inside af9005-fe.c If you remove that code, does it fix the issue? Well, I'm doing the attach myself to attach the tuner to the frontend the first time it is opened, so if I remove the code there will be at least one reference to the mt2060 (or qt1010, depending on the model) so it cannot be unloaded. The tuner gets attached once when you call dvb_attach() from af9005_fe_init. It will get detached once when dvb_frontend_detach() is called. Everything balanced. but dvb_frontent_detach doesnt' know anynthing about the tuner (since it's in the frontend private data), so if I don't do the put_symbol myself in af9005_fe_release (as I do the dvb_attach myself in af9005_fe_init) there will be a dangling reference count, yes? Bye Luca, You are incorrect -- dvb_frontend_detach has access to the entire struct dvb_frontend *fe , and dvb-core will call fe-ops.tuner_ops.release function itself and dvb_frontend_detach will handle the module detachment. Yes, but my tuner is in fe-demodulator_priv-tuner (probably a bad design, mind me, but that's was the best I could come up with at the time). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na P. van Gaans ha escrit: Luca Olivetti wrote: En/na Michael Krufky ha escrit: The driver will not be removed -- I apologize if my previous email was misinterpreted. I only stated that the driver should stay in the v4l-dvb mercurial master branch and not be pushed upstream until the issues are resolved. Don't worry :-) And I apologize for being so blunt and for not putting retire in quotes, since I did understand what you were saying and I just meant retire from upstream kernel submission. Bye Ok, good :). Still, Luca, you probably understand the driver the best, would you mind looking at the problems some people apparently have if you would get a working AF9005 for free? Obviously I can lend a hand, but there's some really bright people on the list, so I don't think there's a need for me to have an af9005. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Trent Piepho ha escrit: Exactly, the dvb_frontend struct contains the tuner. In fact, the pointer returned by the tuner attach functions is just the dvb_frontend pointer you passed in. The tuner attach functions don't return a new tuner object (there is no dvb_tuner object), they add the tuner functions into the frontend. One could have a frontend with no tuner. In af9005_fe_set_frontend(), you do this: ret = state-tuner-ops.tuner_ops.set_params(state-tuner, fep); What you should do is: ret = fe-ops.tuner_ops.set_params(state-tuner, fep); I don't think you need the state-tuner field really. Just replace all the state-tuner-ops... with fe-ops And change (state-tuner != NULL) to (fe-ops.tuner_ops.release != NULL), or add a one bit flag state-tuner_is_attached and use that. Ok, that could be an idea, but it wouldn't explain why my symbol_put_addr messes up the reference count, while the same exact thing done in dvb_frontend_detach wouldn't. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Michael Krufky ha escrit: Luca Olivetti wrote: En/na Trent Piepho ha escrit: Exactly, the dvb_frontend struct contains the tuner. In fact, the pointer returned by the tuner attach functions is just the dvb_frontend pointer you passed in. The tuner attach functions don't return a new tuner object (there is no dvb_tuner object), they add the tuner functions into the frontend. One could have a frontend with no tuner. In af9005_fe_set_frontend(), you do this: ret = state-tuner-ops.tuner_ops.set_params(state-tuner, fep); What you should do is: ret = fe-ops.tuner_ops.set_params(state-tuner, fep); I don't think you need the state-tuner field really. Just replace all the state-tuner-ops... with fe-ops And change (state-tuner != NULL) to (fe-ops.tuner_ops.release != NULL), or add a one bit flag state-tuner_is_attached and use that. Ok, that could be an idea, but it wouldn't explain why my symbol_put_addr messes up the reference count, while the same exact thing done in dvb_frontend_detach wouldn't. Bye It does explain it -- dvb_frontend_detach is running _and_ your code that calls symbol_put_addr is also running. With both of them occurring, this explains the module ref count being screwed up. dvb_frontend_detach calls fe-ops.release, which is af9005_release, which, before returning, does the symbol_put_addr, at the same time that dvb_frontend_detach would do it if it had a fe-ops.tuner_ops.release, so, frankly, though at the time it cost me a lot of time to untangle the indirections, I don't see the difference. I.e: with fe-ops.tuner_ops.release not null the sequence is: --in dvb_frontend_detach symbol_put_addr(fe-ops.tuner_ops.release); symbol_put_addr(ptr) (where ptr is a copy of fe) while in my code the sequence is --in af9005_release symbol_put_addr(fe-demodulator_priv-tuner_ops.release); --in dvb_frontend_detach symbol_put_addr(ptr) i.e. exactly the same. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Trent Piepho ha escrit: But dvb_frontend_detach _does_ have fe-ops.tuner_ops.release(). Now I see it! It's mt2060_attach (or qt1010_attach) that fills tuner_ops. Duh, I missed that one. I'll make a patch tomorrow. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
En/na Luca Olivetti ha escrit:
En/na Trent Piepho ha escrit:
But dvb_frontend_detach _does_ have fe-ops.tuner_ops.release().
Now I see it! It's mt2060_attach (or qt1010_attach) that fills
tuner_ops. Duh, I missed that one. I'll make a patch tomorrow.
Attached.
I can test it up to the point where it correctly attaches the mt2060,
but then I don't know if it tunes correctly since my stick doesn't work
(though it should, since it does the same as before, only without the
extra tuner pointer). Olaf, could you give it a try?
I also tried (again) to unload and reload the module and, while at first
it seems to recognize and initialize, after a (short) while it gives
bulk transfer errors, so in case the module is unloaded the stick must
be reconnected.
Maybe the usb_clear_halt in af9005.c should be somewhere else, at the
time it seemed to work where it is (I had to duplicate what dvb-usb-init
does since the standard dvb-usb uses a single endpoint for bulk
transfers, while the af9005 uses one for writing and another one for
reading).
Bye
--
Luca
diff -r 76b92a337aec linux/drivers/media/dvb/dvb-usb/af9005-fe.c
--- a/linux/drivers/media/dvb/dvb-usb/af9005-fe.c Wed Jun 13 15:11:15 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/af9005-fe.c Fri Jun 15 01:26:16 2007 +0200
@@ -29,8 +29,6 @@
struct af9005_fe_state {
struct dvb_usb_device *d;
- struct dvb_frontend *tuner;
-
fe_status_t stat;
/* retraining parameters */
@@ -454,7 +452,7 @@ static int af9005_fe_read_status(struct
#endif
int ret;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
*stat = 0;
@@ -512,7 +510,7 @@ static int af9005_fe_read_ber(struct dvb
static int af9005_fe_read_ber(struct dvb_frontend *fe, u32 * ber)
{
struct af9005_fe_state *state = fe-demodulator_priv;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
af9005_fe_refresh_state(fe);
*ber = state-ber;
@@ -522,7 +520,7 @@ static int af9005_fe_read_unc_blocks(str
static int af9005_fe_read_unc_blocks(struct dvb_frontend *fe, u32 * unc)
{
struct af9005_fe_state *state = fe-demodulator_priv;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
af9005_fe_refresh_state(fe);
*unc = state-unc;
@@ -536,7 +534,7 @@ static int af9005_fe_read_signal_strengt
int ret;
u8 if_gain, rf_gain;
- if (state-tuner == NULL)
+ if (fe-ops.tuner_ops.release == NULL)
return -ENODEV;
ret =
af9005_read_ofdm_register(state-d, xd_r_reg_aagc_rf_gain,
@@ -827,11 +825,11 @@ static int af9005_fe_power(struct dvb_fr
#if 0
if (ret)
return ret;
- if (state-tuner != NULL) {
+ if (fe-ops.tuner_ops.init != NULL) {
if (on)
- ret = state-tuner-ops.tuner_ops.init(state-tuner);
+ ret = fe-ops.tuner_ops.init(fe);
else
- ret = state-tuner-ops.tuner_ops.sleep(state-tuner);
+ ret = fe-ops.tuner_ops.sleep(fe);
}
#endif
return ret;
@@ -1135,7 +1133,7 @@ static int af9005_fe_init(struct dvb_fro
return ret;
#endif
/* attach tuner and init */
- if (state-tuner == NULL) {
+ if (fe-ops.tuner_ops.release == NULL) {
/* read tuner and board id from eeprom */
ret = af9005_read_eeprom(adap-dev, 0xc6, buf, 2);
if (ret) {
@@ -1152,20 +1150,16 @@ static int af9005_fe_init(struct dvb_fro
return ret;
}
if1 = (u16) (buf[0] 8) + buf[1];
- state-tuner =
- dvb_attach(mt2060_attach, fe, adap-dev-i2c_adap,
- af9005_mt2060_config, if1);
- if (state-tuner == NULL) {
+ if (dvb_attach(mt2060_attach, fe, adap-dev-i2c_adap,
+ af9005_mt2060_config, if1) == NULL) {
deb_info(MT2060 attach failed\n);
return -ENODEV;
}
break;
case 3: /* QT1010 */
case 9: /* QT1010B */
- state-tuner =
- dvb_attach(qt1010_attach, fe, adap-dev-i2c_adap,
- af9005_qt1010_config);
- if (state-tuner == NULL) {
+ if (dvb_attach(qt1010_attach, fe, adap-dev-i2c_adap,
+ af9005_qt1010_config) ==NULL) {
deb_info(QT1010 attach failed\n);
return -ENODEV;
}
@@ -1174,7 +1168,7 @@ static int af9005_fe_init(struct dvb_fro
err(Unsupported tuner type %d, buf[0]);
return -ENODEV;
}
- ret = state-tuner-ops.tuner_ops.init(state-tuner);
+ ret = fe-ops.tuner_ops.init(fe);
if (ret)
return ret;
}
@@ -1212,7 +1206,7 @@ static int af9005_fe_set_frontend(struct
deb_info(af9005_fe_set_frontend freq %d bw %d\n, fep-frequency,
fep-u.ofdm.bandwidth);
- if (state-tuner == NULL) {
+ if (fe-ops.tuner_ops.release == NULL) {
err(Tuner not attached);
return -ENODEV;
}
@@ -1300,7 +1294,7 @@ static int af9005_fe_set_frontend(struct
#endif
/* set tuner */
deb_info(set tuner\n);
- ret = state-tuner-ops.tuner_ops.set_params(state-tuner, fep);
+ ret = fe-ops.tuner_ops.set_params(fe, fep);
if (ret)
return ret;
@@ -1576,12 +1570,6 @@ static void af9005_fe_release(struct dvb
{
struct af9005_fe_state *state =
(struct af9005_fe_state *)fe-demodulator_priv;
- if (state
Re: [linux-dvb] V-Gear MobiDTV Pro
En/na John Pilkington ha escrit: The packaging says: Tuner: Microtune tuner USB IC: Afa (9015 chip) Demodulator: Afa COFDM The driver for this chip is under development (not by me). Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvb-apps questions
En/na Paul ha escrit: Q 2. DVB_Frontend_API document output is in what units (eg Db , % or someother value) eg Frontend Function Calls FE_READ_BER what units are these Currend dvb api specification doesn't say anything. An older version of the specification (http://linuxtv.org/downloads/old/linux_dvb_api-20020304.pdf) says that the value should be a multiple of 10E-9, so that 2500 means 2.5*10E-6 or 1 error in 40 bits. I don't think that many drivers do the scaling, they just report whatever the card tells them. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Af9005 driver: remote control not initialised on driver load
En/na Stanislav Nikolov ha escrit:
Hello,
I think there is a small problem in the af9005 driver implementation. When the
driver is initialised, it is registered with the fields for the remote
control empty. This doesn't allow for the remote control driver to be
initialised. So, in order to use the remote, one has to manually remove and
reinsert the stick, then the remote control works. It also doesn't work if
one boots the system with the usb stick in.
That's strange, since the remote decoding functions are loaded with
symbol_request in module_init, so what you're seeing shouldn't happen.
I think a kernel guru could tell me if the initialization is wrong and
suggest how to correct it in that case:
static int __init af9005_usb_module_init(void)
{
int result;
if ((result = usb_register(af9005_usb_driver))) {
err(usb_register failed. (%d), result);
return result;
}
rc_decode = symbol_request(af9005_rc_decode);
rc_keys = symbol_request(af9005_rc_keys);
rc_keys_size = symbol_request(af9005_rc_keys_size);
if (rc_decode == NULL || rc_keys == NULL || rc_keys_size == NULL) {
err(af9005_rc_decode function not found, disabling
remote);
af9005_properties.rc_query = NULL;
} else {
af9005_properties.rc_key_map = rc_keys;
af9005_properties.rc_key_map_size = *rc_keys_size;
}
return 0;
}
Bye
--
Luca
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech AF9015 - Some progress?
En/na Juan ha escrit: I Andrew, all, No news from other list members about this device. Please, can you send me your progress and related doc? I want to try to do something. Hopefully I should receive one of those devices soon, so I can offer my help, and I know that someone else is working on it too. This is just a heads-up since I'm terribly lazy, so I cannot stand to see useless duplication of work ;-) Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
En/na Mauro Carvalho Chehab ha escrit:
Hi Luca,
Em Sex, 2007-05-04 às 00:16 +0200, Luca Olivetti escreveu:
En/na Luca Olivetti ha escrit:
Ok, done. I also added a dependency on qt1010 in Kconfig (forgot to do
it when I added qt1010 support) and corrected the experimental gain
reduction of the mt2060 in case of strong signal (though it is code
included in #ifdef 0) - a patch that I send on the mailing list.
Due to the size I compressed the patch, I hope it is ok.
And I forgot to exclude dvb-usb-ids.h.orig, so it was in the patch,
please remove it or tell me if I shuld re-send the patch without it.
To avoid losing Manu's SOB at the first patch you've sent, I'm applying
the patches from Manu's tree, then the diff between his tree and the
patch you've sent. I need, however, your SOB. The diff between Manu's
patch and the one you've sent is enclosed.
Could you sign it?
Sure
Signed-off-by: Luca Olivetti [EMAIL PROTECTED]
Bye
--
Luca
diff -r 50c77dd2bcf8 linux/drivers/media/dvb/dvb-usb/Kconfig
--- a/linux/drivers/media/dvb/dvb-usb/Kconfig Mon May 07 15:19:32 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/Kconfig Mon May 07 15:35:57 2007 -0300
@@ -221,8 +221,9 @@ config DVB_USB_OPERA1
config DVB_USB_AF9005
tristate Afatech AF9005 DVB-T USB1.1 support
- depends on DVB_USB
- select DVB_TUNER_MT2060 if !DVB_FE_CUSTOMISE
+ depends on DVB_USB EXPERIMENTAL
+ select DVB_TUNER_MT2060 if !DVB_FE_CUSTOMISE
+ select DVB_TUNER_QT1010 if !DVB_FE_CUSTOMISE
help
Say Y here to support the Afatech AF9005 based DVB-T USB1.1 receiver
and the TerraTec Cinergy T USB XE (Rev.1)
@@ -231,5 +232,6 @@ config DVB_USB_AF9005_REMOTE
tristate Afatech AF9005 default remote control support
depends on DVB_USB_AF9005
help
- Say Y here to support the default remote control decoding for the
+ Say Y here to support the default remote control decoding for the
Afatech AF9005 based receiver.
+
diff -r 50c77dd2bcf8 linux/drivers/media/dvb/dvb-usb/af9005-fe.c
--- a/linux/drivers/media/dvb/dvb-usb/af9005-fe.c Mon May 07 15:19:32 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/af9005-fe.c Mon May 07 15:35:57 2007 -0300
@@ -403,8 +403,8 @@ static int af9005_get_statistic(struct d
if (ret == 0) {
af9005_reset_pre_viterbi(fe);
if (state-pre_vit_bit_count 0) {
- /* according to v 0.0.4 of the dvb api ber should be a multiple
- of 10E-9 so we have to multiply the error count by
+ /* according to v 0.0.4 of the dvb api ber should be a multiple
+ of 10E-9 so we have to multiply the error count by
10E9=10 */
numerator =
(u64) state-pre_vit_error_count * (u64) 10;
@@ -495,7 +495,7 @@ static int af9005_fe_read_status(struct
#if 0
/* adjust mt2060 for strong signal (test) */
buf[0] = 0x0b;
- if (strong) {
+ if (temp) {
buf[1] = 0x30;
} else {
buf[1] = 0x33;
@@ -878,7 +878,7 @@ static int af9005_fe_init(struct dvb_fro
if (i == 150)
return -ETIMEDOUT;
- /*FIXME in the dump
+ /*FIXME in the dump
write B200 A9
write xd_g_reg_ofsm_clk 7
read eepr c6 (2)
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
En/na Luca Olivetti ha escrit: En/na Luca Olivetti ha escrit: Ok, done. I also added a dependency on qt1010 in Kconfig (forgot to do it when I added qt1010 support) and corrected the experimental gain reduction of the mt2060 in case of strong signal (though it is code included in #ifdef 0) - a patch that I send on the mailing list. Due to the size I compressed the patch, I hope it is ok. And I forgot to exclude dvb-usb-ids.h.orig, so it was in the patch, please remove it or tell me if I shuld re-send the patch without it. No feedback on this or the patch? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
En/na Mauro Carvalho Chehab ha escrit: Hi Luca, Em Dom, 2007-05-06 às 17:18 +0200, Luca Olivetti escreveu: En/na Luca Olivetti ha escrit: En/na Luca Olivetti ha escrit: Ok, done. I also added a dependency on qt1010 in Kconfig (forgot to do it when I added qt1010 support) and corrected the experimental gain reduction of the mt2060 in case of strong signal (though it is code included in #ifdef 0) - a patch that I send on the mailing list. Due to the size I compressed the patch, I hope it is ok. And I forgot to exclude dvb-usb-ids.h.orig, so it was in the patch, please remove it or tell me if I shuld re-send the patch without it. No feedback on this or the patch? I intend to give you some feedback as soon as possible, maybe later today. I'm busy with some stuff here right now. One trouble I've already noticed is that some hexa values are on uppercase. It is weird that indent haven't converted those to lowercase. I was supposing that it would solve. I just looked at the info page of indent and I cannot see no option that would convert hex values to lowercase, certainly none of the options in Lindent does. I suppose I could fix it with a simple script, however I cannot find the section in CodingStyle that says that hexadecimal values must be lowercase. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] innacle PCTV USB hybrid stick - error: 'struct net_device' has no member named 'xmit_lock']
french 44 escribió: Hi, My configuration : Mandriva 2007.1 (spring) with the kernel : 2.6.17-13mdv - Pinnacle PCTV USB hybrid stick. I have some problems to do the compilation of the driver for this product. [...] /usr/src/v4l-dvb-kernel/v4l/dvb_net.c: In function 'wq_set_multicast_list': /usr/src/v4l-dvb-kernel/v4l/dvb_net.c:1141: error: 'struct net_device' has no member named 'xmit_lock' /usr/src/v4l-dvb-kernel/v4l/dvb_net.c:1170: error: 'struct net_device' has no member named 'xmit_lock' Mandriva kernel is more a cross between 2.6.17 and 2.6.18 than a pure 2.6.17. If you don't need dvb-net functionality for your device you can just comment out those lines, or try to change the surrounding conditional to look for version 2,6,18 instead of 2,6,17. Bye -- - Yo también quiero una Europa libre de Patentes de Software - - I want a Software Patents Free Europe too! And you? - --- EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
En/na Mauro Carvalho Chehab ha escrit: Em Qui, 2007-05-03 às 13:55 +0200, Markus Rechberger escreveu: Is there anything against it? Markus On 5/1/07, P. van Gaans [EMAIL PROTECTED] wrote: I managed to screw up my message for a second time so I'll just write a whole new message. Would it be possible to push the AF9005 drvier from /hg/~manu/af9005 to the main repo? I'm not sure Luca's line in his reply to me will get noticed so I thought this deserved a whole new message. For me, it is ok, providing that Luca or Manu send us a pull request. Is this a special mail or something, or can this message considered as a pull request? ;-) I've did a really quick look at his patch. There are some CodingStyle issues that should be fixed, like hexadecimal values using uppercase. At the pull request, I'll take a closer look at the patch, before adding my SOB. Most CodingStyle issues can easily by running a really small script, available at scripts/Lindent at the kernel tree. The script content is: #!/bin/sh indent -npro -kr -i8 -ts8 -sob -l80 -ss -ncs $@ I ran Lindent before submitting the patch to Manu !?!? (of course, you need to have the indent package installed at the local machine) It is interesting also to mark newer drivers as EXPERIMENTAL for one or two kernel releases. If AF9005 is intended to be added on kernel 2.6.22, this should be done ASAP, since the merge window is closing. Otherwise, if the driver is not stable enough, the better is to wait to the end of the window, then add it to the tree. I prefer the last option. Well, I've been using my driver since december and I didn't suffer any crash or problems. I had reports of funky usage number in lsmod, but I think that's because of my use of symbol_request/symbol_put (though it doesn't happen on my machine): I separated the remote decoding functions in a standalone module, so I can substitute the implementation (in fact I have a different one on my page that interfaces with lirc). Other users have been using it with no problems (or at least with no more problems than under windows, as P. van Gaans can testify ;-) Anyway, do as you like, but if it's more visible someone more capable than me can correct more bugs ;-) Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
En/na Mauro Carvalho Chehab ha escrit: Most CodingStyle issues can easily by running a really small script, available at scripts/Lindent at the kernel tree. The script content is: #!/bin/sh indent -npro -kr -i8 -ts8 -sob -l80 -ss -ncs $@ I ran Lindent before submitting the patch to Manu !?!? I don't think so. I saw some hexadecimal values on uppercase. Also some idents were wrong. Could you review it please, and then, send me the newest version c/c ML? re-ran Lindent and it produced the same files (at least according to diff) Please, also mark the driver as EXPERIMENTAL, since this will be the first release. Hopefully, we can remove the tags at the next kernel. Ok, done. I also added a dependency on qt1010 in Kconfig (forgot to do it when I added qt1010 support) and corrected the experimental gain reduction of the mt2060 in case of strong signal (though it is code included in #ifdef 0) - a patch that I send on the mailing list. Due to the size I compressed the patch, I hope it is ok. Bye -- Luca af9005-take2.diff.bz2 Description: application/bzip ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
En/na Luca Olivetti ha escrit: Ok, done. I also added a dependency on qt1010 in Kconfig (forgot to do it when I added qt1010 support) and corrected the experimental gain reduction of the mt2060 in case of strong signal (though it is code included in #ifdef 0) - a patch that I send on the mailing list. Due to the size I compressed the patch, I hope it is ok. And I forgot to exclude dvb-usb-ids.h.orig, so it was in the patch, please remove it or tell me if I shuld re-send the patch without it. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AF9005 not installable anymore?
En/na P. van Gaans ha escrit: It seems the driver from /hg/~manu/af9005 can't be used on a recent v4l-dvb version? Possibly I'm just messing up or I should use another directory or something, but I could imagine that code that wasn't changed for 2 weeks gets incompatible. Any help? A new device has been added in the meantime, so the patch doesn't apply cleanly anymore. You have to hand edit linux/drivers/media/dvb/dvb-usb/Kconfig adding the missing lines at the end: config DVB_USB_AF9005 tristate Afatech AF9005 DVB-T USB1.1 support depends on DVB_USB select DVB_TUNER_MT2060 if !DVB_FE_CUSTOMISE help Say Y here to support the Afatech AF9005 based DVB-T USB1.1 receiver and the TerraTec Cinergy T USB XE (Rev.1) config DVB_USB_AF9005_REMOTE tristate Afatech AF9005 default remote control support depends on DVB_USB_AF9005 help Say Y here to support the default remote control decoding for the Afatech AF9005 based receiver. Or just use the complete /hg/~manu/af9005 tree. Would it be possible to push the driver to the main repository? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Asus P7131 Analog
Hello, I have an Asus P7131 Analog (not the Hybrid/Dual one), with subsys id 1043:4845, which seems to be detected as a TV-FM 7135 (as stated in http://www.spinics.net/lists/vfl/msg31515.html ). My question is if I can somehow get the Composite and/or S-video inputs working (even at the expense of breaking the original TV-FM 7135 support). Thanks, Bogdan Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
En/na P. van Gaans ha escrit: Sorry, that doesn't seem to help, I don't see any difference at all. It doesn't seem to hurt either. Not that I was really expecting it to help (after all it cannot report an mpeg sync without a tps lock, or can it?), but it was the only thing I could think of driver side. Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
En/na P. van Gaans ha escrit: Luca Olivetti wrote: En/na P. van Gaans ha escrit: Sorry, that doesn't seem to help, I don't see any difference at all. It doesn't seem to hurt either. Not that I was really expecting it to help (after all it cannot report an mpeg sync without a tps lock, or can it?), but it was the only thing I could think of driver side. Bye Sorry Luca, but my e-mail client automatically starts at the top of the message (Thunderbird) oh, they must have changed the default recently (though I just created a test account and it defaulted to repky at bottom). , in any e-mail conversation with companies I companies don't get the internet and don't get email (otherwise they won't be using any microsoft software connecting to the internet at large). Anyway it has nothing to do with dvb. receive top-posted replies (and they expect me to top-post back or else I risk not getting a response) and trust me it's really hard to remember to do a different posting style just for one person. I'm trying but it's so easy to forget. If bottom-posting were the standard I would use it by default but it simply isn't, at least not in e-mail. It's not intentional, I don't mean to annoy you but how can I remember? Simple, read the message you're composing from top to bottom and see if it makes sense. If you're top-posting it surely won't. Companies don't usually make sense either, that's because they don't mind top posting, or actually require it ;-) I gave scan a go and scan is a lot faster than Kaffeine. And good thing, more frequencies allow to be scanned, but still not all. with or without the suggested modification? On the ones that don't work I get (tuning failed). But if the driver wouldn't be the problem I couldn't explain why the MSI scans (also in Kaffeine) without problems. So scan works better.. I'm not far enough into the technical stuff to explain this. As I said earlier (and if I didn't I'm telling it now ;-)) I'm not a dvb expert, but the driver is trying to report what the stick is telling, so if the stick is reporting a lock when there isn't one I cannot do much. Of course I could have misinterpreted the data sheet or didn't match exactly what it's reporting to the linux dvb infrastructure. The af9005 provides 3 bits: - agc lock that I mapped to FE_HAS_SIGNAL - tps lock that I mapped to FE_HAS_CARRIER - mpeg 2 lock signal that I mapped to FE_HAS_LOCK, FE_HAS_SYNC, FE_HAS_VITERBI scan only looks at FE_HAS_LOCK, and that correspond to mpeg 2 lock signal. With the modification I suggested I made it dependent also on tps lock. I think the driver cannot do much more (besides filtering the signal, waiting for it to be stable for, e.g. 200ms, but I'm not sure that's the correct thing to do) There are also various bits that I ignored: fractional frequency offset estimator lock, integer frequency offset estimator lock and sampling clock offset lock. What I'm asking now is if I got the mapping right, if not what should be the correct one. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
En/na P. van Gaans ha escrit: So the bug is: you can't scan for channels with the stick. Well, hardly ever. On some specific frequency I do get results with the Afatech while scanning, but that's just one frequency filled with mostly (worthless) encrypted channels. With the MSI this is no problem, and if I use the channellist from the MSI on the Afatech it also works as expected. Only scanning with the Afatech itself somehow won't work properly. My Kaffeine version btw is 0.7.1 (will upgrade soon, Ubuntu 6.06), but I feel it shouldn't really matter that much, but to be complete. Maybe (just maybe) the afatech is slower/too slow to lock on a channel so kaffeine will time-out? Did you try with plain old scan and/or raising the timeut (if possible)? I don't remember how I got my channel list, but I think I primed it with scan then vdr did the rest. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
En/na P. van Gaans ha escrit: For my feeling speed isn't the problem, but where do I increase the timeout? I just saw that there isn't one in the scan utility, and probably this isn't the (only) problem: I report FE_HAS_LOCK when the af9005 says that it has seen the mpeg sync byte, while I use the tpsd_lock to indicate FE_HAS_CARRIER. Probably FE_HAS_LOCK should depend on both conditions. Try, as a test, in af9005-fe.c, function af9005_fe_read_status, where you see if (temp) *stat |= FE_HAS_SYNC | FE_HAS_VITERBI | FE_HAS_LOCK; change the condition to if (temp (*stat FE_HAS_CARRIER)) and tell me if you can scan this way. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Why is it called BER?
En/na Morgan Tørvolt ha escrit: My advice would be to change the current FE_READ_BER to FE_READ_BEC (Bit Error Counter), and try to phase out the current definition by making it obsolete. Or fix the driver(s) to return what the api specifies? Btw, an older version of the api specified that it had to be a multiple of 10E-9. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
En/na P. van Gaans ha escrit: What, top-posting? Wikipedia is helpful.. I didn't know, I prefer top-posting, saves scrollingtime. In fact I was wondering why you were bottom-posting. I'm used to forums, not to mailinglists. On forums you decide yourself if you want to see everything top or bottomposted.. Seriously I didn't know it was a crime! See sig. This is a mailing list, not a forum So I understand I have to change the 0 into a 1 and change state-strong to temp? Not remove the # for if? If that's all correct I guess it didn't really help. If you're following the mailing list, see Thomas Pinz's reply to my message. Maybe you just get what you pay for then.. On other receivers I get signals from 60 kilometers away, on the afatach vitually nothing (closest transmitter is 27 kilometer). Are you supposed to tape the antenna to the transmitter? I live ~6km to the transmitting tower, and I cannot get at least one mux (the rest are mostly fine though). But, in my case, it's the same under windows. But wait.. *looks at laptop*, suddenly the afatech stick reads the channels from Wavre, Belgium. That's over 80 kilometers away and a pretty weak transmitter. The much stronger signal from Schoten (35 kilometers or so) is blissfully ignored. The image contains some blocks but it's better than the radio I had earlier. Strange stuff.. Indeed Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
En/na Thomas Pinz - DC2RPT ha escrit: Hi Luca, On Monday 16 April 2007 08:57, Luca Olivetti wrote: I live ~6km to the transmitting tower, and I cannot get at least one mux (the rest are mostly fine though). But, in my case, it's the same under windows. On which channels are muxes (also the belgian one) ? An which of them don't you get ? Look at the es-Collserola file. I don't get c26 and c33, but I think that's normal, since those are local tv directed at Barcelona and I'm at the opposite side (though I could get a glimpse once of c26). c61 is the best of all, the others are so-so and the problematic one is c64. Maybe you can also find out the transmission power of the muxes. Here for example they are not equal. According to some forums neither are here, and it seems they screwed many times with that mux. However I still think I should receive it fine. Probably they'll increase the power, or I'll have to raise the antenna (I have a building blocking direct line of sight to the tower) Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
En/na P. van Gaans ha escrit: My last question for a cheap USB DVB-T stick took a whole other turn. Earlier I bought an Allnet all2006 USB DVB-T stick, just praying it would run on Linux. It didn't. At least it didn't back then. On Windows I figured out it's an Afatech AF9005 clone. On Google I figured out there is a driver and firmware here, recently written: http://ventoso.org/luca/af9005/ Happy was I! I installed everything and yes, the device is detected. But it hardly ever locks correctly on a frequency. I see the lock thingie in Kaffeine light up, as well as a blue led on the stick. But few times do I read some channel information. Once I was able to read the radio transponder, but the radio stutters. That doesn't really say much, radio stutters with another DVB-T device on Windows as well at that frequency, and I have no idea if my reception or buggy software is the problem here. The main problem is I can't read all channels. I'm missing almost all the channels. The -/+167 trick didn't help. Well, I found that reception with this stick isn't very good, but since it does the same under windows (actually under Linux I can catch more channels) I thought it was just a problem with the hardware. OTOH I have other users reporting that the stick works just fine for them. Maybe it depends on the tuner used (I have an mt2060, others have a qt1010) or on the overall quality of the stick (there are various no name ones using this chipset and the terratec cinergy xe). If you have a stick with an mt2060, there's a commented out section of code that tries to reduce the gain of the mt2060 if the demodulator detects a strong signal. I tried it talking directly on the i2c bus with the mt2060, since the mt2060 code doesn't provide such an option (maybe one of the tuner ops should provide for gain adjustment?), but since I saw it didn't make a difference here (and I live pretty close to the transmitting tower) I just commented it out. You can however look in the logs (enabling at least debug=1) for messages adjust for strong signal 1. If you see them you can try to uncomment the code in af9005-fe.c (look for the comments adjust mt2060 for strong signal (test)). Bye -- Luca ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
En/na P. van Gaans ha escrit:
[please, keep this on list, and avoid top posting, I hate it and I was
tempted to ignore your message ]
Thanks, I tried but I get a load of compilation errors. I don't know if
I have a mt2060.
Look in the syslog, you should see an MT2060: successfully identified
or if you have a qt1010 Quantek QT1010 successfully identified..
I don't really know what I'm doing wrong, I tried
Oop, there's an error there. In the second block between #if 0...#endif
there's a if (strong) { line, change that to if (state-strong) {
debugging it but my little PHP knowledge is not enough to debug C code.
I just uncommented everything that said something about the strong
signal, maybe I uncommented too much?
there are just two sections of code in function af9005_fe_read_status
enclosed in #if 0 just change that to #if 1.
To the rest of the list, maybe there should be a standardized way to
adjust tuner gain in dvb_tuner_ops or is the mt2060 the only tuner with
adjustable gain (even if in its current incarnation mt2060.c doesn't do it)?
Bye
--
Luca
___
linux-dvb mailing list
[EMAIL PROTECTED]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
En/na Luca Olivetti ha escrit:
En/na P. van Gaans ha escrit:
[please, keep this on list, and avoid top posting, I hate it and I was
tempted to ignore your message ]
Thanks, I tried but I get a load of compilation errors. I don't know
if I have a mt2060.
Look in the syslog, you should see an MT2060: successfully identified
or if you have a qt1010 Quantek QT1010 successfully identified..
I don't really know what I'm doing wrong, I tried
Oop, there's an error there. In the second block between #if 0...#endif
there's a if (strong) { line, change that to if (state-strong) {
Ooops (again) that should be if (temp) {
Bye
--
Luca
___
linux-dvb mailing list
[EMAIL PROTECTED]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [patch] fix experimental mt2060 gain adjustment for the af9005
This patch should be applied to the repository
http://linuxtv.org/hg/~manu/af9005
It is code normally not compiled, so no big harm, but it would be nice
to fix it anyway.
Signed-off-by: Luca Olivetti [EMAIL PROTECTED]
Bye
--
Luca
diff --unified --recursive --exclude=v4l v4l-dvb-a80058519add.orig/linux/drivers/media/dvb/dvb-usb/af9005-fe.c v4l-dvb-a80058519add/linux/drivers/media/dvb/dvb-usb/af9005-fe.c
--- v4l-dvb-a80058519add.orig/linux/drivers/media/dvb/dvb-usb/af9005-fe.c 2007-03-02 21:24:51.0 +0100
+++ v4l-dvb-a80058519add/linux/drivers/media/dvb/dvb-usb/af9005-fe.c 2007-04-14 16:17:05.459194000 +0200
@@ -495,7 +495,7 @@
#if 0
/* adjust mt2060 for strong signal (test) */
buf[0] = 0x0b;
- if (strong) {
+ if (temp) {
buf[1] = 0x30;
} else {
buf[1] = 0x33;
___
linux-dvb mailing list
[EMAIL PROTECTED]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] fix experimental mt2060 gain adjustment for the af9005
En/na Thomas Pinz - DC2RPT ha escrit: Hi, On Saturday 14 April 2007 16:22, Luca Olivetti wrote: This patch should be applied to the repository http://linuxtv.org/hg/~manu/af9005 It is code normally not compiled, so no big harm, but it would be nice to fix it anyway. You can always leave the register 0x0b to 0x33 (highest amplification), you will not have any problems with strong signals. That's how it works now (that code is enclosed in if #0 and the mt2060 code initializes it at 0x33) (If you see an improvement, please tell me exact product, then there would be an other problem) No, I tried it but I never see a strong signal (as reported by the af9005), so in my case either with that code enabled there's no difference. I tried it because that's what the sample code that afatech provided me does. Bye -- Luca ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Unbranded USB DVB device afatech af9005
En/na Luca Olivetti ha escrit: Ok, I have what I think is a working driver (I have bad reception quality but that's even worse under windows), now what should I do? 3 months have passed and the driver is still sitting on my server, bit-rotting. I repeat my question: what should I do? Post a (big) patch to the list? Forget about it? Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Unbranded USB DVB device afatech af9005
En/na Nick Andrew ha escrit: On Tue, Apr 10, 2007 at 09:16:17AM +0200, Luca Olivetti wrote: En/na Luca Olivetti ha escrit: Ok, I have what I think is a working driver (I have bad reception quality but that's even worse under windows), now what should I do? 3 months have passed and the driver is still sitting on my server, bit-rotting. I repeat my question: what should I do? Post a (big) patch to the list? Forget about it? Please post the patch! Already sent, privately, to Manu. It's also available here http://ventoso.org/luca/af9005/af9005.diff.bz2 Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problems on scanning Hotbird
Hi. I'm testing an Hauppauge WinTV Nova CI DVB-s card on Knoppix with kernel 2.6.19. When I try to scan the Hotbird satellites, the scan utility doesn't found all channels. The scanning process takes about only 10 seconds and then stops without errors. The scan /usr/share/doc/dvb-utils/examples/scan/dvb-s/Hotbird-13.0E channels.conf output ends with: 0x 0x231b: pmt_pid 0x046a Tadiran Scopus -- MEDIOLANUM (running) 0x 0x22b0: pmt_pid 0x140c EUTELSAT -- DIRECT 8 (running) 0x 0x22af: pmt_pid 0x1405 NTH -- VIKOM RADIO (running) 0x 0x22ae: pmt_pid 0x1404 EUTELSAT -- TV8 Mt Blanc (running) 0x 0x22ad: pmt_pid 0x1403 EUTELSAT -- DIRECT 8 (running) Network Name 'EUTELSAT 13EAST' tune to: 10853:h:0:27500 0x2db4 0x219c: pmt_pid 0x007c T-Systems -- Supreme Master TV (running) 0x2db4 0x21ac: pmt_pid 0x008c T-Systems -- eurotic TV (running) 0x2db4 0x21ad: pmt_pid 0x0096 T-Systems -- INXTC TV (running) 0x2db4 0x21ae: pmt_pid 0x00a0 T-Systems -- eUroticPlus TV (running) 0x2db4 0x21af: pmt_pid 0x00aa T-Systems -- eurotic TV 2 (running) 0x2db4 0x21b0: pmt_pid 0x00ab T-Systems -- Sexy-Arab.TV (running) 0x2db4 0x21b1: pmt_pid 0x00ac T-Systems -- e-sat.tv (running) 0x2db4 0x21b2: pmt_pid 0x00ad T-Systems -- xxxFun TV (running) 0x2db4 0x21b3: pmt_pid 0x00ae T-Systems -- ArabSexClub (running) 0x2db4 0x21b4: pmt_pid 0x00af T-Systems -- ALO TV (running) 0x2db4 0x21b5: pmt_pid 0x00b0 T-Systems -- 'Arab-Girls.TV (running) 0x2db4 0x21cd: pmt_pid 0x0079 T-Systems -- EUMETCAST (running) 0x2db4 0x21ce: pmt_pid 0x007e T-Systems -- BTV IP (running) 0x2db4 0x21d0: pmt_pid 0x0080 T-Systems -- Tenfore (running) 0x2db4 0x21d2: pmt_pid 0x00b5 T-Systems -- InfomedTV (running) Network Name 'T-Systems' dumping lists (45 services) Done. I'm attaching my complete channels.conf, which is only 46 rows long (it should be very very longer!). In fact, the scanning process doesn't work even with Kaffeine or MythTV, and if I try to manually tune some transponders no channels are found. Using the original Hauppauge's drivers on Windows XP with the same cable and the same card I don't get any problem, and I can tune all channels on Hotbird satellite, so I don't think it is a cable or card related problem. My dish antenna is pointed only to Hotbird, so I can't try with another satellites. Anyone could help me to solve this problem? Thank you very much! Luca. _ Hotmail 1 GB: ancora più spazio per i tuoi messaggi e foto! GRATIS! http://specials.it.msn.com/hotmail.aspx channels.conf Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech
En/na Nick Bruton ha escrit: Hi, This usb stick was working until I just crashed my system and rebooted, now the damn thing isn't starting if I uplug and replug the stick I get .. sb 3-1: USB disconnect, address 3 usb 3-1: new full speed USB device using uhci_hcd and address 4 usb 3-1: new device found, idVendor=15a4, idProduct=9020 usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: DVBT usb 3-1: Manufacturer: Afatech usb 3-1: configuration #1 chosen from 1 choice but kaffeine does not see it, can someone help me please I don't see any message from the af9005 modules, are they loaded (either manually or automatically)? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TechniSat SkyStar HD
Hello, So, the picture is at http://www.synco.ro/pics/skystar_hd.jpg (sorry for the flash), and under the tin can (which i de-soldered after taking the picture) there is indeed a STB6100. Bogdan Manu Abraham wrote: On 3/19/07, Bogdan Luca [EMAIL PROTECTED] wrote: ATTN DVB Developers Hello, I 'desperately' need support (preferably including CI) for the TechniSat SkyStar HD card, using SAA7146 + STB0899 chips. I own one of these cards (and a CI module coming soon), and I'm willing to help with anything I can. Is it having a tin can tuner based on the TDA8261 , or is it based on the STB6100 ? Manu !DSPAM:9,46003e7998941295492554! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] TechniSat SkyStar HD
ATTN DVB Developers Hello, I 'desperately' need support (preferably including CI) for the TechniSat SkyStar HD card, using SAA7146 + STB0899 chips. I own one of these cards (and a CI module coming soon), and I'm willing to help with anything I can. I have tried the current mercurial repository with the patches from http://kromtek.com/dvb/patches/ and http://linuxtv.org/pipermail/linux-dvb/2007-February/016165.html , but all I've got is lots of errors beginning from stb0899_init when I try to tune. I can provide remote access to a linux machine with this card on. Thank you, Bogdan Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy T USB XE
En/na Dietmar Segbert ha escrit: dvb-usb: did not find the firmware file. (af9005.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) dvb_usb_af9005: probe of 4-2:1.0 failed with error -2 I use slackware 10.2 and so the firmware file af9005.fw is in /lib/ firmware/. I suppose that you have to configure your hotplug so that it finds the firmware and sends it to the kernel. Sorry, I cannot help you here since it just works(tm) here. I can say that in my system where to look for the firmware and how to react to kernel requests is configured in /etc/hotplug/firmware.agent I will be happy for any help, especially for an how-to to create the af9005-driver for an 2.4.34 kernel, that i am normally use. I think that'll be difficult :-( Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy T USB XE
En/na Luca Olivetti ha escrit: En/na Dietmar Segbert ha escrit: dvb-usb: did not find the firmware file. (af9005.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) dvb_usb_af9005: probe of 4-2:1.0 failed with error -2 I use slackware 10.2 and so the firmware file af9005.fw is in /lib/ firmware/. I suppose that you have to configure your hotplug so that it finds the firmware and sends it to the kernel. Sorry, I cannot help you here since it just works(tm) here. I can say that in my system where to look for the firmware and how to react to kernel requests is configured in /etc/hotplug/firmware.agent I will be happy for any help, especially for an how-to to create the af9005-driver for an 2.4.34 kernel, that i am normally use. I think that'll be difficult :-( BTW, arcor.de refuses my mail, so I won't comment any further until they fix their mailserver. Surry, I'm tired of incompetent mail admins that just rely on stupid blacklists maintained by anti-spam vigilantes (that only amplify the problem, i.e. rendering communication difficult, instead of solving it) instead of intelligently dealing with spam. I know it's not your fault, but be warned that, due to the incompetent mail admins of the isp you're using, you're surely losing legitimate email. Note also that if you try to contact me directly you won't be able to, since a while ago I took the decision to only accept mail I can answer to (i.e. I verify that the sender address accepts my mail before accepting an incoming message). Bye. -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] How does bad reception influence quality of macroblocks?
En/na Richard Scobie ha escrit: status 03 | signal 8675 | snr | ber 001f | unc | status 1f | signal 8435 | snr | ber | unc 0013 | FE_HAS_LOCK status 1f | signal 8455 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 844e | snr | ber | unc | FE_HAS_LOCK The crucial ones here are ber and unc. These values are useless anyway: no driver (or at least none of the one I looked at to write my own) complies with the specification of the api, so the magnitudes aren't comparable between one card and the other. In fact, if you want to know how a driver is to scale the values you have to look at an older specification of the api, since the current one doesn't give any hint on the scale of these values. As a side note, the api spec says that unc should be cumulative during the lifetime of the frontend, so this driver (and probably most others) is wrong, since the value cannot go back to 0 after being 13. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec Cinergy t USB XE
En/na Dietmar Segbert ha escrit: Hello, i am searching for an kernel modul for the Terratec cinergy t usb xe dvb-t stick, that i can use with a 2.4.34 kernel. I have only found a modul for v4l-dvb and 2.6.x kernels. It is called af9005. I don't think it's possible to compile it under 2.4 (though, with some coaxing, I'm using it under 2.6.3). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005, remote with lircd
En/na Matthäus Janiczek ha escrit: Sorry, it took me a little bit longer, to test if the remote even work in Windows. And the result is: It does. But the strange thing is, that even after the right input in Linux (btw. thank you for correcting me... damn how stupid I was) nothing happend. I can press whatever i want to press but i do get no signal :/ The last debug messages which are written in the debug file are from booting up the system. Strange, there should be a lot more messages (i.e. informing of the discovery and initialization of the stick, but then it all depends on how syslogd is configured). So could it be that I need a very different code or something like that? It's possible but I doubt it. You can try to load dvb-usb-af9005.ko with debug=4 (as well as dvb-usb-af9005-remote.ko with debug=1), then it should dump whatever it receives from the remote. Of course you have to discover first where your syslogd dumps these messages. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec cinergy T USB XE driver status
En/na Marco Ballesio ha escrit: Hi Luca, thank you for the informations. After downloading the last snapshot from linux-dvb, applying the modifications as suggested in the URL and changing the id numbers in the driver source (and of course compiling and installing all the stuff) I was finally able to scan for a list of channels but, at the moment, I cannot see anything with xine :(. I must admit the version of the player I'm using, even supporting DVB, is quite old and today I'll try again with the last one. I tried it with xine v0.99.4cvs and mplayer 1.0pre6. Hardly bleeding edge. Of course my stick is not a cinergy, I just got the report from a user. Note that the performance of the tuner isn't exceptional, but, at least with my no name stick, it's no different under windows. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Again Pinnacle 71e
En/na Jussi Larjo ha escrit: hello again, thanks to Oliver, I suppose the chipset on my Pinnacle 71e is afatec, uses driver AF15BDA.sys on windows. the .inf file lists several entries like AF15BDA.FriendlyName= AF9015 BDA Filter so I guess the chipset is AF9015. What now? you'll have to wait: http://www.linuxtv.org/wiki/index.php/AF9015 -- Bye ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005, remote with lircd
En/na Matthäus Janiczek ha escrit: /Sorry for not replied earlier but i had to bought an new battery to be sure that the remote gets power :) So, i tried /sudo rmmod dvb-usb-af9005-remote sudo modprobe dvb-usb-af9005-remote debug=1 /and / ///sudo rmmod dvb-usb-af9005-remote sudo modprobe dvb-usb-af9005-remote debug=1 raw_code_log// It doesn't work that way, you have to look for the debug messages in /var/log/messages. Oh, and before unloading dvb-usb-af9005-remote, you have to unload dvb-usb-af9005 to load the module with debug=1 but nothing happend :(/ /So I tried to prepare everything for lirc, I followed the instruction. after made /patch -p1 af9005-config.diff /in the v4l-dvb-kernel Directory i got this: / patching file linux/drivers/media/dvb/dvb-usb/Kconfig Hunk #1 succeeded at 168 (offset -12 lines). patching file linux/drivers/media/dvb/dvb-usb/Makefile Hunk #1 FAILED at 42. 1 out of 1 hunk FAILED -- saving rejects to file linux/drivers/media/dvb/dvb-usb/Makefile.rej Apply the patch *before* following the instructions in README.lirc. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Terratec cinergy T USB XE driver status
En/na Marco Ballesio ha escrit: Hi to all, I wonder know if someone is currently implementing or maintaining a driver for this device (in the latter case many thanks to anyone who could suggest me the correct one). From what I've read in this and others mailing lists probably TerraTec has sent someone (maybe Markus Rechberger?) some sort of technical specification. Being a linux spare-time driver developer and owning one of these adapters I'd like to contribute but, first of all, I need to obtain as much infos as possible about the device. I still haven't opened the chassis because of the 7-days warranty but, of course, I'll do that one of these nights :). Thanks in advance to anyone who would help. Hi, if the usb ids are 0x0ccd (vendor) and 0x0055 (device), I just received a report from a user telling me that it uses an af9005 and he made it work with the driver at http://ventoso.org/luca/af9005/ (after changing the ids). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [Fwd: [linux-dvb] af9005, remote with lircd]
En/na Matthäus Janiczek ha escrit: I've googled much but can't find a HowTo or a Documentation to integrate the custom lirc file which Luca wrote (or generally an costum lirc file) into LIRC. So I would guess I've to put the file somewhere before make and make file but I'm everything else then sure. And that's the way it comes that I beg you to tell me a how. Because after the Stick runs great the remote is the last thing I need to be absolutely happy :) Please help me :) Hi, I just wrote a README.lirc file with the instructions. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [Fwd: [linux-dvb] af9005, remote with lircd]
En/na Matthäus Janiczek ha escrit: And that's the way it comes that I beg you to tell me a how. Because after the Stick runs great the remote is the last thing I need to be absolutely happy :) BTW, if you're fine with the remote provided with the card, it should already work. If it doesn't it means that it generates different codes than the 2 remotes I know (1 mine and 1 from another user, download a fresh copy of the source in case you have an old table with just one remote), so I'd ask you to load the dvb-usb-af9005-remote module with debug=1 and check in the log the raw codes, check that they're repeatable (i.e., pressing the same key you should get the same code) and send me the mapping key-code so I can add your remote to the table (if it suits the model). Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech 9015 QT1010 *was* Unbranded USB DVB device afatech af9005
En/na Andrew Leech ha escrit: Well I'm making some progress here, but I feel I'm shooting in the dark a bit. I've got the firmware loading, using the firmware that was in the sample code (it's a big array of data packets to be sent). So replacing the AF9005 firmware code with new stuff to copy the firmware on, I suggest that you convert the firmware.h to a binary firmware I get it loading fine and the dongle responds that it has switched to firmware mode. Obviously I've got the basic low level usb communicaton working, which in itself was a bit of a chore. Afatech didn't keep much the same between the old and the new chip, but the 9005 still seems more similar to my 9015 than other chips source files I've been browsing. But now I'm getting lostthere's just so much to do I don't know where to start. Is there any documentation around describing what needs to be implemented where to fit into the dvb-usb framework? I can't seem to find much, and wading through the header files feels like I'm just hitting things at random. I know the feeling ;-) You just need a lot of patience. It's not easy to follow things but you have the source for all of the dvb framework. You also have sample code from afactech (which may or may not be 100% correct, but it should help making sense of the documentation). What I did is copy another driver as a skeleton, then looked at the other files in the dvb subdirectories to see what function the driver had to implement. Besides, the af9015 documentation is better than the af9005 one ;-) (In fact, when things didn't work, I had to analyze the usb traffic under windows to find the differences with the sample code, a slow and painful process, as you may imagine). I've been trying to focus on getting the i2c working, the AF9015 chip has got a different interface to the AF9005, so that needs a considerable re-write, but again I don't know what interfaces need to be written to handle what information. I didn't know either, but I looked at what other drivers are doing and (specifically) how the mt2060 uses the i2c adapter. Look at af9005_i2c_xfer and af9005_i2c_algo, these are what an i2c adapter should do (in fact I just implemented what is needed by the mt2060, but it should also work with the qt1010). Once the device emulates an i2c adapter (by providing the appropriate functions, filling the i2c_algo field in dvb_usb_device_properties and telling in caps that DVB_USB_IS_AN_I2C_ADAPTER), the tuner code can use it to talk to the tuner. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech 9015 QT1010
En/na Zsolt ha escrit: Am Donnerstag, 25. Januar 2007 13:20 schrieb Andrew Leech: ... So basically I'm asking if there's any documentation around on what to implement, or at least some pointers in the right direction? are you shure you need the i2c stuff? is the af9015 not more like the twinhandtv (vp7045) as the af9005? just guessed :-) Yes, he does: with the af9015, like with the af9005, it is responsibility of the driver to talk to the tuner via i2c, the firmware doesn't abstract the tuner. At least according to the documentation. However implementing the i2c stuff is not that difficult. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] af9005, remote with lircd
Hi, I looked at the other usb drivers and all of them get a decoded key from the adapter, so they just map the code to a keypress and put it in the input device. OTOH the af9005 doesn't decode the ir data, it just gives the length of the spaces/pulses. I decode them in software (with the codes of the remote that came with the stick) to do the same that the other drivers are doing (i.e. emulate a keyboard). Now I wrote another rather simple module that just passes on the raw data as a lirc device for lircd to decode, so in theory it should work with any remote. It seems to work fairly well (I tried with a lircd.conf that I'm using with lirc_serial and recording the stock remote with irrecord). The problem is that it needs lirc, which isn't included in the stock kernel, so I don't know if it can be integrated in the linux-dvb driver. Comments, opinions? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Unbranded USB DVB device afatech af9005
En/na Raziel ha escrit: And maybe a short HowTo to make your drivers and firewall run, what I am really looking for :) Hi, sorry for not replying earlier. Now there's a short README file at http://ventoso.org/luca/af9005/ Bye -- Luca A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mailing lists? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Unbranded USB DVB device afatech af9005
En/na Luca Olivetti ha escrit: Ok, I have what I think is a working driver (I have bad reception quality but that's even worse under windows), now what should I do? I reiterate, and reformulate, my question: what should I do to have the driver integrated in v4l-dvb? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Unbranded USB DVB device afatech af9005
En/na Zsolt ha escrit: Am Donnerstag, 4. Januar 2007 00:59 schrieb Luca Olivetti: ... dear luca, plz can you send me some usbsniff log files from your device (few lines of device init and data exhange), i play around with an af9015 chip model and like to know if it is a complete other design or not. Everything is at http://ventoso.org/luca/af9005/ afatech.log is probably what you're looking for: it is not a plain usbsniff log but a partially interpreted log with much of the dross removed (the af9005 uses two different endpoints for reading and writing, I just removed all the chit-chat and left the raw data, plus a decode of the type of command/reply and the possible name of register -- most registers are only a few bits, so the same byte address can contain many registers) . mini.log is even more reduced, it has only the interpreted commands (with some comments that I wrote, by now they are obsolete). And then there's the driver you can look at. Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Unbranded USB DVB device afatech af9005
En/na Luca Olivetti ha escrit: En/na Luca Olivetti ha escrit: En/na Thomas Pinz ha escrit: Hi Stephen, On Friday 03 November 2006 13:11, Stephen D. Strowes wrote: The markings on one chip are: AF9005-L2* 0615 HJA6S The AF9005 cames from a company called afatek and is a DVB-T demodulator. But nobody wasn't able to write a driver for this IC and also the vendor seems to has no intrest on linux. I just contacted them and they replied (not with the specifications, though, they just asked me if I wanted to write a driver for my own use or to publish it). I hope they'll reply with some info. Well, they did: they just sent the complete documentation and sample source code, so it doesn't seem to be the case that they aren't interested, maybe nobody asked them before. In case that I'm unable to write a driver (most probable since I'm not that experienced), is there someone willing to help? Ok, I have what I think is a working driver (I have bad reception quality but that's even worse under windows), now what should I do? Bye -- Luca ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: Linuxdvb on small Linux
Hi, On Mon, 2004-06-28 at 14:50, Irek Defée wrote: Has anybody tried to run linuxdvb drivers on a small Linux distribution? Running on a very small harddisk or compact flash card? I am currently using the drivers in a home maden distribution booting from a disk-on-chip (about 15MB). Everything is compiled from scratch. [...] Mandrake Linux 9.2 is installed in the truly-minimal configuration mode, we managed to get it on a 210 MB harddisk partition, with system occupying 89 MB. The we tried to install drivers compiled on another machine with the same Linux. That looks OK but entries in /dev are not created and in the end nothing works but also there are no message errors. Anybody has hints what is done wrong? I think you have to create the device files in /dev by yourself (see MAKEDEV-DVB.sh, or something like that). Luca -- _ Copy this in your signature, if you think it is important: N OW A R ! ! ! -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Treccia di Bufala Campana comprala su Terrasolis.com Spedizione Gratis per spese superiori a 85 Euro Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid$93d(-6cca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid#38d(-6
[linux-dvb] Re: Nova-CI: why does opening /dev/dvb/adapter0/ca0 return no such device?
Hi all, On Tue, 2004-01-20 at 13:24, Carlo E. Prelz wrote: Subject: [linux-dvb] Re: Nova-CI: why does opening /dev/dvb/adapter0/ca0 return no such device? Date: mar, gen 20, 2004 at 02:01:55 +0100 Quoting Johannes Stezenbach ([EMAIL PROTECTED]): Is someone having success with accessing the CAM on such a card? Or am I overlooking something critical? I'm sorry to have to disappoint you, but the common interface is not supported because we have no information from the vendor how it works. I added a note to Kconfig accordingly. Well, I hope this helps others not to make the same mistake I did... Is the Hauppauge Nexus the only possibility for using a CAM, so? Or are there better choices? I'd also like to know if there is some budget CI card that works under linux... Thanks, Luca -- _ Copy this in your signature, if you think it is important: N OW A R ! ! ! -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [RFC] Limitations of current filtering
Hi all, [...] The TS_TAP method has a big limitation; there is only one /dev/dvb/adapter/dvrY device, so it's not possible to read two sets of pids (as it's necessary when one wants to separately record two television channels with identical frontend settings). Sorry, I am not an expert, but I think this kind of demultiplexing shoud be done in user space. In other words: I think that a single dvr device is ok: we can select all the pids that we need and then a user-space program can read the dvr device and generate all the desired TSs (it is pretty simple, I think). I suspect that any other solution would require to move this simple demultiplexing code from user space to kernel space. But, as I said, I am not an expert (just a random user) hence I might be completely wrong. Luca -- _ Copy this in your signature, if you think it is important: N OW A R ! ! ! -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] How to receive a TS containing PAT and PMT?
Hi all, since I am not able to dump the whole TS received by my DVB-S card, I am trying a different approach: 1) I use DMX_SET_PES_FILTER for selecting PID 0 (the PAT), and I read the resulting stream from /dev/dvb/adapter0/dvr0 2) I parse the PAT, finding the PIDs of the various PMTs, and I dynamically select those PIDs by using DMX_SET_PES_FILTER 3) I parse the PMTs, selecting the PIDs of the ESs (again, by using DMX_SET_PES_FILTER) Steps 1) and 2) work ok (I can receive in /dev/dvb/adapter0/dvr0 a TS containing the PAT only, or a TS containing PAT+PMT), but as soon as I select the first ES PID the stream is corrupted... Hence, I am beginning to wonder if my approach is correct or not. Any ideas? Summing up: I'd like to receive a TS containing the PAT, one or more PMT, and the relative PESs... What's the best way to achieve this result? Thanks, Luca -- _ Copy this in your signature, if you think it is important: N OW A R ! ! ! -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Hai una fotocamera digitale e vuoi stampare le tue immagini su vera carta fotografica professionale? Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1533d=16-10 -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: How to receive a TS containing PAT and PMT?
Hi Johannes, [...] Steps 1) and 2) work ok (I can receive in /dev/dvb/adapter0/dvr0 a TS containing the PAT only, or a TS containing PAT+PMT), but as soon as I select the first ES PID the stream is corrupted... What exactly do you mean by corrupted? Basically, before selecting the first ES PID I can parse all the PAT and PMT packets that I receive, the PAT section lenght is 33 and the PMT section lenght is about 50. The Payload Unit Start Indicator bit is always 1. After selecting an ES PID, I receive a PAT packet (PID = 0x00) with the Payload Unit Start Indicator bit equal to 0, but the previous PAT section is already finished, hence I think this is an error (isn't it?). This is very strange, because it happens only after selecting an ES PID. Also, I receive some PES packets with the Payload Unit Start Indicator bit set to 1, but the Packet Start Code Prefix is wrong... Thanks, Luca -- _ Copy this in your signature, if you think it is important: N OW A R ! ! ! -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Ritrova la linea! Nel reparto Dimagrimento troverai tanti prodotti che faranno al caso tuo! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2045d=16-10 -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
