summaryrefslogtreecommitdiff
path: root/drivers/video/savage
diff options
context:
space:
mode:
authorJean Delvare <khali@linux-fr.org>2006-01-09 20:52:59 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2006-01-10 08:01:44 -0800
commitc35dba601728412f67801792107d3dddd1f3ada1 (patch)
tree8fe67ba50d8bbb78d2e161b90be3c4c223c37c72 /drivers/video/savage
parentf3e21169b84a80b35d81a2b9fd97eb0b7d73d3f9 (diff)
[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 <khali@linux-fr.org> Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/video/savage')
-rw-r--r--drivers/video/savage/savagefb-i2c.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/video/savage/savagefb-i2c.c b/drivers/video/savage/savagefb-i2c.c
index 3c98457783c4..aeec437104eb 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;