Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux@cthulhu.engr.sgi.com
Subject: newport console problems, some hardware questions
Date: Mon, 15 Mar 1999 22:03:41 +0100	[thread overview]
Message-ID: <19990315220341.C2301@alpha.franken.de> (raw)

Ok, I finally found the reason for the video corruptions with the new
newport console some reported to me. It happens only, when there are
less than 1024 scanlines on the screen. My fix is to enable the
faster scrolling only with 1024 scanline screen modes. This slows
down scrolling, and I hope there is a better solution (but I doubt it).

It looks like video rams get only refreshed, when they are displayed. 
Is this true ? I've tried enabling the vram refresh in the config
register, but that didn't change anything. Is there are a way to avoid
losing the content of offscreen scanlines ?

Another question:

As the newport problem is mostly solved, I'll try to get the scsi fixed.
I'm now able to reproduce a complete lockup with my DAT drive. While
looking for the reason, I've got GIO fifo full interrupts (INT2 local
interrupt 0). Can someone explain, when these interrupts occur ?

Thomas.

-- 
   This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
                                        [Martin `MJ' Mares on linux-kernel]

             reply	other threads:[~1999-03-15 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-15 21:03 Thomas Bogendoerfer [this message]
1999-03-18 12:45 ` newport console problems, some hardware questions Michael Hill
1999-03-18 21:35   ` Thomas Bogendoerfer

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=19990315220341.C2301@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux@cthulhu.engr.sgi.com \
    /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