linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Engert <kai.engert@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: ajoshi@unixbox.com
Subject: Sync bit bug in drivers/video/radeonfb.c ?
Date: Tue, 30 Jul 2002 14:43:17 +0200	[thread overview]
Message-ID: <3D4689E5.5000504@gmx.de> (raw)

I suspect the line
         v_sync_pol = sync & FB_SYNC_VERT_HIGH_ACT ? 0 : 1;
is incorrect, and probably also line
         h_sync_pol = sync & FB_SYNC_HOR_HIGH_ACT ? 0 : 1;

If I use "fbset -vsync low" the uppermost line is only halfway displayed 
on my system. With "fbset -vsync high" the uppermost line is fully visible.

I'm using 2.4.19-rc3-ac4 which has an entry in drivers/video/modedb.c to 
support a 1280x600 screen resolution on Sony C1M*. That entry defines
   fb_videomode->sync = FB_SYNC_VERT_HIGH_ACT

However, after booting the top level line is not fully visible.
I have to correct that manually with "fbset -vsync high".

The patch below makes it work on boot.

Also note, the variables vSyncPol and hSyncPol use the same assignments, 
but seem to be unused, and should probably get removed.

Kai

PS: I'm not subscribed, please cc me on replys. Thanks.


--- bad/drivers/video/radeonfb.c        Tue Jul 30 14:38:29 2002
+++ good/drivers/video/radeonfb.c       Tue Jul 30 14:39:10 2002
@@ -2401,8 +2401,8 @@
         }

         sync = mode->sync;
-       h_sync_pol = sync & FB_SYNC_HOR_HIGH_ACT ? 0 : 1;
-       v_sync_pol = sync & FB_SYNC_VERT_HIGH_ACT ? 0 : 1;
+       h_sync_pol = sync & FB_SYNC_HOR_HIGH_ACT ? 1 : 0;
+       v_sync_pol = sync & FB_SYNC_VERT_HIGH_ACT ? 1 : 0;

         RTRACE("hStart = %d, hEnd = %d, hTotal = %d\n",
                 hSyncStart, hSyncEnd, hTotal);



             reply	other threads:[~2002-07-30 12:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 12:43 Kai Engert [this message]
2002-07-30 14:33 ` Sync bit bug in drivers/video/radeonfb.c ? James Mayer
2002-07-30 14:54   ` Kai Engert
2002-07-30 15:08     ` Russell King
2002-07-31 15:57     ` James Mayer

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=3D4689E5.5000504@gmx.de \
    --to=kai.engert@gmx.de \
    --cc=ajoshi@unixbox.com \
    --cc=linux-kernel@vger.kernel.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).