Allan Stirling wrote:
> Manu Abraham wrote:
>
>> Allan Stirling wrote:
>>
>>> Manu Abraham wrote:
>>>
>>>> You have i2c communication failures completely. What makes i2c
>>>> communications fail for you completely .. ?
>>>>
>>>> i2c communications is common for all cards .. Is it that you are
>>>> trying to an invalid frequency/polarity. That could be one of the
>>>> causes you can see those messages.. Other than that, i have never
>>>> seen communications fail so badly.. I all the cases it retries, but
>>>> in this case all the retries also fail ..
>>>>
>>>> Does doing a scan list channels for you ?
>>>>
>>>> Manu
>>>
>>>
>>> Apologies for the direct reply earlier.
>>>
>>> Applied all patches up to the polarization patch. At this point, I
>>> can no longer get a lock on H or V polarised signals. Up until this
>>> patch, only V channels worked.
>>>
>>> I'll try and have a closer look at this later.
>>>
>>> Cheers,
>>
>>
>>
>> Try the card in another PCI slot also ..
>>
>> Manu
>
> I'm pretty sure it's not the PCI slot.
>
> It's now working. I had to change:
>
> --- dst.c~ 2005-06-20 17:49:54.730668000 +0100
> +++ dst.c 2005-06-20 17:49:54.734668000 +0100
> @@ -325,12 +325,12 @@
> switch (state->voltage) {
> case SEC_VOLTAGE_13: // vertical
> printk("%s: Polarization=[Vertical]\n",
> __FUNCTION__);
> - state->tx_tuna[8] |= 0x40; //1
> + state->tx_tuna[8] =~ 0x40; //1
> break;
>
> case SEC_VOLTAGE_18: // horizontal
> printk("%s: Polarization=[Horizontal]\n",
> __FUNCTION__);
> - state->tx_tuna[8] =~ 0x40; // 0
> + state->tx_tuna[8] |= 0x40; // 0
> break;
>
> This is probably wrong, but it works for me. Scan now completes
This one is correct ... There was a bug indeed ..
Manu
