[linux-dvb] HVR-4000 driver problems - i2c error

[linux-dvb] HVR-4000 driver problems - i2c error

[Ales Jurik]

Hi,

I've got a HVR-4000, but I have now some very strange problems.
I have Debian Leeny with 2.6.25-2 kernel and multiproto from Igor Lipianin hg 
running at Athlon64 X2 2700+ and Asus M2N-DVI mobo. 
Whole multiproto tree compiled without any problem.

- when starting system I got this message:

[   24.658572] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
[   24.659047] tuner-simple 0-0061: i2c i/o error: rc == -121 (should be 4)
[   23.609971] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)

- the firmware is loaded into the card at first time the card is opened - it 
is okay?

[  917.660620] cx24116_firmware_ondemand: Waiting for firmware upload 
(dvb-fe-cx24116.fw)...
[  917.703010] cx24116_firmware_ondemand: Waiting for firmware upload(2)...
[  922.703870] cx24116_load_firmware: FW version 1.22.82.0
[  922.703889] cx24116_firmware_ondemand: Firmware upload complete

The result is that only for some channels it is possible to get lock with 
szap2. VDR is hanging (or starting) when trying to tune to initial channel, 
even when this channel is set to channel at which is szap2 successfull. I'm 
not able to say criteria which channels are possible to lock.

Any hints are appreciated.

BR,

Ales

[    9.343037] Linux video capture interface: v2.00
...
[    9.465617] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
[    9.466569] cx88[0]: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 
DVB-S/S2/T/Hybrid [card=68,autodetected]
[    9.466622] cx88[0]: TV tuner type 63, Radio tuner type -1
...
[    9.497778] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
[    9.539221] cx2388x alsa driver version 0.0.6 loaded
[    9.596629] cx88[0]: i2c init: enabling analog demod on HVR1300/3000/4000 
tuner
[    9.672364] tuner' 0-0043: chip found @ 0x86 (cx88[0])
[    9.701019] tda9887 0-0043: creating new instance
[    9.701019] tda9887 0-0043: tda988[5/6/7] found
[    9.704336] tuner' 0-0061: chip found @ 0xc2 (cx88[0])
[    9.705311] tuner' 0-0063: chip found @ 0xc6 (cx88[0])
[    9.750913] tveeprom 0-0050: Hauppauge model 69009, rev B2D3, serial# 
3326338
[    9.750954] tveeprom 0-0050: MAC address is 00-0D-FE-32-C1-82
[    9.750991] tveeprom 0-0050: tuner model is Philips FMD1216MEX (idx 133, 
type 63)
[    9.751041] tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') 
PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4)
[    9.751093] tveeprom 0-0050: audio processor is CX882 (idx 33)
[    9.751131] tveeprom 0-0050: decoder processor is CX882 (idx 25)
[    9.751169] tveeprom 0-0050: has radio, has IR receiver, has no IR 
transmitter
[    9.751218] cx88[0]: hauppauge eeprom: model=69009
[    9.802610] tuner-simple 0-0061: creating new instance
[    9.802610] tuner-simple 0-0061: type set to 63 (Philips FMD1216ME MK3 
Hybrid Tuner)
[    9.805659] input: cx88 IR (Hauppauge WinTV-HVR400 as /class/input/input6
[    9.850619] cx88[0]/2: cx2388x 8802 Driver Manager
[    9.850619] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 19
[    9.850619] ACPI: PCI Interrupt 0000:01:06.2[A] -> Link [LNKA] -> GSI 19 
(level, low) -> IRQ 19
[    9.850619] cx88[0]/2: found at 0000:01:06.2, rev: 5, irq: 19, latency: 64, 
mmio: 0xfb000000
[    9.849788] ACPI: PCI Interrupt Link [LNEA] enabled at IRQ 18
[    9.849840] ACPI: PCI Interrupt 0000:04:00.0[A] -> <6>ACPI: PCI Interrupt 
0000:01:06.1[A] -> Link [LNKA] -> GSI 19 (level, low) -> IRQ 19
[    9.850619] cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
[    9.849841] Link [LNEA] -> GSI 18 (level, low) -> IRQ 18
...
[    9.901424] cx88/2: cx2388x dvb driver version 0.0.6 loaded
[    9.901465] cx88/2: registering cx8802 driver, type: dvb access: shared
[    9.901505] cx88[0]/2: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 
DVB-S/S2/T/Hybrid [card=68]
[    9.901557] cx88[0]/2: cx2388x based DVB/ATSC card
...
[    9.976606] DVB: registering new adapter (cx88[0])
[    9.976648] DVB: registering frontend 0 (Conexant CX24116/CX24118)...
[   10.053023] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKA] -> GSI 19 
(level, low) -> IRQ 19
[   10.053123] cx88[0]/0: found at 0000:01:06.0, rev: 5, irq: 19, latency: 64, 
mmio: 0xfd000000
[   10.053216] cx88[0]/0: registered device video0 [v4l2]
[   10.053270] cx88[0]/0: registered device vbi0
[   10.053321] cx88[0]/0: registered device radio0
...
[   24.658572] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
[   24.659047] tuner-simple 0-0061: i2c i/o error: rc == -121 (should be 4)
[   23.609971] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
...
[  917.660620] cx24116_firmware_ondemand: Waiting for firmware upload 
(dvb-fe-cx24116.fw)...
[  917.703010] cx24116_firmware_ondemand: Waiting for firmware upload(2)...
[  922.703870] cx24116_load_firmware: FW version 1.22.82.0
[  922.703889] cx24116_firmware_ondemand: Firmware upload complete

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Steven Toth]

