dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16402] drm: refresh rate down to 60 Hz in 2.6.35-rc5
Date: Thu, 15 Jul 2010 18:41:41 GMT	[thread overview]
Message-ID: <201007151841.o6FIffnL006928@demeter.kernel.org> (raw)
In-Reply-To: <bug-16402-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16402


Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com




--- Comment #1 from Alex Deucher <alexdeucher@gmail.com>  2010-07-15 18:41:36 ---
I'm not sure I'd call this a regression.  It brings the behavior into
compliance with the vesa spec.  I'd wager the TFT's actual preferred mode is 60
hz.  Most TFTs run at 60 hz.  The 75 hz modes are mostly there for
compatibility.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--

  parent reply	other threads:[~2010-07-15 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 18:01 [Bug 16402] New: drm: refresh rate down to 60 Hz in 2.6.35-rc5 bugzilla-daemon
2010-07-15 18:02 ` [Bug 16402] " bugzilla-daemon
2010-07-15 18:41 ` bugzilla-daemon [this message]
2010-07-16  7:03 ` bugzilla-daemon
2010-07-17 12:45 ` bugzilla-daemon
2010-07-18 22:37 ` bugzilla-daemon
2010-07-18 22:39 ` bugzilla-daemon

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=201007151841.o6FIffnL006928@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-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