From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: kronos@kronoz.cjb.net,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: Re: EDID for radeonfb
Date: 22 Aug 2003 09:33:22 +0200 [thread overview]
Message-ID: <1061537601.18043.35.camel@gaston> (raw)
In-Reply-To: <20030821212107.55742.qmail@web14915.mail.yahoo.com>
On Thu, 2003-08-21 at 23:21, Jon Smirl wrote:
> The list of modes supported by the board has to get worked into this too. Who
> should do the diff'ing to determine valid modes? The list of legal monitor
> modes might be from EDID or the fbmode database.
>
> Should sysfs have one entry for legal board modes and one for legal monitor
> modes? Or should it just have a single entry for legal combos?
Good point. Looking at what things like MacOS do, I'd say fbmon provides
a list to radeonfb, which filters it out and creates the "real" list.
I think it's not time to do a full blown fbmon layer now, we need more
experience with it and it's too late in the 2.6 process. I'll probably
just keep fbmon as a pool of "utility" functions and do most from
radeonfb (and aty128fb if I get a chance to port the i2c code) for now.
One thing I'm hesitating to do is to dive into a driver split &
rearchitecture now or not...
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
prev parent reply other threads:[~2003-08-22 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 22:33 EDID for radeonfb Kronos
2003-08-21 20:16 ` Benjamin Herrenschmidt
2003-08-21 20:39 ` Jon Smirl
2003-08-21 20:45 ` Benjamin Herrenschmidt
2003-08-21 20:51 ` Jon Smirl
2003-08-21 21:10 ` Benjamin Herrenschmidt
2003-08-21 21:21 ` Jon Smirl
2003-08-22 7:33 ` Benjamin Herrenschmidt [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=1061537601.18043.35.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.com \
--cc=jsimmons@infradead.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).