dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28146] New: typo in drm_edid.c drm_dmt_modes table
Date: Mon, 17 May 2010 10:06:39 -0700 (PDT)	[thread overview]
Message-ID: <bug-28146-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=28146

           Summary: typo in drm_edid.c drm_dmt_modes table
           Product: DRI
           Version: XOrg CVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/other
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: ssb@umn.edu


It has an extra 0 in the clock frequency for a 1600x1200 mode:

{ DRM_MODE("1600x1200", DRM_MODE_TYPE_DRIVER, 2025000, 1600, 1664,
           1856, 2160, 0, 1200, 1201, 1204, 1250, 0,
           DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },

Note clock specified as 2025000 rather than 202500.

Prevented xorg-server 1.8.0 from using this mode on a Dell D1226H I have under
kernel 2.6.32 (Gentoo/Sabayon).

Bug still shows up in git.kernel.org: linux-next.git.

Tried to find in freedesktop repository, but couldn't seem to figure out how to
get to it.  Should have read more, but hoping this isn't too inconvenient for
you folks - i.e. that it hasn't already been fixed on your side.

Thanks.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-05-17 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 17:06 bugzilla-daemon [this message]
2010-05-17 19:10 ` [Bug 28146] typo in drm_edid.c drm_dmt_modes table bugzilla-daemon
2010-05-19 15:51 ` bugzilla-daemon
2010-05-19 15:52 ` 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=bug-28146-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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