From: Nicolas Boichat <nicolas@boichat.ch>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 9/10] i810fb: Add i2c/DDC support
Date: Sun, 04 Sep 2005 15:51:31 +0200 [thread overview]
Message-ID: <1125841891.7590.52.camel@tom> (raw)
In-Reply-To: <43177635.8020005@gmail.com>
Hello Antonino,
I have an information that may interest you: On i865G, you can connect
an AGP daughter card to add a DVI connector. The I2C bus of this
connector is accessed using the register that I called GPIO"C", and its
offset is 0x0501C (it is not documented in Intel datasheets). It works
exactly like the busses on GPIOA (0x05010) and GPIOB (0x05014), i.e. you
can reuse the same functions.
BTW, you could merge i810i2c_* and i810ddc_* functions, as they are the
same excepting the register address (you did this in rivafb).
Also note that your code to read/write to the I2C busses has been
reported to work on i915G (I don't know about the real framebuffer
support).
Best regards,
Nicolas
On Fri, 2005-09-02 at 05:44 +0800, Antonino A. Daplas wrote:
> Add ddc/i2c support for i810fb. This will allow the driver to
> get display information, especially for monitors with fickle timings.
> The i2c support depends on CONFIG_FB_I810_GTF.
>
> Changed __init* to __devinit*
>
> Signed-off-by: Antonino Daplas <adaplas@pol.net>
>
[snip]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-09-04 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 21:44 [PATCH 9/10] i810fb: Add i2c/DDC support Antonino A. Daplas
2005-09-04 13:51 ` Nicolas Boichat [this message]
2005-09-04 14:46 ` Antonino A. Daplas
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=1125841891.7590.52.camel@tom \
--to=nicolas@boichat.ch \
--cc=adaplas@gmail.com \
--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.