All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Alessio Sangalli <alesan-+h0hele9I7BBDgjK7y7TUQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Implementing a new driver
Date: Sat, 24 Jan 2009 09:58:21 +0100	[thread overview]
Message-ID: <20090124095821.316b05ff@hyperion.delvare> (raw)
In-Reply-To: <497A3820.2060405-+h0hele9I7BBDgjK7y7TUQ@public.gmane.org>

Hi Alessio,

On Fri, 23 Jan 2009 13:35:28 -0800, Alessio Sangalli wrote:
> Jean Delvare wrote:
> 
> > Examples of I2C chip drivers can be found under drivers/rtc (for RTC
> 
> 
> Thanks. I guess there is already a driver for DDC/EDID monitor
> parameters right? Should be a fairly common feature for graphic cards

See drivers/video/fb_ddc.c and drivers/video/edid.h, presumably this is
what you want for a framebuffer driver. For an X driver, the code
handling DDC is in X itself.

Or, for testing purpose, you can use the legacy "eeprom" driver
together with the ddcmon and decode-edid scripts from i2c-tools [1].

[1] http://www.lm-sensors.org/wiki/I2CTools

-- 
Jean Delvare

      parent reply	other threads:[~2009-01-24  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  9:28 Implementing a new driver Alessio Sangalli
     [not found] ` <49798DAD.1070100-+h0hele9I7BBDgjK7y7TUQ@public.gmane.org>
2009-01-23  9:39   ` Jean Delvare
     [not found]     ` <20090123103909.281770dd-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-23 17:31       ` Alessio Sangalli
     [not found]         ` <4979FEF2.1090006-+h0hele9I7BBDgjK7y7TUQ@public.gmane.org>
2009-01-23 20:25           ` Jean Delvare
     [not found]             ` <20090123212506.7997e4ee-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-23 21:35               ` Alessio Sangalli
     [not found]                 ` <497A3820.2060405-+h0hele9I7BBDgjK7y7TUQ@public.gmane.org>
2009-01-24  8:58                   ` Jean Delvare [this message]

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=20090124095821.316b05ff@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=alesan-+h0hele9I7BBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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.