Ales Jurik wrote:
> Hi,
> 
> I've got a HVR-4000, but I have now some very strange problems.
> I have Debian Leeny with 2.6.25-2 kernel and multiproto from Igor Lipianin hg 
> running at Athlon64 X2 2700+ and Asus M2N-DVI mobo. 
> Whole multiproto tree compiled without any problem.
> 
> - when starting system I got this message:
> 
> [   24.658572] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
> [   24.659047] tuner-simple 0-0061: i2c i/o error: rc == -121 (should be 4)
> [   23.609971] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
> 
> - the firmware is loaded into the card at first time the card is opened - it 
> is okay?
> 
> [  917.660620] cx24116_firmware_ondemand: Waiting for firmware upload 
> (dvb-fe-cx24116.fw)...
> [  917.703010] cx24116_firmware_ondemand: Waiting for firmware upload(2)...
> [  922.703870] cx24116_load_firmware: FW version 1.22.82.0
> [  922.703889] cx24116_firmware_ondemand: Firmware upload complete
> 
> The result is that only for some channels it is possible to get lock with 
> szap2. VDR is hanging (or starting) when trying to tune to initial channel, 
> even when this channel is set to channel at which is szap2 successfull. I'm 
> not able to say criteria which channels are possible to lock.
> 
> Any hints are appreciated.

I fixed an issue with cx88 sometime ago where a value of 0 (taken from 
the cards struct) was being written to the GPIO register, resulting in 
the same i2c issues.

It looks a lot like this.

- Steve



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Ales Jurik]

On Monday 18 of August 2008, Steven Toth wrote:
> Ales Jurik wrote:
> > Hi,
> >
> > I've got a HVR-4000, but I have now some very strange problems.
> > I have Debian Leeny with 2.6.25-2 kernel and multiproto from Igor
> > Lipianin hg running at Athlon64 X2 2700+ and Asus M2N-DVI mobo.
> > Whole multiproto tree compiled without any problem.
> >
> > - when starting system I got this message:
> >
> > [   24.658572] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
> > [   24.659047] tuner-simple 0-0061: i2c i/o error: rc == -121 (should be
> > 4) [   23.609971] tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
> >
>
> I fixed an issue with cx88 sometime ago where a value of 0 (taken from
> the cards struct) was being written to the GPIO register, resulting in
> the same i2c issues.
>
> It looks a lot like this.
>
> - Steve

Yes, after few hours using google I also found such remarks, but please could 
you be more specific? I don't have any documentation for chips used at 
HVR-4000.

Thanks,

Ales


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Mika Laitio]

