linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Jeff Rugen <jprugen@earthlink.net>
Cc: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: RTC and SCSI for PowerStack/2.4.6 Kernel
Date: Mon, 9 Jul 2001 20:48:08 +0200	[thread overview]
Message-ID: <20010709204808.A12487@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0107090842230.1593-100000@raptor.earthlink.net>; from jprugen@earthlink.net on Mon, Jul 09, 2001 at 09:20:21AM -0700

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

On Mon, Jul 09, Jeff Rugen wrote:

> I did have VGA console be the default, and installed clgenfb as a module.

Is there a way to rmmod the module later?
The colors are wrong in X whit >8bit and the console is slow with fbcon :)

> On a related note, the endianness issue with gpm seems to also show up
> when running the VGA console -- any text that is written to a non-visible
> virtual terminal is not byte-swapped, so it appears to be garbage when you
> switch back to that virtual terminal.  This isn't a problem when running
> clgenfb as the terminal though (I don't know how gpm worked in either
> mode).

The attached patch fix that, but it seems to be wrong.
Geert said the shadow buffer is stored in native endian. The VGA text
console itself is the "shadow buffer" for the foreground console and
little endian.



Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

[-- Attachment #2: y_ppc_2.4.5_vga_console.diff --]
[-- Type: text/plain, Size: 977 bytes --]

--- linux-2.4.5/include/asm-ppc/vga.h	Tue May 22 00:02:06 2001
+++ linux-2.4.5.vgafix/include/asm-ppc/vga.h	Mon May 28 11:50:48 2001
@@ -15,11 +15,11 @@

 #include <linux/config.h>

-#if defined(CONFIG_VGA_CONSOLE) || defined(CONFIG_MDA_CONSOLE)
+#if defined(CONFIG_VGA_CONSOLE)

 #define VT_BUF_HAVE_RW
 /*
- *  These are only needed for supporting VGA or MDA text mode, which use little
+ *  These are only needed for supporting VGA text mode, which use little
  *  endian byte ordering.
  *  In other cases, we can optimize by using native byte ordering and
  *  <linux/vt_buffer.h> has already done the right job for us.
@@ -38,7 +38,11 @@
 #define VT_BUF_HAVE_MEMCPYW
 #define scr_memcpyw	memcpy

-#endif /* !CONFIG_VGA_CONSOLE && !CONFIG_MDA_CONSOLE */
+#define VT_BUF_HAVE_MEMCPYF
+#define scr_memcpyw_from memcpy
+#define scr_memcpyw_to memcpy
+
+#endif /* CONFIG_VGA_CONSOLE */

 extern unsigned long vgacon_remap_base;
 #define VGA_MAP_MEM(x) (x + vgacon_remap_base)

  reply	other threads:[~2001-07-09 18:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-08  7:49 RTC and SCSI for PowerStack/2.4.6 Kernel Jeff Rugen
2001-07-08 19:00 ` Tom Rini
2001-07-09 14:38   ` Jeff Rugen
2001-07-09 14:47     ` Benjamin Herrenschmidt
2001-07-09 14:57     ` Tom Rini
2001-07-09 15:08       ` Geert Uytterhoeven
2001-07-09 15:17         ` Tom Rini
2001-07-09 15:25         ` Jeff Garzik
2001-07-09 16:20       ` Jeff Rugen
2001-07-09 18:48         ` Olaf Hering [this message]
2001-07-09 20:37           ` Jeff Rugen
2001-07-09 20:54             ` Olaf Hering
2001-12-13 16:13 ` Tom Rini

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=20010709204808.A12487@suse.de \
    --to=olh@suse.de \
    --cc=jprugen@earthlink.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).