On Wed, Jul 16, 2003 at 04:04:43PM +1000, CaT wrote:
> On Tue, Jul 15, 2003 at 09:11:27AM -0700, Greg KH wrote:
> > On Tue, Jul 15, 2003 at 07:07:27PM +1000, CaT wrote:
> > So, if you don't have any i2c code loaded, everything works? How about
> > just loading the i2c driver and not the sensor driver?
> All's fine.
> > Oh, how about enabiling debugging in the i2c driver that you are using?
> Well this is what I did:
> 11 [15:53:38] root@theirongiant:/usr/src/linux/drivers/i2c>> grep 'define DEBUG' . -r
> ./i2c-core.c:#define DEBUG 1 /* needed to pick up the dev_dbg() calls */
> ./scx200_acb.c:#define DEBUG 0
> ./i2c-sensor.c:#define DEBUG 1
> ./i2c-algo-bit.c:/* #define DEBUG 1 */
> ./i2c-dev.c:#define DEBUG 1
> ./i2c-algo-pcf.c:/* #define DEBUG 1 */ /* to pick up dev_dbg calls */
> ./busses/i2c-amd756.c:/* #define DEBUG 1 */
> ./busses/i2c-ali15x3.c:/* #define DEBUG 1 */
> ./busses/i2c-i801.c:/* #define DEBUG 1 */
> ./busses/i2c-piix4.c:#define DEBUG 1
> ./busses/i2c-sis96x.c:/* #define DEBUG */
> ./busses/i2c-ali1535.c:/* #define DEBUG 1 */
> ./chips/adm1021.c:#define DEBUG 1
> ./chips/lm75.c:/* #define DEBUG 1 */
> Did I do the right thing?
Looks good, but are you _really_ building all of those drivers into your
kernel? Make them modules, that way booting will not require a small
Then load only the i2c bus driver that you have. See if that causes the
system to slow down, or cause any kernel log messages?
Only then try loading a i2c client driver, for your hardware.
Exactly what i2c hardware do you have anyway?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:23 EST