>> - the firmware is loaded into the card at first time the card is opened - it
>> is okay?
>>
>> [  917.660620] cx24116_firmware_ondemand: Waiting for firmware upload
>> (dvb-fe-cx24116.fw)...
>> [  917.703010] cx24116_firmware_ondemand: Waiting for firmware upload(2)...
>> [  922.703870] cx24116_load_firmware: FW version 1.22.82.0
>> [  922.703889] cx24116_firmware_ondemand: Firmware upload complete
>>
>> The result is that only for some channels it is possible to get lock with
>> szap2. VDR is hanging (or starting) when trying to tune to initial channel,
>> even when this channel is set to channel at which is szap2 successfull. I'm
>> not able to say criteria which channels are possible to lock.
>>
>> Any hints are appreciated.
>
> I fixed an issue with cx88 sometime ago where a value of 0 (taken from
> the cards struct) was being written to the GPIO register, resulting in
> the same i2c issues.
>
> It looks a lot like this.
>
> - Steve

I am trying to get the dvb-t tuner working with my hvr-4000 (dvb-s is 
working fine) and have tried both the latest S2 repository and the latest 
version of liplianins multiproto repository with 2.6.26 kernels.

It seems that S2 repository does not yet support DVB-T at all, am I 
correct?  At least the "options cx88-dvb frontend=1" option in 
/etc/modprope.conf prevents adapters to be created at all under
/dev/dvb. Without that option adapter is created but it can only be used 
for scanning dvb-s.

WIth liplianinis multiproto version the selection between DVB-S and DVB-T 
works by using the "options cx88-dvb frontend=1" but I am seeing the i2c
errors described below.

Could you have any URL and changeset tag to patch in some repository where 
this I2C thing has been fixed?

Btw, I tested also the HVR-1300 and it seems to be working with S2 but 
scan (from dvb-apps trunk) is failing to find channels from some 
frequencies while things with external philips dvb-t work ok.
(-5 option for scan does not make any difference)

The message I am getting with scan is.:

...
0x0000 0x1111: pmt_pid 0x0105 YLE -- YLE PEILI (running)
0x0000 0x1131: pmt_pid 0x0107 YLE -- YLEN KLASSINEN (running)
0x0000 0x1151: pmt_pid 0x0109 YLE -- YLEMONDO (running)
Network Name 'Digita Finland'
>>> tune to: 
602000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 
602000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 
(tuning failed)
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010

Mika

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Steven Toth]

Mika Laitio wrote:
>>> - the firmware is loaded into the card at first time the card is 
>>> opened - it
>>> is okay?
>>>
>>> [  917.660620] cx24116_firmware_ondemand: Waiting for firmware upload
>>> (dvb-fe-cx24116.fw)...
>>> [  917.703010] cx24116_firmware_ondemand: Waiting for firmware 
>>> upload(2)...
>>> [  922.703870] cx24116_load_firmware: FW version 1.22.82.0
>>> [  922.703889] cx24116_firmware_ondemand: Firmware upload complete
>>>
>>> The result is that only for some channels it is possible to get lock 
>>> with
>>> szap2. VDR is hanging (or starting) when trying to tune to initial 
>>> channel,
>>> even when this channel is set to channel at which is szap2 
>>> successfull. I'm
>>> not able to say criteria which channels are possible to lock.
>>>
>>> Any hints are appreciated.
>>
>> I fixed an issue with cx88 sometime ago where a value of 0 (taken from
>> the cards struct) was being written to the GPIO register, resulting in
>> the same i2c issues.
>>
>> It looks a lot like this.
>>
>> - Steve
> 
> I am trying to get the dvb-t tuner working with my hvr-4000 (dvb-s is 
> working fine) and have tried both the latest S2 repository and the 
> latest version of liplianins multiproto repository with 2.6.26 kernels.
> 
> It seems that S2 repository does not yet support DVB-T at all, am I 
> correct?  At least the "options cx88-dvb frontend=1" option in 
> /etc/modprope.conf prevents adapters to be created at all under
> /dev/dvb. Without that option adapter is created but it can only be used 
> for scanning dvb-s.

The ~stoth/hg/s2 has no DVB-T support on the HVR4000 yet. Those patches 
will appear very shortly in ~stoth/hg/s2-mfe.

