From: John Zielinski <grim@undead.cc>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Radeonfb hsync fudge factor?
Date: Tue, 23 Dec 2003 18:43:17 -0500 [thread overview]
Message-ID: <3FE8D315.1000904@undead.cc> (raw)
What's the hsync fudge factor used for?
I noticed that the left edged of my screen moved a bit when I was
switching between 32/16/8 bpp modes and tracked it down to this.
John
p.s. I have this urge to giggle every time I type in the words "fudge
factor" for some reason. :)
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next reply other threads:[~2003-12-23 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 23:43 John Zielinski [this message]
2003-12-24 1:42 ` Radeonfb hsync fudge factor? 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
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=3FE8D315.1000904@undead.cc \
--to=grim@undead.cc \
--cc=benh@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).