From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: arief# <arief_m_utama@telkomsel.co.id>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Radeon Framebuffer Driver in 2.6.3?
Date: Fri, 27 Feb 2004 20:56:42 +1100 [thread overview]
Message-ID: <1077875802.22215.267.camel@gaston> (raw)
In-Reply-To: <1077876373.843.3.camel@damai.telkomsel.co.id>
On Fri, 2004-02-27 at 21:06, arief# wrote:
> Dear all.
>
>
> This patch from Benjamin solved my problem.
>
> To Zilvinas <zilvinas@gemtek.lt>, I've tried your suggestion to change
> my XF86Config-4 file to include UseFBDev line. But it doesnt work. It
> made my Xserver wont even start. But I'm not sure, it could be X problem
> (Debian Unstable got some updated X package that I haven't got a chance
> to upgrade to).
There is a problem with recent radeonfb's an X + UseFBDev. I think the
problem is that XFree is claiming a mode whose virtual resolution is very
large. I have to verify that (it works for me here). Radeonfb has
limitations on what it allows on the virtual resolution in recent
version to limit the ioremap'ing done in the kernel. Unfortunately,
there is no simple way to "detach" one from the other at this point.
I should modify radeonfb to crop the virtual resolution instead of
failing though...
Can you try hacking in drivers/video/aty/radeon_base.c, function
check_mode() and see why it fails ? (I think it's that function
that is failing).
Ben.
next prev parent reply other threads:[~2004-02-27 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 6:27 Radeon Framebuffer Driver in 2.6.3? arief#
2004-02-27 7:04 ` Benjamin Herrenschmidt
2004-02-27 10:06 ` arief#
2004-02-27 9:56 ` Benjamin Herrenschmidt [this message]
2004-02-27 10:45 ` Zilvinas Valinskas
2004-02-27 17:19 ` Mike Houston
2004-02-27 18:00 ` James Simmons
2004-02-27 22:43 ` Benjamin Herrenschmidt
2004-02-28 0:58 ` James Simmons
2004-02-28 1:37 ` Benjamin Herrenschmidt
2004-03-02 0:22 ` James Simmons
2004-03-02 0:26 ` Benjamin Herrenschmidt
2004-03-02 3:08 ` Paul Jackson
2004-03-02 7:50 ` Paul Jackson
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=1077875802.22215.267.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=arief_m_utama@telkomsel.co.id \
--cc=linux-kernel@vger.kernel.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.