From: Otto Solares <solca@guug.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Merge of Luca and Ben's sysfs work for Radeon
Date: Thu, 25 Sep 2003 17:49:05 -0600 [thread overview]
Message-ID: <20030925234905.GC9615@guug.org> (raw)
In-Reply-To: <20030925203535.54019.qmail@web14909.mail.yahoo.com>
On Thu, Sep 25, 2003 at 01:35:35PM -0700, Jon Smirl wrote:
> R128 is more a problem. No one has written the code to get EDID info from the
> R128.
> There is a 2.4 R128 FB driver here: http://www.saftware.de/ that has I2C
> support.
>
> A good project would be to take code from that driver plus look at benh's new
> radeon driver and try to make a new 2.6 R128 driver that can read EDID. Once
> the driver can get to the EDID block it is easy to export it from sysfs.
> Radeons are very similar to R128's so benh's EDID code may just work on a R128.
>
> I have a merge between benh and kronos' Radeon work. I'm working on finding a
> place to keep it.
Ok. Thanks a lot.
-solca
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-25 23:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 6:05 Merge of Luca and Ben's sysfs work for Radeon Jon Smirl
2003-09-25 19:21 ` Otto Solares
2003-09-25 20:01 ` Kronos
2003-09-25 23:48 ` Otto Solares
2003-09-26 0:10 ` Jon Smirl
2003-09-26 2:36 ` Otto Solares
2003-09-26 2:57 ` Jon Smirl
2003-09-26 8:39 ` Otto Solares
[not found] ` <20030926171144.GA1380@dreamland.darkstar.lan>
2003-09-26 17:43 ` Otto Solares
2003-09-26 3:03 ` Jon Smirl
2003-09-26 17:51 ` Otto Solares
2003-09-25 20:35 ` Jon Smirl
2003-09-25 23:49 ` Otto Solares [this message]
2003-09-26 18:23 ` radeonfb work (WAS: Merge of Luca and Ben's sysfs work for Radeon) 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=20030925234905.GC9615@guug.org \
--to=solca@guug.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 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.