From: Zilvinas Valinskas <zilvinas@gemtek.lt>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: arief# <arief_m_utama@telkomsel.co.id>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Radeon Framebuffer Driver in 2.6.3?
Date: Fri, 27 Feb 2004 12:45:28 +0200 [thread overview]
Message-ID: <20040227104528.GB31552@gemtek.lt> (raw)
In-Reply-To: <1077875802.22215.267.camel@gaston>
On Fri, Feb 27, 2004 at 08:56:42PM +1100, Benjamin Herrenschmidt wrote:
> 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).
Not sure what was failing on Arief# laptop, here it works perfectly
fine. Hardware: Compaq EVO N800v, kernel 2.6.3 , frambuffer and
UseFBDev "true" just fine.
Without UseFBDev console had almost the same effects Arief has reported.
After "clear screen" ^L in console with X running in background, I see a
lot of artifacts ... UseFBDev made it go away.
BR
>
> Ben.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-02-27 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 6:27 arief#
2004-02-27 7:04 ` Benjamin Herrenschmidt
2004-02-27 10:06 ` arief#
2004-02-27 9:56 ` Benjamin Herrenschmidt
2004-02-27 10:45 ` Zilvinas Valinskas [this message]
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=20040227104528.GB31552@gemtek.lt \
--to=zilvinas@gemtek.lt \
--cc=arief_m_utama@telkomsel.co.id \
--cc=benh@kernel.crashing.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®