From: Florian Lohoff <flo@rfc822.org>
To: ajoshi@kernel.crashing.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Radeonfb v/hsync polarity defaults
Date: Sun, 8 Feb 2004 21:07:47 +0100 [thread overview]
Message-ID: <20040208200747.GA1359@paradigm.rfc822.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
Hi,
i was just trying 2.6.2 on my Vaio C1MHP. It uses a RadeonM6 with a
1280x600 panel size. As on 2.4 it hs the same default problem of wrong
set v/hsync polarity. The radeonfb makes exactly the opposite
assumptions about default polarity as XFree does. I debugged this when
having the exact same problem on 2.4. I cooked the following patch
against a 2.4 version. This wrong polarity causes the display to shift
up by about 4-6 pixels which causes the top line to be unreadable while
at the bottom we have 4-6 unused rows.
I would like to see this fixed on 2.6 too so i am sending this again.
The patch does not apply to 2.6 as too much has changed but you get the
point.
--- radeonfb.c.orig Wed Apr 30 19:22:55 2003
+++ radeonfb.c Wed Apr 30 19:31:46 2003
@@ -1353,12 +1353,11 @@
var->hsync_len = rinfo->hSync_width;
var->vsync_len = rinfo->vSync_width;
var->sync = 0;
- if (rinfo->synct == 3) {
- if (rinfo->hAct_high)
- var->sync |= FB_SYNC_HOR_HIGH_ACT;
- if (rinfo->vAct_high)
- var->sync |= FB_SYNC_VERT_HIGH_ACT;
- }
+
+ if (rinfo->hAct_high)
+ var->sync |= FB_SYNC_HOR_HIGH_ACT;
+ if (rinfo->vAct_high)
+ var->sync |= FB_SYNC_VERT_HIGH_ACT;
var->vmode = 0;
if (rinfo->interlaced)
@@ -1404,6 +1403,11 @@
rinfo->vOver_plus = (readw(tmp0+28) & 0x7ff) - readw(tmp0+26);
rinfo->vSync_width = (readw(tmp0+28) & 0xf800) >> 11;
rinfo->clock = readw(tmp0+9);
+
+ /* We don't know that the H/V sync active level should be
+ make the same assumptions as XFree does - High Active */
+ rinfo->vAct_high=1;
+ rinfo->hAct_high=1;
rinfo->got_dfpinfo = 1;
return 1;
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-02-08 20:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040208200747.GA1359@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=ajoshi@kernel.crashing.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).