From: Antonino Daplas <adaplas@pol.net>
To: Nicholas Wourms <nwourms@netscape.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Status of radeonfb in 2.5?
Date: 19 Oct 2002 05:40:19 +0800 [thread overview]
Message-ID: <1034977216.615.27.camel@daplas> (raw)
In-Reply-To: <3DADD22F.9030508@netscape.net>
On Thu, 2002-10-17 at 04:55, Nicholas Wourms wrote:
> B) Does anyone have a painless, yet precise way of
> generating modelines for fb.modes if you are using
> XFree-4.2? I only ask because the XFree modelines are all
> determined by i2c DDC probing, thus there are none in the
> XF86Config file. The modeline output captured in the log
> XFree.0.log is not the same output which modeline2fb
> expects. Anyhow, I've tried using some of the information
> in the log, but I always get funky results. I may be
> looking in the wrong place, but the documentation for both
> the fbdev kernel drivers and the X drivers are sorely out of
> date, so please excuse me if this is a question that has
> previously been answered. I just need some formulae to
> convert values between what shows up in XFree.0.log when i2c
> DDC probes for the modelines and what needs to go in
> fb.modes. Thanks in advance!
>
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
-------------------------------------------------------
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 21:47 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 [this message]
2002-10-18 22:16 ` Nicholas Wourms
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=1034977216.615.27.camel@daplas \
--to=adaplas@pol.net \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=nwourms@netscape.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).