From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Rüdiger Scholz" <rscholz@hrzpub.tu-darmstadt.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [PATCH] Additional Address cleanup
Date: Tue, 2 Oct 2001 14:57:01 +0200 [thread overview]
Message-ID: <20011002145701.B3747@solo.franken.de> (raw)
In-Reply-To: <3BB8A3FC.7090304@hrzpub.tu-darmstadt.de>; from rscholz@hrzpub.tu-darmstadt.de on Mon, Oct 01, 2001 at 07:12:28PM +0200
On Mon, Oct 01, 2001 at 07:12:28PM +0200, Rüdiger Scholz wrote:
> I'm glad i'm not the only one with this problem. And even someone knows
> the solution for the problem. ;-). I also disabled my add-on card the
> same way, and then the sti-stuff worked quite fine. But it would be
> cooler to use the second card, too.
sure, after having fixed the X problem I had with artist/viz-eg cards
I've spend some time looking at HCRX. I've found one problem, when we
load the color for the HCRX, the card locks up, probably because we
do a whole color map load per setcolreg() call. I've changed that
and the card doesn't lock up anymore. But either I get wrong colors
without colormap loading or I have some strange looking stuff "behind"
the normal screen content. It looks like either we need to initialize
the Z-Buffer (I'll try without, when I get home) or some overlay/attribute
planes need a better treatment.
> But you already have a patch? I can only help with testing and a little
> bit of debugging as all of my fingers are thumbs ;-)
right now I'm not at home (and behind a 28.8k modem connection) and I only
have a C200 with me, which has other STI problems. So it will take a little
bit more time, to get the HCRX going.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ Alexander Viro on linux-kernel ]
prev parent reply other threads:[~2001-10-02 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 16:48 [parisc-linux] [PATCH] Additional Address cleanup Ryan Bradetich
2001-09-21 18:21 ` Ryan Bradetich
2001-09-21 18:35 ` Matthew Wilcox
2001-09-24 11:06 ` Rüdiger Scholz
2001-09-25 3:59 ` Ryan Bradetich
2001-09-25 17:33 ` Rüdiger Scholz
2001-09-25 19:00 ` Thomas Bogendoerfer
2001-10-01 17:12 ` Rüdiger Scholz
2001-10-02 12:57 ` Thomas Bogendoerfer [this message]
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=20011002145701.B3747@solo.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rscholz@hrzpub.tu-darmstadt.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.