From: Kronos <kronos@kronoz.cjb.net>
To: Andrew Morton <akpm@osdl.org>
Cc: James Simmons <jsimmons@infradead.org>,
benh@kernel.crashing.org, geert@linux-m68k.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH] Fix get_std_timing
Date: Thu, 11 Mar 2004 19:29:48 +0100 [thread overview]
Message-ID: <20040311182948.GA4658@dreamland.darkstar.lan> (raw)
In-Reply-To: <20040311101334.414624d1.akpm@osdl.org>
Il Thu, Mar 11, 2004 at 10:13:34AM -0800, Andrew Morton ha scritto:
> James Simmons <jsimmons@infradead.org> wrote:
> >
> >
> > Various fixes and enhancements to the monitor hardware detection code.
> > The only driver that uses it is the radeon driver. Give it a try before
> > you apply it.
>
> None of my test boxes have radeon. Your comment makes me worry about the
> readiness of this code. Please say reassuring things to me ;)
Old EDID parsing code was very verbose, half of the patch address this
(ie. print lots of stuff iff DEBUG). The other big change is the
FB_MODE_IS_* stuff: we really need a way to know the origin of a video
mode. In this way we can select video mode that comes from EDID instead
of VESA or GTF.
Drivers other than radeonfb won't be affected because they cannot (yet)
get EDID from the monitor and don't use EDID related code.
Luca
--
Home: http://kronoz.cjb.net
This message will self distruct in 5 seconds.
-------------------------------------------------------
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-11 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 22:15 [PATCH] Fix get_std_timing Kronos
2004-03-04 22:31 ` James Simmons
2004-03-05 2:37 ` Benjamin Herrenschmidt
2004-03-11 17:43 ` James Simmons
2004-03-11 17:50 ` Andrew Morton
2004-03-11 18:06 ` James Simmons
2004-03-11 18:13 ` Andrew Morton
2004-03-11 18:20 ` James Simmons
2004-03-11 22:49 ` Benjamin Herrenschmidt
2004-03-11 23:31 ` James Simmons
2004-03-12 23:46 ` character drawing enhancement James Simmons
2004-03-11 18:23 ` Re: [PATCH] Fix get_std_timing James Simmons
2004-03-11 22:48 ` Benjamin Herrenschmidt
2004-03-11 23:26 ` James Simmons
2004-03-11 18:29 ` Kronos [this message]
2004-03-11 19:32 ` James Simmons
2004-03-11 22:46 ` Benjamin Herrenschmidt
2004-03-11 23:32 ` James Simmons
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=20040311182948.GA4658@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--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).