From: Jean Delvare The I2C bus of the S3 Savage2000 is supposed to work the same way the Savage4 does. At least, the legacy i2c-savage4 driver handled both devices the same way. I do not have the hardware to test this, so testers are welcome. Signed-off-by: Jean Delvare Signed-off-by: Antonino Daplas Signed-off-by: Andrew Morton --- drivers/video/savage/savagefb-i2c.c | 1 + 1 files changed, 1 insertion(+) diff -puN drivers/video/savage/savagefb-i2c.c~savagefb-one-more-i2c-enabled-device-in-savagefb drivers/video/savage/savagefb-i2c.c --- devel/drivers/video/savage/savagefb-i2c.c~savagefb-one-more-i2c-enabled-device-in-savagefb 2005-11-21 23:34:48.000000000 -0800 +++ devel-akpm/drivers/video/savage/savagefb-i2c.c 2005-11-21 23:34:48.000000000 -0800 @@ -193,6 +193,7 @@ void savagefb_create_i2c_busses(struct f par->chan.algo.getscl = prosavage_gpio_getscl; break; case FB_ACCEL_SAVAGE4: + case FB_ACCEL_SAVAGE2000: par->chan.reg = 0xff20; par->chan.ioaddr = par->mmio.vbase; par->chan.algo.setsda = savage4_gpio_setsda; _