From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kronos <kronos@kronoz.cjb.net>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Remove voodoo code from i2c
Date: Sat, 06 Mar 2004 10:55:14 +1100 [thread overview]
Message-ID: <1078530914.5700.127.camel@gaston> (raw)
In-Reply-To: <20040305215210.GA23402@dreamland.darkstar.lan>
On Sat, 2004-03-06 at 08:52, Kronos wrote:
> Hi,
> radeon_probe_i2c_connector contains very strange code that just send
> empty start-stop sequencies on the I2C bus. I copied the code from
> XFree86, but speaking with I2C gurus the general feeling is that this
> code can go away without any harm. I tested it on 3 different setup (all
> x86...) and it works well. I don't have any "old" monitor around to
> fiddle with though.
>
> Oh, if you think that this code should stay I'll send you another patch
> to make it more readable.
I'd rather keep the code as close to XFree as possible at this point..
BTW... I'm still looking for an EDID spec if that exist ;)
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-06 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 21:52 [PATCH] Remove voodoo code from i2c Kronos
2004-03-05 23:55 ` Benjamin Herrenschmidt [this message]
2004-03-06 0:47 ` Kronos
2004-03-06 2:10 ` Jon Smirl
2004-03-06 3:42 ` Benjamin Herrenschmidt
2004-03-06 4:02 ` Jon Smirl
2004-03-06 15:08 ` Kronos
2004-03-08 22:17 ` Richard Smith
2004-03-08 22:56 ` Benjamin Herrenschmidt
2004-03-06 0:12 ` Michel Dänzer
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=1078530914.5700.127.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=kronos@kronoz.cjb.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 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).