linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Haffner <haffner@astro.wisc.edu>
To: Tom Rini <trini@kernel.crashing.org>
Cc: atong@uiuc.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: XFree, E, and refresh rates...
Date: Tue, 16 Nov 1999 15:36:26 -0600	[thread overview]
Message-ID: <3831CE5A.DE7F3566@astro.wisc.edu> (raw)
In-Reply-To: Pine.LNX.4.10.9911161408530.3875-100000@opus.bloom.county


Tom Rini wrote:
> 
> On Tue, 16 Nov 1999, Matt Haffner wrote:
> 
> > I was curious if any of you had seen my posting on the users list a bit
> > ago about problems that cropped up with Enlightenment 0.16 related to
> > monitor refresh rates (B&W/400). There are two minor issues on this
> > topic.
> 
> E 0.16.2 & anthonys FBDev seem happy here..

OK... I'll have to try out 16.2. I've got 16.1 installed right now.
Odd...

> > There seems to be a general problem (at least on my system... I haven't
> > seen corroboration yet) that XFree chooses the _lowest_ vertical refresh
> > modeline instead of the highest one supported by the monitor. I have
> > lines like
> 
> It takes the 1st one that fits, iirc.

Ahhhh... Thanks. I see my misunderstanding with this now. In the
XF86Config file, there's a statement: 
                                  vvvv
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.

I had interpreted that to mean best refresh rate (and thought I read
that elsewhere too). But checking the man page it says it takes the
first valid one. 

Is it possible then for XConfigurator spit out the modelines in reverse
order from what it does now? It looks like it's in order of increasing
hsync right now, but maybe decreasing hsync or vrefresh would be better?
That way we get the highest refresh rate right out of the box. Totally
trival though :)

Thanks again...

mh
--
Matt Haffner                      /|------|\    University of Wisconsin
Dept. of Astronomy               /|--------|\            Madison
haffner@astro.wisc.edu          /|----------|\  
           WHAM project -- http://www.astro.wisc.edu/wham

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-11-16 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.9911151747090.699-100000@opus.bloom.county>
1999-11-16 18:18 ` XFree, E, and refresh rates Matt Haffner
1999-11-16 21:10   ` Tom Rini
1999-11-16 21:36     ` Matt Haffner [this message]
1999-11-16 21:52       ` Tom Rini

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=3831CE5A.DE7F3566@astro.wisc.edu \
    --to=haffner@astro.wisc.edu \
    --cc=atong@uiuc.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    /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).