I will try it later on (your suggested modification), as I really do need v2.8.0 of i2c, because in 2.7.0 my motherboard is not properly supported and sometimes the fans stop during prolonged high CPU load or system freezes..... which is obviously not very good for your CPU, unless you're planning to cook a steak on it.
On Sun, 2003-06-29 at 04:53, Ronald Bultje wrote:
> Well, yes, but I think it's the same version that is currently in 2.5.x.
> I don't know of a quick way to detect it from the top of my head.
> i2c-2.8.0 changes the API/ABI of the i2c modules, and so our driver no
> longer compiles.
>
> For now, I'd recommend to simply use i2c-2.7.0. I can try some #ifdef
> voodoo when I find time, that will make i2c-2.8.0 work too, I suppose,
> but I can't give a solution right from here. ;). You could also try it
> manually: in each of the files that gives this compile error, at the
> bottom, you'll find lines like this:
> --
> static struct i2c_driver i2c_driver_saa7111 = {
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,5,0)
> .owner = THIS_MODULE,
> #endif
> .name = "saa7111",
>
> .id = I2C_DRIVERID_SAA7111A,
> .flags = I2C_DF_NOTIFY,
>
> .attach_adapter = saa7111_attach_adapter,
> .detach_client = saa7111_detach_client,
> .command = saa7111_command,
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0)
> .inc_use = saa7111_inc_use,
> .dec_use = saa7111_dec_use,
> #endif
> };
> --
> "saa7111" is the name of the driver, which is different for each file.
> Simply change the "#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0)" here
> into "#if I2C_VERSION == "2.8.0"" or something similar, and see if it
> compiles now. If it doesn't, just wait for a while until I've fixed it.
> ;).
>
signature.asc
Description: This is a digitally signed message part
