It is currently Sat, 24 Oct 2020 08:19:50 GMT



 
Author Message
 Problems with i2c-matroxfb and latest kernel
On 19 Apr 01 at 20:31, German Gomez Garcia wrote:

Hi German,
  try it without connected monitor. It looks to me like that
DDC's SDA and SCL pins are connected to ground in your monitor
and/or your monitor cable. If they are stuck, it takes very long
before i2c code gives up (1s timeout; BTW, there is a bug,
adap->timeout in i2c_bit_add_bus should be set to HZ and not to 100,
if it is doing what I think it does... besides that I thought that
it is caller responsibility to set timeout).

  You should compile i2c-algo-bit as module and use insmod it
with 'bit_test=1' parameter. It should do some tests on these pins
to find whether they are stuck in 0 or in 1. You can also try
'i2c_debug=3' ...

  And last question - which matrox hardware do you have?
                                                    Thanks,
                                                        Petr Vandrovec
                                                        vandr...@vc.cvut.cz

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at   http://www.**-**.com/
Please read the FAQ at   http://www.**-**.com/



 Wed, 08 Oct 2003 00:10:09 GMT   
 
   [ 1 post ] 

Similar Threads

1. Problems with i2c-matroxfb and latest kernel

2. Problems with i2c-matroxfb and latest kernel

3. [I2C] fix unsafe usage of list_for_each in i2c-core

4. i2c #1/3: listify i2c core

5. 2.5.36 i2c new adapter i2c-pport driver

6. Four new i2c drivers and __init/__exit cleanup to i2c

7. Four new i2c drivers and __init/__exit cleanup to i2c

8. Four new i2c drivers and __init/__exit cleanup to i2c

9. Four new i2c drivers and __init/__exit cleanup to i2c

10. Four new i2c drivers and __init/__exit cleanup to i2c


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software