[linux-dvb] I have the same experience with you.
You may need to have a look at the linux-dvb framework. The memory is allocated from systems' DMA area. So you will have to limit the buffer count to let your driver work correctly. Good luck. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] em28xx tv support under linux kernel.
On 9/10/07, kevin liu [EMAIL PROTECTED] wrote:
Dear Mako:
I am studying the em28xx codes under Linux kernel(2.6.20). It
seems that there is no ATSC or NTSC support.
In em28xx-card.c, it defines em28xx_boards array to specify the tv
card the driver can support, struct em28xx_input indicates the tv
input method, but in the em28xx_boards, there is no struct that
includes EM28XX_VMUX_TELEVISION.
I got puzzled by the driver now.
:{
Hi Kevin,
you might have a look at
http://mcentral.de/wiki/index.php/Em2880
after doing some cleanup I will commit some newer code this week
basically the implementation on mcentral.de takes care about alot
extra things.
Anyway the logs which you sent previously does not really show up what
device it is about (it moreover shows up that you own a device which
is supported by dvb_usb)
could you submit an lsusb output?
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] em28xx tv support under linux kernel.
On 9/10/07, Markus Rechberger [EMAIL PROTECTED] wrote:
On 9/10/07, kevin liu [EMAIL PROTECTED] wrote:
Dear Mako:
I am studying the em28xx codes under Linux kernel(2.6.20). It
seems that there is no ATSC or NTSC support.
In em28xx-card.c, it defines em28xx_boards array to specify the tv
card the driver can support, struct em28xx_input indicates the tv
input method, but in the em28xx_boards, there is no struct that
includes EM28XX_VMUX_TELEVISION.
I got puzzled by the driver now.
:{
Hi Kevin,
you might have a look at
http://mcentral.de/wiki/index.php/Em2880
after doing some cleanup I will commit some newer code this week
basically the implementation on mcentral.de takes care about alot
extra things.
Anyway the logs which you sent previously does not really show up what
device it is about (it moreover shows up that you own a device which
is supported by dvb_usb)
could you submit an lsusb output?
Just as a reference, I'm refering to the mail which got submitted
earlier to the em28xx ML; if it's still about the same device it's not
supported by the em28xx.
http://www.mail-archive.com/linux-dvb%40linuxtv.org/msg24925.html
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB0700 firmware - next try
Hi all, Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw ? Don't forget to either change the referring firmware filename in dib0700_devices.c or rename the file to the current name. Please report whether it works better, the same or less good. best regards, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
On Mon, 2007-09-10 at 11:14 +0200, Patrick Boettcher wrote: Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw ? Don't forget to either change the referring firmware filename in dib0700_devices.c or rename the file to the current name. Please report whether it works better, the same or less good. In place, with the machine now turned off. I now need a human being at home to turn it back on in order to get a card in cold state and a fresh load of the new firmware... Just for our general education, what changed? Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
On Mon, 10 Sep 2007, Nicolas Will wrote: On Mon, 2007-09-10 at 11:14 +0200, Patrick Boettcher wrote: Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw ? Don't forget to either change the referring firmware filename in dib0700_devices.c or rename the file to the current name. Please report whether it works better, the same or less good. In place, with the machine now turned off. I now need a human being at home to turn it back on in order to get a card in cold state and a fresh load of the new firmware... Just for our general education, what changed? Some fixes regarding USB. The exact fixes I'm not able to (able in the sense of not understanding) to repeat ;) . Patrick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Greetings from IBC
Greetings from IBC. I have a cx88xx analog card at out booth that works badly in linux. I went to the Conexant booth to ask them about linux support of their chips and the answer was clear: No, no and no. It seems they are afraid of hackers and their main concern is digital rights managemet such as macrovision that can be disabled too easily if we get their specs. And they say they would lose all their business if that could be done. Right. But at least I know that Conexant based cards is something not to buy any time soon. I have no idea how official company policy that is. Maybe they just randomly picked an explanation. I visited Technotrend also and they were a lot more linux friendly. The guy at the booth was aware of vdr even he is not a technical person. And he told me that the FF-cards will be on the market and developing in the future too. Anyway, if some of you happen to be at the IBC, I'll be at booth 2.116 doing some broadcasting with linux based tools. And if you yourself aren't here, but have any difficult questions to some exhibitors, I might have to time go talk to them for you. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
Hi, Patrick Boettcher píše v Po 10. 09. 2007 v 11:14 +0200: Hi all, Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw ? Leadtek Winfast DTV Dongle remote controller: 1) no key pressed 2) push key 2a) repetitively send key code 3) push another key - 2a) In firmware dvb-usb-dib0700-01.fw no IR receiver found. With dvb-usb-dib0700-02.fw IR receiver registered, but read error. With dvb-usb-dib0700-03-pre1.fw IR receiver registered, repetition key code sending. With dvb-usb-dib0700-1.10.fw the same. Is it bug in fw or in driver? Don't forget to either change the referring firmware filename in dib0700_devices.c or rename the file to the current name. Please report whether it works better, the same or less good. best regards, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ -- Jaroslav Bartoň DjAARA [EMAIL PROTECTED] [EMAIL PROTECTED] +420 608 620 897 JID : [EMAIL PROTECTED] JID2: [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Greetings from IBC
the booth was aware of vdr even he is not a technical person. And he told me that the FF-cards will be on the market and developing in the future too. do you mean FF card with h264 decoder ? do you know when this card will be on the market ? how much ? regards Igor ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Greetings from IBC
He didn't tell exactly what they are planning and I asked only about hdmi and the missing J2 block on the cable-card. He told me next year there might be a new ff-card model and didn't know about J2. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
On Monday 10 September 2007 11:44:39 Jaroslav Barton wrote: Hi, Patrick Boettcher píše v Po 10. 09. 2007 v 11:14 +0200: Hi all, Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dv b-usb-dib0700-1.10.fw ? Leadtek Winfast DTV Dongle remote controller: 1) no key pressed 2) push key 2a) repetitively send key code 3) push another key - 2a) Your remote control uses the NEC protocol. You can change it with a module option. The current driver won't handle the data coreectly. http://www.grunau.be/dib0700_rc_query.diff is a preliminary patch to add support for the NEC Protocol. Janne ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
Hi all, Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw ? Don't forget to either change the referring firmware filename in dib0700_devices.c or rename the file to the current name. Please report whether it works better, the same or less good. best regards, Patrick. Great... - Will that replace dvb-usb-dib0700-03-prel.fw ?? - Will it require the latest v4l-dvb source ?? Best Regards Joacim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge DEC-3000s
Hi! I have a Hauppauge DEC-3000s at home, which should, according to the documentation, work under linux, at least for watching tv. Now, as some other people already reported (some months ago) this is actually not true. And I would like to help, finally fixing this. However, all I can provide, is information. With this mail, I give you all information I have at the moment. First of all, initialisation seems to work. Dmesg reports the following: [CODE] usb 1-2: new full speed USB device using uhci_hcd and address 2 usb 1-2: configuration #1 chosen from 1 choice ttusb_dec: Firmware 2.316ttusb_dec: found DSP code DEC2540-t. usbcore: registered new interface driver ttusb-dec usb 1-2: USB disconnect, address 2 usb 1-2: new full speed USB device using uhci_hcd and address 3 usb 1-2: configuration #1 chosen from 1 choice DVB: registering new adapter (DEC3000-s). DVB: registering frontend 0 (TechnoTrend/Hauppauge DEC3000-s Frontend)... [/CODE] The necessary files for dvb are there, so I guess the initialisation works, somehow. I prefer using Kaffeine for watching tv, so I tried to scan for channels. The resulting dmesg output: [CODE] ttusbdecfe_read_status: returned unknown value: 0 [/CODE] and that about 15 times or so. To also show, that it is not (only probably) caused by kaffeine, I used a shipped channels.conf from dvb-apps, and szap (20070816) to switch to ProSieben. Szap shows the following: [CODE] reading channels from file '/root/.szap/channels.conf' zapping to 26 'ProSieben': sat 0, frequency = 12480 MHz V, symbolrate 2750, vpid = 0x00ff, apid = 0x0100 sid = 0x0382 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' FE_DISEQC_SEND_BURST failed: Operation not supported FE_READ_STATUS failed: Connection timed out status 00 | signal fffe | snr fffe | ber fffe | unc fffe | FE_READ_STATUS failed: Connection timed out status 00 | signal fffe | snr fffe | ber fffe | unc fffe | FE_READ_STATUS failed: Connection timed out [/CODE] and so forth. The coresponding dmesg output: [CODE] ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusbdecfe_read_status: returned unknown value: 0 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusbdecfe_read_status: returned unknown value: 0 ttusbdecfe_read_status: returned unknown value: 0 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusbdecfe_read_status: returned unknown value: 0 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusbdecfe_read_status: returned unknown value: 0 ttusbdecfe_read_status: returned unknown value: 0 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusbdecfe_read_status: returned unknown value: 0 ttusbdecfe_read_status: returned unknown value: 0 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: Failed to lock usb mutex. ttusb_dec_send_command: Failed to lock usb mutex. ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusb_dec_send_command: result bulk message failed: error -110 ttusbdecfe_read_status: returned unknown value: 0 ttusb_dec_send_command: result bulk message failed: error -110 [/CODE] So this is all I have at the moment, but if someone is able to tell me, how to get more information, I'll do that. However, I hope that this will bring some light in the current situation of DEC-support under linux.
Re: [linux-dvb] DiB0700 firmware - next try
On Mon, 10 Sep 2007, Maillist wrote: Hi all, Some time has gone by and there have been some fixes. Can everyone please try the latest firmware from http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw ? Don't forget to either change the referring firmware filename in dib0700_devices.c or rename the file to the current name. Please report whether it works better, the same or less good. best regards, Patrick. Great... - Will that replace dvb-usb-dib0700-03-prel.fw ?? If it works better, yes. - Will it require the latest v4l-dvb source ?? Yes it is better. Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
Leadtek Winfast DTV Dongle remote controller: 1) no key pressed 2) push key 2a) repetitively send key code 3) push another key - 2a) Your remote control uses the NEC protocol. You can change it with a module option. The current driver won't handle the data coreectly. http://www.grunau.be/dib0700_rc_query.diff is a preliminary patch to add support for the NEC Protocol. Great! How can I help? Janne ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Jaroslav Bartoň DjAARA [EMAIL PROTECTED] [EMAIL PROTECTED] +420 608 620 897 JID : [EMAIL PROTECTED] JID2: [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem building newest DVB Drivers
Hi, i wanted to install the newest DVB-drivers but during the make i get an error (running ubuntu dapper): |CC [M] /usr/src/v4l-dvb/v4l/cx88-alsa.o /usr/src/v4l-dvb/v4l/cx88-alsa.c:42:23: error: sound/tlv.h: No such file or directory /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: error: syntax error before '-' token /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: warning: type defaults to 'int' in declaration of 'DECLARE_TLV_DB_SCALE' /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: warning: function declaration isn't a prototype /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: warning: type qualifiers ignored on function return type /usr/src/v4l-dvb/v4l/cx88-alsa.c:667: error: 'SNDRV_CTL_ELEM_ACCESS_TLV_READ' undeclared here (not in a function) /usr/src/v4l-dvb/v4l/cx88-alsa.c:672: error: unknown field 'tlv' specified in initializer /usr/src/v4l-dvb/v4l/cx88-alsa.c:672: error: 'snd_cx88_db_scale' undeclared here (not in a function) make[3]: *** [/usr/src/v4l-dvb/v4l/cx88-alsa.o] Error 1 make[2]: *** [_module_/usr/src/v4l-dvb/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.15-26-server' make[1]: *** [default] Error 2 make[1]: Leaving directory `/usr/src/v4l-dvb/v4l' make: *** [all] Error 2 Regards, Dennis | ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem building newest DVB Drivers
Dennis Schwan wrote: Hi, i wanted to install the newest DVB-drivers but during the make i get an error (running ubuntu dapper): |CC [M] /usr/src/v4l-dvb/v4l/cx88-alsa.o /usr/src/v4l-dvb/v4l/cx88-alsa.c:42:23: error: sound/tlv.h: No such file or directory /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: error: syntax error before '-' token /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: warning: type defaults to 'int' in declaration of 'DECLARE_TLV_DB_SCALE' /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: warning: function declaration isn't a prototype /usr/src/v4l-dvb/v4l/cx88-alsa.c:662: warning: type qualifiers ignored on function return type /usr/src/v4l-dvb/v4l/cx88-alsa.c:667: error: 'SNDRV_CTL_ELEM_ACCESS_TLV_READ' undeclared here (not in a function) /usr/src/v4l-dvb/v4l/cx88-alsa.c:672: error: unknown field 'tlv' specified in initializer /usr/src/v4l-dvb/v4l/cx88-alsa.c:672: error: 'snd_cx88_db_scale' undeclared here (not in a function) make[3]: *** [/usr/src/v4l-dvb/v4l/cx88-alsa.o] Error 1 make[2]: *** [_module_/usr/src/v4l-dvb/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.15-26-server' make[1]: *** [default] Error 2 make[1]: Leaving directory `/usr/src/v4l-dvb/v4l' make: *** [all] Error 2 Dennis, Kernel backwards compat has been broken in the master branch against older kernels... Until it's fixed, you can use one of my devel trees, which still builds fine against older kernels... Instead, try: http://linuxtv.org/hg/~mkrufky/dvb-pll You shouldn't have any problems there. Cheers, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] TUV1236d / dvb-pll: rf input switching via module option
On Mon, Sep 10, 2007 at 12:12:01PM -0500, David Engel wrote:
Unfortunately, this does not allow for REVERSING the input selection --
this will only force it to use one or the other in digital mode. If
anybody has some ideas as to how to reverse the default selection in a
clean way, I am open to suggestions.
The attached patch, is completely untested (I didn't even try
compiling it), but it should be close.
Take two, with the patch.
David
--
David Engel
[EMAIL PROTECTED]
diff -r b7fa7c4598ac linux/drivers/media/dvb/frontends/dvb-pll.c
--- a/linux/drivers/media/dvb/frontends/dvb-pll.c Sun Sep 09 12:00:45 2007 -0400
+++ b/linux/drivers/media/dvb/frontends/dvb-pll.c Mon Sep 10 11:58:50 2007 -0500
@@ -49,9 +49,9 @@ module_param(debug, int, 0644);
module_param(debug, int, 0644);
MODULE_PARM_DESC(debug, enable verbose debug messages);
-static unsigned int input[DVB_PLL_MAX] = { [ 0 ... (DVB_PLL_MAX-1) ] = 0 };
+static int input[DVB_PLL_MAX] = { [ 0 ... (DVB_PLL_MAX-1) ] = 0 };
module_param_array(input, int, NULL, 0644);
-MODULE_PARM_DESC(input,specify rf input choice, 0 for autoselect (default));
+MODULE_PARM_DESC(input,specify rf input choice, 0 for autoselect (default), -1 for autoselect reversed);
static unsigned int id[DVB_PLL_MAX] =
{ [ 0 ... (DVB_PLL_MAX-1) ] = DVB_PLL_UNDEFINED };
@@ -399,9 +399,10 @@ static void tuv1236d_rf(struct dvb_front
const struct dvb_frontend_parameters *params)
{
struct dvb_pll_priv *priv = fe-tuner_priv;
- unsigned int new_rf = input[priv-nr];
-
- if ((new_rf == 0) || (new_rf 2)) {
+ int new_rf = input[priv-nr];
+
+ if ((new_rf = 0) || (new_rf 2)) {
+ int reverse = (new_rf == -1);
switch (params-u.vsb.modulation) {
case QAM_64:
case QAM_256:
@@ -411,6 +412,8 @@ static void tuv1236d_rf(struct dvb_front
default:
new_rf = 2;
}
+ if (reverse)
+ new_rf = 3 - new_rf;
}
switch (new_rf) {
@@ -856,6 +859,9 @@ struct dvb_frontend *dvb_pll_attach(stru
printk( %d-%04x, i2c_adapter_id(i2c), pll_addr);
printk(: tuner rf input will be );
switch (input[priv-nr]) {
+ case -1:
+ printk(autoselected reversed\n);
+ break;
case 0:
printk(autoselected\n);
break;
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] TUV1236d / dvb-pll: rf input switching via module option
David Engel wrote:
On Mon, Sep 10, 2007 at 12:12:01PM -0500, David Engel wrote:
Unfortunately, this does not allow for REVERSING the input selection --
this will only force it to use one or the other in digital mode. If
anybody has some ideas as to how to reverse the default selection in a
clean way, I am open to suggestions.
The attached patch, is completely untested (I didn't even try
compiling it), but it should be close.
Take two, with the patch.
David,
This is the same thing I did in my tree, but just didn't push it to the
repository.
This would work, but it doesn't cover all possible cases. For instance,
what if there was a tuner with three rf inputs? I don't think that such
a device exists on any supported hardware, but you never know.
This solution is fine with me, for the meanwhile... if you could test
it, would be nice :-)
-Mike
diff -r b7fa7c4598ac linux/drivers/media/dvb/frontends/dvb-pll.c
--- a/linux/drivers/media/dvb/frontends/dvb-pll.c Sun Sep 09 12:00:45
2007 -0400
+++ b/linux/drivers/media/dvb/frontends/dvb-pll.c Mon Sep 10 11:58:50
2007 -0500
@@ -49,9 +49,9 @@ module_param(debug, int, 0644);
module_param(debug, int, 0644);
MODULE_PARM_DESC(debug, enable verbose debug messages);
-static unsigned int input[DVB_PLL_MAX] = { [ 0 ... (DVB_PLL_MAX-1) ] = 0 };
+static int input[DVB_PLL_MAX] = { [ 0 ... (DVB_PLL_MAX-1) ] = 0 };
module_param_array(input, int, NULL, 0644);
-MODULE_PARM_DESC(input,specify rf input choice, 0 for autoselect
(default));
+MODULE_PARM_DESC(input,specify rf input choice, 0 for autoselect (default),
-1 for autoselect reversed);
static unsigned int id[DVB_PLL_MAX] =
{ [ 0 ... (DVB_PLL_MAX-1) ] = DVB_PLL_UNDEFINED };
@@ -399,9 +399,10 @@ static void tuv1236d_rf(struct dvb_front
const struct dvb_frontend_parameters *params)
{
struct dvb_pll_priv *priv = fe-tuner_priv;
- unsigned int new_rf = input[priv-nr];
-
- if ((new_rf == 0) || (new_rf 2)) {
+ int new_rf = input[priv-nr];
+
+ if ((new_rf = 0) || (new_rf 2)) {
+ int reverse = (new_rf == -1);
switch (params-u.vsb.modulation) {
case QAM_64:
case QAM_256:
@@ -411,6 +412,8 @@ static void tuv1236d_rf(struct dvb_front
default:
new_rf = 2;
}
+ if (reverse)
+ new_rf = 3 - new_rf;
}
switch (new_rf) {
@@ -856,6 +859,9 @@ struct dvb_frontend *dvb_pll_attach(stru
printk( %d-%04x, i2c_adapter_id(i2c), pll_addr);
printk(: tuner rf input will be );
switch (input[priv-nr]) {
+ case -1:
+ printk(autoselected reversed\n);
+ break;
case 0:
printk(autoselected\n);
break;
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] CinergyT2 dvb-usb driver (incomplete first version or such)
Hi, I've had quite a lot of problems with the existing Cinergy T2-driver (keyboard hangs sooner or later). Therefore I've converted the existing driver to use dvb-usb framework as used in the vp7045-driver. The current version of the converted driver seems to work OK, although the remote controller code has been disabled for now. Hi, I'm very interested in that driver, as I also had some problems with the original driver in the past, and the original authors don't maintain it anymore. So if you need some testers, I'd be glad to help. I also know Holger in person and could ask him to help if needed. However, for productive testing I would need working remote controller support. :-) I've attached a version of the original CinergyT2-driver which has been merged to work with dvb-usb framework.. It should compile with the latest HG-version of DVB-sources if you just untar the contents on top of the current HG CinergyT2-source code. It spits out error about enabling/disabling device power, but the actual command seems to go through just fine (for some reason any usb_bulk_msg() read will fail in power_ctrl-handler atm.). Also the remote control handler is currently disabled for now (as mentioned before). Otherwise the current driver seem to work at leat here just fine. I'm very interested to hear any comments about this merged version of CinergyT2 driver ... Regards, Tomi Orava -- tomimo+linux-dvb at ncircle.nullnet.fi cinergyT2-hg.tar.bz2 Description: BZip2 compressed data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] TUV1236d / dvb-pll: rf input switching via module option
On Mon, Sep 10, 2007 at 03:04:32PM -0400, Michael Krufky wrote: This is the same thing I did in my tree, but just didn't push it to the repository. This would work, but it doesn't cover all possible cases. For instance, what if there was a tuner with three rf inputs? I don't think that such a device exists on any supported hardware, but you never know. Yes, devices with three or more inputs would be really troublesome this way. An alternative would be to have separate modules parameters per modulation type. Instead of dvb_pll taking an input parameter, it could, for example, take qam_input and vsb_input parameters. That could work as long as the number of modulation types doesn't grow much more. This solution is fine with me, for the meanwhile... if you could test it, would be nice :-) I will, but it take a few to serveral days. David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Question about dvb-usb driver stream settings
Hi Tomi,
On Sat, 8 Sep 2007, Tomi Orava wrote:
I've had quite a lot of problems with the existing Cinergy T2-driver
(keyboard hangs sooner or later). Therefore I've converted the existing
driver to use dvb-usb framework as used in the vp7045-driver. The current
version of the converted driver seems to work OK, although the remote
controller code has been disabled for now.
I'm still wondering about the stream-settings and especially if there
exists a predefined maximum value for the stream count-setting ?
If I use too large value in here, the module will load initialize just
fine but will crash in unregistering phase when unloading.
.stream = {
.type = USB_BULK,
.count = 7,
.endpoint = 0x02,
.u = {
.bulk = {
.buffersize = 4096,
}
}
},
The value 7 seems to work for the .count-variable, but
when I was testing larger values (like 30) the module crashed the
kernel in unloading phase:
The answer is simple, the maximum number of urbs you can have today is 10
(see dvb-usb.h #define MAX_NO_URBS_FOR_DATA_STREAM 10 ) . Maybe a check
would be appropriate.
However if you really have 4096 bytes urbs, 7 URBs should be enough on an
average system (so far nobody ever had problems with streaming which were
caused by too few URBs).
Are you sure that the size of the URBs returned by the USB-stack is 4096?
(load dvb-usb.ko with debug=0x100 and have a look at the lines lengh
number/4096 in syslog - it should be 4096 as number)
Patrick.
--
Mail: [EMAIL PROTECTED]
WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB0700 firmware - next try
Hi. I have Artec T14BR DVB-T USB dongle. It has DiBcom 7070PB and 0700C chips, so I assume it is close to the reference design. At least the USB device ID is not found in the sources (it is 05d8:810f), so I assume the sw (in http://linuxtv.org/hg/~pb/v4l-dvb/) does not directly support the HW. However the sources seem (on a cursory glance) support both chips so getting the dongle to work should not be huge task? What should I do next? No, I have never worked on USB nor v4l nor dvb. Nor with Linux kernel. Yes, I do know basic kernel stuff and too much C. -- @jhol http://jhol.dyndns.org/jhol/blog.html ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] autoconf for dvb-apps
To someone responsible for dvb-apps project Will you accept patch to add autoconf for dvb-apps? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
