Hi, On Mon, May 3, 2010 at 4:32 PM, Dr. H. Nikolaus Schaller <h...@computer.org>wrote:
> After more and more experimenting I now tried this config: > > $ fgrep I2C kernel/.config > CONFIG_I2C=y > CONFIG_I2C_BOARDINFO=y > CONFIG_I2C_CHARDEV=m > # I2C Algorithms > # CONFIG_I2C_ALGOBIT is not set > # CONFIG_I2C_ALGOPCF is not set > # CONFIG_I2C_ALGOPCA is not set > # I2C Hardware Bus support > # CONFIG_I2C_OCORES is not set > # CONFIG_I2C_PARPORT_LIGHT is not set > # CONFIG_I2C_SIMTEC is not set > # CONFIG_I2C_TAOS_EVM is not set > # CONFIG_I2C_STUB is not set > # CONFIG_I2C_TINY_USB is not set > # Miscellaneous I2C Chip support > CONFIG_I2C_DEBUG_CORE=y > CONFIG_I2C_DEBUG_ALGO=y > CONFIG_I2C_DEBUG_BUS=y > CONFIG_I2C_DEBUG_CHIP=y > > There is no I2C algoritm enabled and no Hardware Bus support. > With that the only i2c related messages I see in dmesg: > > i2c-core: driver [pcf8563] registered > i2c-core: driver [pcf8583] registered > > and the > > Write I2C device 0x13 failed. > > Finally, > > /sys/bus/i2c/devices > > exists but is completely empty. > > Finally, i2cdump reports: > > Error: No I2C busses found! > > So I now think that the I2C chip driver is not working or not enabled. > > Does anyone know where to look for this? How does the JZ4730 I2C interface > work? Do we need to do some board-configuration for > initialization/registration > Apparently the 2.4 kernel is setup up quite differently. the only RTC line I see is (verbatim): PCF8563 RTC installed !!! there are no i2c or I2C lines in dmesg, only I2S is mentioned, which is for sound and not clocks :) Riccardo
_______________________________________________ Mipsbook-devel mailing list Mipsbook-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
