newport console problems, some hardware questions

newport console problems, some hardware questions

[Thomas Bogendoerfer]

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]

Re: newport console problems, some hardware questions

[Michael Hill]

On Mar 15, 10:03pm, Thomas Bogendoerfer wrote:

> 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).

This works well, Thomas.  Now I can see what's happening on the screen.  I
haven't run into any problems with the scrolling speed yet (I don't notice a
difference just by watching it).

Mike

Re: newport console problems, some hardware questions

[Thomas Bogendoerfer]

On Thu, Mar 18, 1999 at 07:45:43AM -0500, Michael Hill wrote:
> > faster scrolling only with 1024 scanline screen modes. This slows
> > down scrolling, and I hope there is a better solution (but I doubt it).
> 
> This works well, Thomas.  Now I can see what's happening on the screen.  I
> haven't run into any problems with the scrolling speed yet (I don't notice a
> difference just by watching it).

it isn't that bad, when the lines are only partially filled or whenever
columns contain the same content. But there is a fix insight. I just
have to figure out, how to completly clear the scrolled in scanlines.

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]