From: Mike Houston <mikeserv@bmts.com>
To: linux-kernel@vger.kernel.org
Cc: benh@kernel.crashing.org
Subject: Re: Radeon Framebuffer Driver in 2.6.3?
Date: Fri, 27 Feb 2004 12:19:38 -0500 [thread overview]
Message-ID: <20040227121938.213a83e2.mikeserv@bmts.com> (raw)
In-Reply-To: <1077865490.22215.217.camel@gaston>
On Fri, 27 Feb 2004 18:04:51 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> If it happens only after switching back from XFree, then it's a known
> problem. I have implemented a fix locally but got sidetracked before I
> could test it properly.
>
> Can you test the patch below ? :
>
> ===== drivers/char/vt.c 1.61 vs edited =====
> --- 1.61/drivers/char/vt.c Thu Feb 19 14:43:03 2004
> +++ edited/drivers/char/vt.c Fri Feb 27 17:27:09 2004
> @@ -2743,12 +2743,12 @@
That patch fixes the problem for me also, Benjamin. Thank you!
Now I have my proper framebuffer console fully usable again (I had switched to VESA fb console in the interrim and that was OK, but it was causing a conflict with the linear framebuffer handle, unable to allocate an mtrr and unable to use write combining on starting X/DRI)
ATI Technologies Inc Radeon RV200 QW [Radeon 7500] on i845 chipset.
Grogan
next prev parent reply other threads:[~2004-02-27 17:24 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
2004-02-27 17:19 ` Mike Houston [this message]
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=20040227121938.213a83e2.mikeserv@bmts.com \
--to=mikeserv@bmts.com \
--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®