From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: xfree86/fbdevhw not sending right mode to radeonfb.c
Date: 18 Nov 2001 18:31:18 +0100 [thread overview]
Message-ID: <1006104678.9556.7.camel@pismo> (raw)
In-Reply-To: <20011118140926.MNTJ9849.tomts10-srv.bellnexxia.net@there>
On Sun, 2001-11-18 at 15:12, Kevin B. Hendricks wrote:
>
> I am still working on the radeon driver for XFree86 and trying to get the
> useFBDev options to work properly.
>
> I have a properly constructued mode line in my XF86Config-4 which I
> specifiy.
>
> However when the XFree86 radeon_driver passes this initial mode to the
> radeonfb.c kernel framebuffer driver, most of the mode information is
> missing (no detailed timing info, just xres and yres, etc.
>
> The radeonfb.c messes up when this incomplete mode information is passed
> to it (from fbdevHWModeInit ?).
>
> So where should I look to see where this is messing up. It does not
> appear to be an issue with the framebuffer kernel driver since it is the
> victim of the receiving end of the bad data.
>
> It is almost like the the xfree86 code that parses the XF86Config-4 config
> file is not properly grabbing the specific mode information (or somehow
> later it is being mangled).
>
> Any hints or guidance of where to look in xfree86, would be greatly
> appreciated.
fbdevHW and fbdevHWModeInit in particular are probably good places to
start. If you enable debugging in fbdevHW, it will print detailed mode
information.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-18 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 14:12 xfree86/fbdevhw not sending right mode to radeonfb.c Kevin B. Hendricks
2001-11-18 17:31 ` Michel Dänzer [this message]
2001-11-18 18:45 ` Kevin B. Hendricks
2001-11-19 11:00 ` Kostas Gewrgiou
2001-11-21 19:42 ` Kevin B. Hendricks
2001-11-24 17:38 ` Michel Dänzer
2001-11-24 18:04 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-11-19 15:28 Kevin Hendricks
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=1006104678.9556.7.camel@pismo \
--to=michdaen@iiic.ethz.ch \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).