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: 24 Nov 2001 18:38:42 +0100 [thread overview]
Message-ID: <1006623522.24435.63.camel@pismo> (raw)
In-Reply-To: <20011121193918.PTJS24249.tomts11-srv.bellnexxia.net@there>
On Wed, 2001-11-21 at 20:42, Kevin B. Hendricks wrote:
> FYI: Well I finally figured out what was up. It seems the first thing the
> special code for "DFPValidateModes" in radeon_driver.c does is delete all
> modes since the timing info is technically not needed by them for DFP.
>
> That is just a pisser since it removes the completely valid mode I had
> placed into the XF86Config-4 for just that reason.
>
> So no great mystery but I just don't think they should do that when using
> fbdevhw.
So fix it and submit a patch. ;)
> That is only part of the problem, the other is that if you change the
> depth from what is used by the frame buffer it does mess up as others have
> reported.
I believe Ben's work on radeonfb should fix this.
We were talking about different resolutions, which probably breaks due
to the fbdev driver.
--
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-24 17:38 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
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 [this message]
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=1006623522.24435.63.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.