Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Markus Dahms <dahms@fh-brandenburg.de>
To: linux-mips <linux-mips@linux-mips.org>
Subject: newport console fixes
Date: Mon, 15 Mar 2004 14:57:08 +0100	[thread overview]
Message-ID: <20040315135708.GA7861@fh-brandenburg.de> (raw)

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

Hello list,

I patched the newport console driver to have the correct colormap
when exiting X11 / switching from X11 to console.
This problem doesn't affect all versions of the newport, the old
revision in my very old indy doesn't show these effects.
Some revision information of my (different) newports is written in
the header of the attached diff.
Could someone please apply the patch to cvs (2.4 branch, 2.6 isn't
very usable for me), if there are no objections?

Markus

-- 
No RISC - No fun!

[-- Attachment #2: patch-newport_con-switchvt.diff --]
[-- Type: text/plain, Size: 688 bytes --]

#### old newport, works w/o patch
#
# NG1: Revision 3, 8 bitplanes, REX3 revision B, VC2 revision A, 
#      xmap9 revision A, cmap revision C, bt445 revision A
# NG1: Screensize 1296x1024
#
## (strange resolution, isn't it? - X does 1280x1024 anyway)

#### new newport, works w/ patch
#
# NG1: Revision 6, 8 bitplanes, REX3 revision B, VC2 revision A,
#      xmap9 revision A, cmap revision D, bt445 revision D
# NG1: Screensize 1280x1024

--- drivers/video/newport_con.c.orig	Mon Mar 15 10:28:08 2004
+++ drivers/video/newport_con.c	Mon Mar 15 09:55:24 2004
@@ -448,6 +448,8 @@
 {
 	static int logo_drawn = 0;
 
+	newport_init_cmap();
+
 	topscan = 0;
 	npregs->cset.topscan = 0x3ff;
 

             reply	other threads:[~2004-03-15 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 13:57 Markus Dahms [this message]
2004-03-16  9:50 ` newport console fixes Dominik 'Rathann' Mierzejewski
2004-03-16 10:18   ` Thiemo Seufer

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=20040315135708.GA7861@fh-brandenburg.de \
    --to=dahms@fh-brandenburg.de \
    --cc=linux-mips@linux-mips.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