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: 21 Aug 2003 23:10:46 +0200 [thread overview]
Message-ID: <1061500246.18043.15.camel@gaston> (raw)
In-Reply-To: <20030821205110.89821.qmail@web14912.mail.yahoo.com>
On Thu, 2003-08-21 at 22:51, Jon Smirl wrote:
> Is GregKH designing the EDID thorough sysfs scheme? I haven't seen a proposal
> on how it is going to work. We need to coordinate with that so that we don't
> end up with a different EDID scheme for every card.
Imho, the fbdev should be a separate device from the monitor:
fbdev -> fbmon -> EDID
The EDID should be a property of the monitor
So fbdev should instanciate a monitor object for each head after
detection. It's still unclear for me how to deal with the various
types of monitors though
- EDID available
- Mac old style "sense code" available
- fixed mode known based on motherboard (old mac laptops among others,
probably some embedded)
- unknown
The EDID shall be used to build a modedb of available modes for this
display, the driver doing validation based on that, though a flag to
set_var would still be useful to force a mode that doesn't pass
validation (EDIDs can be wrong...)
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
next prev parent reply other threads:[~2003-08-22 7:11 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 [this message]
2003-08-21 21:21 ` Jon Smirl
2003-08-22 7:33 ` 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=1061500246.18043.15.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).