From: Jean Delvare Date: Tue, 10 Jan 2006 04:52:59 +0000 (-0800) Subject: [PATCH] savagefb: One more I2C-enabled device in savagefb X-Git-Tag: v2.6.16-rc1~558 X-Git-Url: http://pilppa.com/gitweb/?a=commitdiff_plain;h=c35dba601728412f67801792107d3dddd1f3ada1;p=linux-2.6-omap-h63xx.git [PATCH] savagefb: One more I2C-enabled device in savagefb 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 Signed-off-by: Linus Torvalds --- diff --git a/drivers/video/savage/savagefb-i2c.c b/drivers/video/savage/savagefb-i2c.c index 3c98457783c..aeec437104e 100644 --- a/drivers/video/savage/savagefb-i2c.c +++ b/drivers/video/savage/savagefb-i2c.c @@ -193,6 +193,7 @@ void savagefb_create_i2c_busses(struct fb_info *info) 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;