> 
> WIth liplianinis multiproto version the selection between DVB-S and 
> DVB-T works by using the "options cx88-dvb frontend=1" but I am seeing 
> the i2c
> errors described below.
> 
> Could you have any URL and changeset tag to patch in some repository 
> where this I2C thing has been fixed?

I'm speculating that your issue is the same issue I fixed sometime ago 
(2-3 months in the master repo). I'd suggest you wait for the 
~stoth/hg/s2-mfe patches to appear later tonight and test again.

That tree (and ~stoth/hg/s2 for that matter) have the i2c fix I'm 
referring to.

- Steve

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Mika Laitio]

> The ~stoth/hg/s2 has no DVB-T support on the HVR4000 yet. Those patches will 
> appear very shortly in ~stoth/hg/s2-mfe.

Thanks,

I build and installed drivers from s2-mfe branch and now atleast the dvb-t 
and dvb-s scan were working both for hvr-1300 and hvr-4000.
With hvr-4000, the scan worked with
"./scan -a 1 -f 1 "... parameters.

>>  WIth liplianinis multiproto version the selection between DVB-S and DVB-T
>>  works by using the "options cx88-dvb frontend=1" but I am seeing the i2c
>>  errors described below.
>>
>>  Could you have any URL and changeset tag to patch in some repository where
>>  this I2C thing has been fixed?
>
> I'm speculating that your issue is the same issue I fixed sometime ago (2-3 
> months in the master repo). I'd suggest you wait for the 
> ~ stoth/hg/s2-mfe patches to appear later tonight and test again.
>
> That tree (and ~stoth/hg/s2 for that matter) have the i2c fix I'm referring 
> to.

I tried to find the fix by checking from the log your commits for cx88 
couple of months ago and could not find the one you were referring.
Then I remembered that in 2.6.25 kernel, similar errors for HVR-1300 could 
be fixed by defining the radio information for the board structure.

So I tried the same trick also for hvr-4000, and that made dvb-t working 
without I2C errors also for HVR4000. ( with liplianis version of 
multiproto tree.)

--- cx88-cards.c_old	2008-09-25 00:51:18.000000000 +0300
+++ cx88-cards.c	2008-09-24 10:44:15.000000000 +0300
@@ -1480,6 +1480,10 @@
  		}},
  		/* fixme: Add radio support */
  		.mpeg           = CX88_MPEG_DVB,
+		.radio = {
+			.type   = CX88_RADIO,
+			.gpio0	= 0xe780,
+		},
  	},
  	[CX88_BOARD_HAUPPAUGE_HVR4000LITE] = {
  		.name           = "Hauppauge WinTV-HVR4000(Lite) 
DVB-S/S2",

In S2 and S2-mfe, the dvb-t worked even without radio data defined for 
hvr-4000.

Other non-API related changes that I could found between multiproto and s2 
trees for CX88 were pretty small. Is this udelay really needed?

@@ -2594,8 +2598,9 @@
  		break;
  	case CX88_BOARD_HAUPPAUGE_HVR3000: /* ? */
  	case CX88_BOARD_HAUPPAUGE_HVR4000:
-		/* Init GPIO for DVB-S/S2/Analog */
-		cx_write(MO_GP0_IO,core->board.input[0].gpio0);
+		/* Init GPIO */
+		cx_write(MO_GP0_IO, core->board.input[0].gpio0);
+		udelay(1000);
  		break;

  	case CX88_BOARD_PROLINK_PV_8000GT:
@@ -2939,6 +2944,7 @@
  		cx88_card_list(core, pci);
  	}

+	memset(&core->board, 0, sizeof(core->board));
  	memcpy(&core->board, &cx88_boards[core->boardnr], 
sizeof(core->board));

  	info_printk(core, "subsystem: %04x:%04x, board: %s 
[card=%d,%s]\n",

Those did not help

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Steven Toth]

