From: Nicholas Wourms <nwourms@netscape.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Status of radeonfb in 2.5?
Date: Fri, 18 Oct 2002 18:16:26 -0400 [thread overview]
Message-ID: <aoq14h$qqg$1@main.gmane.org> (raw)
In-Reply-To: 1034977216.615.27.camel@daplas
Antonino Daplas wrote:
> Not necessarily painless...
>
> Given timings in X modeline format (you can generate with xvidtune):
>
> "XRESxYRES" MHZ XACTIVE FP_X HSYNC BP_X YACTIVE FP_Y VSYNC
> BP_Y +hsync +vsync
>
> Then timings in fb.mode:
>
> mode "XRESxYRES MHZ"
> # D: "MHZ, H: HorizSync kHz, V: VertRefresh Hz
> geometry xres yres vxres vyres bpp
> timings pixclock left right upper lower hsync vsync
> hsync high
> vsync high
> endmode
>
> where:
>
> pixclock = 1000000/MHZ
> left = BP_X - HSYNC
> right = FP_X - XACTIVE
> upper = BP_Y - VSYNC
> lower = FP_Y - YACTIVE
> hsync = HSYNC - FP_X
> vsync = VSYNC - FP_Y
>
> What you need to concentrate on is the timings field of fb.modes. This
> also assumes that the driver actually reads the timings field. Some
> drivers disregard those values (considers only xres and yres) then
> configure their own timings.
>
Tony,
Thank you, this is *exactly* what I was looking for! I never knew what
xvidtune was really for, but this sure answers that one.
Cheers,
Nicholas
-------------------------------------------------------
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD
next prev parent reply other threads:[~2002-10-18 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 23:17 Status of radeonfb in 2.5? Nicholas Wourms
2002-10-15 23:41 ` Ani Joshi
2002-10-29 14:15 ` Nicholas Wourms
2002-10-16 22:36 ` Benjamin Herrenschmidt
2002-10-16 20:55 ` Nicholas Wourms
2002-10-16 22:45 ` Michel Dänzer
2002-10-18 17:21 ` Nicholas Wourms
2002-10-18 19:28 ` Michel Dänzer
2002-10-18 20:54 ` Nicholas Wourms
2002-11-04 8:46 ` James H. Cloos Jr.
2002-10-18 21:40 ` Antonino Daplas
2002-10-18 22:16 ` Nicholas Wourms [this message]
2002-11-21 18:38 ` James Simmons
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='aoq14h$qqg$1@main.gmane.org' \
--to=nwourms@netscape.net \
--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).