From: Russell King <rmk@arm.linux.org.uk>
To: Kai Engert <kai.engert@gmx.de>
Cc: James Mayer <james@cobaltmountain.com>,
linux-kernel@vger.kernel.org, Ani Joshi <ajoshi@unixbox.com>
Subject: Re: Sync bit bug in drivers/video/radeonfb.c ?
Date: Tue, 30 Jul 2002 16:08:45 +0100 [thread overview]
Message-ID: <20020730160845.B7677@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3D46A8A0.2020101@gmx.de>; from kai.engert@gmx.de on Tue, Jul 30, 2002 at 04:54:24PM +0200
On Tue, Jul 30, 2002 at 04:54:24PM +0200, Kai Engert wrote:
> That's strange! I'm using a C1MGP, german version.
>
> See http://www.kuix.de/sonyc1/lspci for lspci output.
>
> However, if you apply the patch below, and you have to manually set it
> to vsync low, I guess this means your on boot mode was set to high,
> which is what is requested in modedb.c, and it sounds like the patch
> below is correct. But we probably need more entries in modedb.c to
> support all models of the C1M.
Maybe the real answer is for someone to scope the sync signals and
work out whether the original or the patched version is correct.
Then someone's left with a buggy monitor (which, quote honestly
wouldn't surprise me in the least.)
If a buggy monitor is the problem, it might be an idea to introduce
generic "invert_vsync=1" and "invert_hsync=1" options to the kernel
(since a buggy monitor will affect _all_ cards, not just radeon)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-07-30 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 12:43 Sync bit bug in drivers/video/radeonfb.c ? Kai Engert
2002-07-30 14:33 ` James Mayer
2002-07-30 14:54 ` Kai Engert
2002-07-30 15:08 ` Russell King [this message]
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=20020730160845.B7677@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ajoshi@unixbox.com \
--cc=james@cobaltmountain.com \
--cc=kai.engert@gmx.de \
--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