Mika Laitio wrote:
>> The ~stoth/hg/s2 has no DVB-T support on the HVR4000 yet. Those 
>> patches will appear very shortly in ~stoth/hg/s2-mfe.
> 
> Thanks,
> 
> I build and installed drivers from s2-mfe branch and now atleast the 
> dvb-t and dvb-s scan were working both for hvr-1300 and hvr-4000.
> With hvr-4000, the scan worked with
> "./scan -a 1 -f 1 "... parameters.
> 
>>>  WIth liplianinis multiproto version the selection between DVB-S and 
>>> DVB-T
>>>  works by using the "options cx88-dvb frontend=1" but I am seeing the 
>>> i2c
>>>  errors described below.
>>>
>>>  Could you have any URL and changeset tag to patch in some repository 
>>> where
>>>  this I2C thing has been fixed?
>>
>> I'm speculating that your issue is the same issue I fixed sometime ago 
>> (2-3 months in the master repo). I'd suggest you wait for the ~ 
>> stoth/hg/s2-mfe patches to appear later tonight and test again.
>>
>> That tree (and ~stoth/hg/s2 for that matter) have the i2c fix I'm 
>> referring to.
> 
> I tried to find the fix by checking from the log your commits for cx88 
> couple of months ago and could not find the one you were referring.
> Then I remembered that in 2.6.25 kernel, similar errors for HVR-1300 
> could be fixed by defining the radio information for the board structure.
> 
> So I tried the same trick also for hvr-4000, and that made dvb-t working 
> without I2C errors also for HVR4000. ( with liplianis version of 
> multiproto tree.)
> 
> --- cx88-cards.c_old    2008-09-25 00:51:18.000000000 +0300
> +++ cx88-cards.c    2008-09-24 10:44:15.000000000 +0300
> @@ -1480,6 +1480,10 @@
>          }},
>          /* fixme: Add radio support */
>          .mpeg           = CX88_MPEG_DVB,
> +        .radio = {
> +            .type   = CX88_RADIO,
> +            .gpio0    = 0xe780,
> +        },
>      },
>      [CX88_BOARD_HAUPPAUGE_HVR4000LITE] = {
>          .name           = "Hauppauge WinTV-HVR4000(Lite) DVB-S/S2",
> 
> In S2 and S2-mfe, the dvb-t worked even without radio data defined for 
> hvr-4000.
> 
> Other non-API related changes that I could found between multiproto and 
> s2 trees for CX88 were pretty small. Is this udelay really needed?
> 
> @@ -2594,8 +2598,9 @@
>          break;
>      case CX88_BOARD_HAUPPAUGE_HVR3000: /* ? */
>      case CX88_BOARD_HAUPPAUGE_HVR4000:
> -        /* Init GPIO for DVB-S/S2/Analog */
> -        cx_write(MO_GP0_IO,core->board.input[0].gpio0);
> +        /* Init GPIO */
> +        cx_write(MO_GP0_IO, core->board.input[0].gpio0);
> +        udelay(1000);
>          break;
> 
>      case CX88_BOARD_PROLINK_PV_8000GT:
> @@ -2939,6 +2944,7 @@
>          cx88_card_list(core, pci);
>      }
> 
> +    memset(&core->board, 0, sizeof(core->board));
>      memcpy(&core->board, &cx88_boards[core->boardnr], 
> sizeof(core->board));
> 
>      info_printk(core, "subsystem: %04x:%04x, board: %s [card=%d,%s]\n",
> 
> Those did not help

Thanks.

I'm going to rebase the s2-mfe tree from master (containing the s2api). 
Darron also has a i2c related fix (which isn't perfect) but does address 
an issue like this.

I'll rebase and push both of those patches into ~stoth/s2-mfe, if you 
can retest after this then that would be useful.

Watch for changes to this tree tonight, it may help.

Regards,

- Steve

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR-4000 driver problems - i2c error

[Darron Broad]

In message <48DAD9C2.2050007@linuxtv.org>, Steven Toth wrote:

hi.

>Mika Laitio wrote:
>>> The ~stoth/hg/s2 has no DVB-T support on the HVR4000 yet. Those 
>>> patches will appear very shortly in ~stoth/hg/s2-mfe.
>> 
>> Thanks,
>> 
>> I build and installed drivers from s2-mfe branch and now atleast the 
>> dvb-t and dvb-s scan were working both for hvr-1300 and hvr-4000.
>> With hvr-4000, the scan worked with
>> "./scan -a 1 -f 1 "... parameters.

>>>>  WIth liplianinis multiproto version the selection between DVB-S and 
>>>> DVB-T
>>>>  works by using the "options cx88-dvb frontend=1" but I am seeing the 
>>>> i2c
>>>>  errors described below.

This was an option added to the SFE driver which has now
become obsolete. A new patch for this can be created easily
enough though. The i2c errors you are probably reporting
here have also been fixed in MFE (see below). 

>>>>  Could you have any URL and changeset tag to patch in some repository 
>>>> where
>>>>  this I2C thing has been fixed?
>>>
>>> I'm speculating that your issue is the same issue I fixed sometime ago 
>>> (2-3 months in the master repo). I'd suggest you wait for the ~ 
>>> stoth/hg/s2-mfe patches to appear later tonight and test again.
>>>
>>> That tree (and ~stoth/hg/s2 for that matter) have the i2c fix I'm 
>>> referring to.
>> 
>> I tried to find the fix by checking from the log your commits for cx88 
>> couple of months ago and could not find the one you were referring.
>> Then I remembered that in 2.6.25 kernel, similar errors for HVR-1300 
>> could be fixed by defining the radio information for the board structure.
>> 
>> So I tried the same trick also for hvr-4000, and that made dvb-t working 
>> without I2C errors also for HVR4000. ( with liplianis version of 
>> multiproto tree.)
>> 
>> --- cx88-cards.c_old    2008-09-25 00:51:18.000000000 +0300
>> +++ cx88-cards.c    2008-09-24 10:44:15.000000000 +0300
>> @@ -1480,6 +1480,10 @@
>>          }},
>>          /* fixme: Add radio support */
>>          .mpeg           = CX88_MPEG_DVB,
>> +        .radio = {
>> +            .type   = CX88_RADIO,
>> +            .gpio0    = 0xe780,
>> +        },

