Re: 2.6.20 -> saa i2c messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Udo van den Heuvel wrote:
> Udo van den Heuvel wrote:
>   
>>> Take the original 2.6.20 driver and change the line above.
>>> No other modifications. Does the card still work?
>>>       
>> With this change undone the kernel boots OK.
>> I also have some saa7146_debug output with this change. Please let me
>> know if this output is interesting enough.
>>     
>
> With an unmodified kernel (.flags = SAA7146_USE_I2C_IRQ, in place) but
> with debugging I get:
>
>
>
>   
I try to interpret the debug output:

- Someone tries to access an i2c device on address 0x50..0x57
(0xa0..0xae). The transfer timed out. The interrupt was not hit.

- Someone tries to access an i2c device on address 0x50..0x57
(0xa0..0xae). For each transfer, the interrupt was hit. The transfer was
successful for the first address. There was no response (ACK) for the
other addresses.

The access to the i2c bus doesn't come from the dvb driver. You should
see a massage like 'budget-av:  A frontend driver was not found for
device xxxx/xxxx subsystem yyyy/yyyy', because one of the saa7146 didn't
got an interrupt.

- Hartmut


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

[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux