All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "Antonino A. Daplas" <adaplas@pol.net>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH 2.6] fb: One more I2C-enabled device in savagefb
Date: Sat, 22 Oct 2005 17:22:56 +0200	[thread overview]
Message-ID: <20051022172256.34eedc1d.khali@linux-fr.org> (raw)

Hi Antonino, all,

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>
CC: Antonino A. Daplas <adaplas@pol.net>

---
 drivers/video/savage/savagefb-i2c.c |    1 +
 1 file changed, 1 insertion(+)

--- linux-2.6.14-rc4.orig/drivers/video/savage/savagefb-i2c.c	2005-10-22 16:42:00.000000000 +0200
+++ linux-2.6.14-rc4/drivers/video/savage/savagefb-i2c.c	2005-10-22 16:43:12.000000000 +0200
@@ -193,6 +193,7 @@
 		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;

-- 
Jean Delvare


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

                 reply	other threads:[~2005-10-22 16:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051022172256.34eedc1d.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.