I put this is the patch also. Radio doesn't work though. There is
not enough information as to how to fix it as yet.

>>      [CX88_BOARD_HAUPPAUGE_HVR4000LITE] = {
>>          .name           = "Hauppauge WinTV-HVR4000(Lite) DVB-S/S2",
>> 
>> In S2 and S2-mfe, the dvb-t worked even without radio data defined for 
>> hvr-4000.
>> 
>> Other non-API related changes that I could found between multiproto and 
>> s2 trees for CX88 were pretty small. Is this udelay really needed?
>> 
>> @@ -2594,8 +2598,9 @@
>>          break;
>>      case CX88_BOARD_HAUPPAUGE_HVR3000: /* ? */

The above has been reverted for the hvr-3000.

>>      case CX88_BOARD_HAUPPAUGE_HVR4000:
>> -        /* Init GPIO for DVB-S/S2/Analog */
>> -        cx_write(MO_GP0_IO,core->board.input[0].gpio0);
>> +        /* Init GPIO */
>> +        cx_write(MO_GP0_IO, core->board.input[0].gpio0);
>> +        udelay(1000);
>>          break;
>> 
>>      case CX88_BOARD_PROLINK_PV_8000GT:
>> @@ -2939,6 +2944,7 @@
>>          cx88_card_list(core, pci);
>>      }
>> 
>> +    memset(&core->board, 0, sizeof(core->board));
>>      memcpy(&core->board, &cx88_boards[core->boardnr], 
>> sizeof(core->board));
>> 
>>      info_printk(core, "subsystem: %04x:%04x, board: %s [card=%d,%s]\n",
>> 
>> Those did not help
>
>Thanks.
>
>I'm going to rebase the s2-mfe tree from master (containing the s2api). 
>Darron also has a i2c related fix (which isn't perfect) but does address 
>an issue like this.

I am about to prepare a new patch-set for the above but in the meantime
you can look at this:
	http://dev.kewl.org/hauppauge/gate_control-8894.diff

This fixes some loading time i2c errors and also errors with
moving from DVB-T to analogue TV.

Other errors found which occur when moving from DVB-S to DVB-T
are work in progress and will be fixed later.

>I'll rebase and push both of those patches into ~stoth/s2-mfe, if you 
>can retest after this then that would be useful.
>
>Watch for changes to this tree tonight, it may help.

cya!

--

 // /
{:)==={ Darron Broad <darron@kewl.org>
 \\ \ 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb