Re: 2.5.66: The I2C code ate my grandma...

• Next message: Greg KH: "Re: [PATCH] convert via686a i2c driver to sysfs"
• Previous message: Jean Tourrilhes: "Re: uart_ioctl OOPS with irtty-sir"
• In reply to: CaT: "2.5.66: The I2C code ate my grandma..."
• Next in thread: CaT: "Re: 2.5.66: The I2C code ate my grandma..."
• Reply: CaT: "Re: 2.5.66: The I2C code ate my grandma..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Apr 04, 2003 at 12:11:52PM +1000, CaT wrote:
>
> I2C components that were compiled in:
>
> -CONFIG_I2C=y
> -CONFIG_I2C_CHARDEV=y
> -CONFIG_I2C_PIIX4=y
> -CONFIG_I2C_PROC=y
> -CONFIG_SENSORS_ADM1021=y
>
> Please help. I like knowing what temp my cpu is at. :)

So if you disable the I2C config items, everything works just fine?

I did send out a bugfix for the i2c code for a problem in 2.5.66, it's
now included in the latest -bk tree. Could you grab that patch and see
if it fixes your problem?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Greg KH: "Re: [PATCH] convert via686a i2c driver to sysfs"
• Previous message: Jean Tourrilhes: "Re: uart_ioctl OOPS with irtty-sir"
• In reply to: CaT: "2.5.66: The I2C code ate my grandma..."
• Next in thread: CaT: "Re: 2.5.66: The I2C code ate my grandma..."
• Reply: CaT: "Re: 2.5.66: The I2C code ate my grandma..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Apr 07 2003 - 22:00:23 EST