From: Sergey Vlasov <vsu@altlinux.ru>
To: John Zielinski <grim@undead.cc>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Radeonfb hsync fudge factor?
Date: Thu, 25 Dec 2003 00:00:03 +0300 [thread overview]
Message-ID: <20031224210003.GB2377@sirius.home> (raw)
In-Reply-To: <3FE9FCA9.3070107@undead.cc>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On Wed, Dec 24, 2003 at 03:52:57PM -0500, John Zielinski wrote:
> Geert Uytterhoeven wrote:
>
> >On Wed, 24 Dec 2003, Sergey Vlasov wrote:
> >
> >
> >>Probably this fudge factor was needed for some early chips?
> >>
> >>
> >
> >Yep, Mach64 needs one (but atyfb doesn't take care of it yet). So if you
> >switch
> >between depths, the display may shift horizontally. I guess this is due to
> >different lengths of the dataflow paths for different color depths.
> >
> >
>
> How many cards handled by radeonfb need it? That way we can add a
> fudge or nofudge driver option. Or put it in the card database if the
> numbers are roughly equal.
I suspect that either none of these cards need it (if this is really a
leftover from Mach64 days), or maybe some of the oldest (R100) cards
need it. Radeon VE QY (RV100) and 8500 QL (R200) certainly don't need
this fudge factor.
Does someone have an old R100-based card to test this?
> I need to see if that's what's causing the sync problems with my friends
> HDTV....
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-24 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 23:43 Radeonfb hsync fudge factor? John Zielinski
2003-12-24 1:42 ` Benjamin Herrenschmidt
2003-12-24 9:18 ` Sergey Vlasov
2003-12-24 12:12 ` Geert Uytterhoeven
2003-12-24 20:52 ` John Zielinski
2003-12-24 21:00 ` Sergey Vlasov [this message]
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=20031224210003.GB2377@sirius.home \
--to=vsu@altlinux.ru \
--cc=geert@linux-m68k.org \
--cc=grim@undead.cc \
--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).