[Savage40] xv Overlay on crtc2 on SuperSavage (T23) / Argyll display calibration (Resend)

[Tim Roberts]

Jon Senior wrote:
> Resent because I wasn't a member of the list last time so couldn't be sure if it was blocked (checking the archives didn't reveal anything coming up).
>   

Yes, I long ago configured the list to unceremoniously and silently 
discard all messages from non-members.  Spam management was just too 
painful.

> I think the title says it all. ;-) Looking through the archives I notice that this got a mention as a known issue, but web searches only seem to produce hits dating from 2004/2005. Being as we are now in 2008 and this a device likely to lose rather than gain coders, I was wondering what the problem actually was.
>   

I'm not sure there are *any* active coders left.  This mailing list had 
more than 1,000 subscribers at its peak, but it's down below 450 now.   
The crtc2 support ("duo view") was added as a labor of love by Alex 
Deucher.  If he's listening, he may be able to address this.  If not, 
you may be out of luck.  The Savage graphics engine is celebrating the 
end of its first decade this year.  In human terms, that makes it 150 
years old...

> There is also a related issue in that in crtc1 with working overlay, video with a horizontal resolution greater than 800 pixels (IIRC) shows pink gradient bars from the 801st pixel onwards. This is hard to demonstrate as screen grabs using xine / player show the correct video.
>   

Does this depend on resolution or refresh rate?  There are a billion 
weird memory timing parameters in the Savage relating to memory access 
for the streams engine, but I thought all the common cases had been 
ironed out long ago.

-- 
Tim Roberts, timr at probo.com
Providenza & Boekelheide, Inc.