linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Kovalev <aka@pxe.ru>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: gx1fb problems.
Date: Thu, 17 Jan 2008 16:29:45 +0400	[thread overview]
Message-ID: <478F4A39.4070003@pxe.ru> (raw)

Hi all,

I have a problem with the gx1fb driver. My board is GX1 with CS5530. 
Award bios. Vanilla kernel 2.6.23.1. I use our own test program.

Here is the right image:

http://www.pxe.ru/ban/gx1fb/gx1fb01.JPG

When I move mouse cursor over the "line of corruption", top part of the 
image becomes corrupted (800x600-8bit):

http://www.pxe.ru/ban/gx1fb/gx1fb02.JPG

This is the biggest possible corruption:

http://www.pxe.ru/ban/gx1fb/gx1fb03.JPG

I'm pretty shure demo program doesn't touch top area of framebuffer when 
cursor is over the "line of corruption". And I can "restore" image by 
moving mouse over corrupted area. I.e. image restores when demo program 
writes data to damaged area of framebuffer and corrupted again when demo 
program writes data near the "line of corruption".

Here is the same problem in 16 bit color:

http://www.pxe.ru/ban/gx1fb/gx1fb04.JPG

The "line of corruption" in 16bit mode is higher (red arrow). And there 
is one more damage - look at the text in the line marked with green arrow.


And second problem. Timings seems not working. I tried to pass 
"mode=800x600-8@60" and "mode=800x600-8@75" while loading gx1fb and 
fbset report correct timings for this rates. But monitor always reports 
85Hz.

This board works right (without image corruption and monitor reports 
60Hz when I ask for 60Hz) with 2.4 series kernel and nsc framebuffer driver.

This board works right (without image corruption and monitor reports 
60Hz) with 2.6.23.1 kernel and VESA driver in svgalib.



Thanks for your help.

-- 
Andrey

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

                 reply	other threads:[~2008-01-17 12:30 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=478F4A39.4070003@pxe.ru \
    --to=aka@pxe.ru \
    --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).