From: John Zielinski <grim@undead.cc>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fbcon & resize
Date: Sun, 23 May 2004 23:11:22 -0400 [thread overview]
Message-ID: <40B167DA.9090609@undead.cc> (raw)
In-Reply-To: <1085366682.24948.22.camel@gaston>
Benjamin Herrenschmidt wrote:
>Well, I'm getting complaints regulary when radeonfb refuses a mode
>(via set_var) that has out of range timings instead of picking a
>closer one. I'm not fully sure this is the right way to do though...
>
>
Out of range for the video card or the monitor? If it's the monitor
then provide a mechanism for updating the monitor information and that
solves that problem. I've seen monitors where the edid had "safe"
values while the tech specs for the monitor had a larger range.
If it's the hardware and we go the user customizable modedb route then
that would be part of the customization process. If a particular mode
didn't work then root can tweak the modelist so that it works on their
hardware. Regular users would then just be able to select from root's
customized list. As a bonus, regular users wouldn't be able to push the
monitor beyone the limits set by root.
John
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
prev parent reply other threads:[~2004-05-24 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 1:08 fbcon & resize Benjamin Herrenschmidt
2004-05-24 2:10 ` John Zielinski
2004-05-24 2:44 ` Benjamin Herrenschmidt
2004-05-24 3:11 ` John Zielinski [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=40B167DA.9090609@undead.cc \
--to=grim@undead.cc \
--cc=benh@kernel.crashing.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).