From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: I2C standalone vs integrated?
Date: Thu, 16 Oct 2003 12:14:34 +0200 [thread overview]
Message-ID: <1066299274.644.130.camel@gaston> (raw)
In-Reply-To: <20031016004349.71177.qmail@web14908.mail.yahoo.com>
> Also, I2C drivers for Intel810, Savage, Voodoo, etc are implemented as
> standalone I2C drivers. Ben implemented his and Matrox as an integral part of
> the fb driver. Wouldn't it be better to implement these all standalone? It's
> probably the same amount of code, and I can use the standalone ones from Mesa
> without loading framebuffer support.
(Note: I didn't do the Matrox part)
Regarding the standalone, I'm not too sure about it. I even though about
not using the linux i2c layer at all, it's not very convenient, and we
need to wrap the i2c accesses in all sort of tweaks to make DDC work
properly in all cases (all the stuff in radeon_probe_i2c_connector()
typically).
I'd rather see things built on top of framebuffer drivers (fbcon staying
something separate).
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-16 10:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 19:18 ioremap problem on highmem Otto Solares
2003-10-13 20:30 ` Jon Smirl
2003-10-14 0:14 ` Otto Solares
2003-10-14 0:46 ` Jon Smirl
2003-10-14 1:56 ` Otto Solares
2003-10-14 4:51 ` Jon Smirl
2003-10-15 1:13 ` Otto Solares
2003-10-15 1:37 ` Jon Smirl
2003-10-15 23:11 ` James Simmons
2003-10-16 10:15 ` Benjamin Herrenschmidt
2003-10-16 16:56 ` Otto Solares
2003-10-17 16:58 ` James Simmons
2003-10-14 8:30 ` Geert Uytterhoeven
2003-10-14 8:34 ` Geert Uytterhoeven
2003-10-14 14:42 ` Jon Smirl
2003-10-14 17:25 ` James Simmons
2003-10-14 17:23 ` James Simmons
2003-10-14 16:49 ` James Simmons
2003-10-14 17:59 ` Jon Smirl
2003-10-15 23:17 ` James Simmons
2003-10-16 0:34 ` Jon Smirl
2003-10-16 10:12 ` Benjamin Herrenschmidt
2003-10-16 0:43 ` I2C standalone vs integrated? Jon Smirl
2003-10-16 10:14 ` Benjamin Herrenschmidt [this message]
2003-10-17 16:43 ` James Simmons
2003-10-16 10:09 ` ioremap problem on highmem Benjamin Herrenschmidt
2003-10-15 16:46 ` Benjamin Herrenschmidt
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=1066299274.644.130.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).