From: "Dominik 'Rathann' Mierzejewski" <rathann@icm.edu.pl>
To: linux-mips <linux-mips@linux-mips.org>
Subject: Re: newport console fixes
Date: Tue, 16 Mar 2004 10:50:51 +0100 [thread overview]
Message-ID: <20040316095051.GA19755@icm.edu.pl> (raw)
In-Reply-To: <20040315135708.GA7861@fh-brandenburg.de>
On Mon, Mar 15, 2004 at 02:57:08PM +0100, Markus Dahms wrote:
> 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.
Just for the record, my Indy also exhibits this fault, but has different
cmap revision than yours:
NG1: Revision 6, 8 bitplanes, REX3 revision B, VC2 revision A,
xmap9 revision A, cmap revision C, bt445 revision D
NG1: Screensize 1280x1024
> #### 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
Regards,
--
Dominik 'Rathann' Mierzejewski <rathann@icm.edu.pl>
Interdisciplinary Centre for Mathematical and Computational Modelling
Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810
next prev parent reply other threads:[~2004-03-16 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 13:57 newport console fixes Markus Dahms
2004-03-16 9:50 ` Dominik 'Rathann' Mierzejewski [this message]
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=20040316095051.GA19755@icm.edu.pl \
--to=rathann@icm.edu.pl \
--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