From: Paul Mackerras <paulus@samba.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>,
Hugh Dickens <hugh@veritas.com>,
Michael Ellerman <michael@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 5/6] From: Andrew Morton <akpm@osdl.org>
Date: Tue, 3 Oct 2006 16:55:52 +1000 [thread overview]
Message-ID: <17698.2424.528747.211313@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20061002225053.46be0324.akpm@osdl.org>
Andrew Morton writes:
> I still get crap all over the screen when xmon is tring to print something
> (at least, I assume that's what causes it). See
> http://userweb.kernel.org/~akpm/s5000334.jpg
That is because the nvidia console driver has changed the line pitch
from what the firmware set it to. This should fix it by making the
nvidia driver inform the btext engine (which xmon uses if the screen
is its output device) about changes to display resolution.
Signed-off-by: Paul Mackerras <paulus@samba.org>
---
diff --git a/drivers/video/nvidia/nvidia.c b/drivers/video/nvidia/nvidia.c
index d4f8501..18b9101 100644
--- a/drivers/video/nvidia/nvidia.c
+++ b/drivers/video/nvidia/nvidia.c
@@ -28,6 +28,9 @@ #ifdef CONFIG_PPC_OF
#include <asm/prom.h>
#include <asm/pci-bridge.h>
#endif
+#ifdef CONFIG_BOOTX_TEXT
+#include <asm/btext.h>
+#endif
#include "nv_local.h"
#include "nv_type.h"
@@ -681,6 +684,13 @@ #endif
nvidia_vga_protect(par, 0);
+#ifdef CONFIG_BOOTX_TEXT
+ /* Update debug text engine */
+ btext_update_display(info->fix.smem_start,
+ info->var.xres, info->var.yres,
+ info->var.bits_per_pixel, info->fix.line_length);
+#endif
+
NVTRACE_LEAVE();
return 0;
}
next prev parent reply other threads:[~2006-10-03 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061003010842.438670755@goop.org>
[not found] ` <20061003010933.392428107@goop.org>
2006-10-03 4:23 ` Paul Mackerras
2006-10-03 4:33 ` Andrew Morton
2006-10-03 5:19 ` Paul Mackerras
2006-10-03 5:50 ` Andrew Morton
2006-10-03 6:55 ` Paul Mackerras [this message]
2006-10-03 7:20 ` Andrew Morton
2006-10-03 7:25 ` Benjamin Herrenschmidt
[not found] ` <20061003010930.971200285@goop.org>
2006-10-03 10:37 ` [PATCH 1/6] Generic implemenatation of BUG Andi Kleen
2006-10-03 15:53 ` Jeremy Fitzhardinge
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=17698.2424.528747.211313@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=rusty@rustcorp.com.au \
/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®