At Tue, 27 Feb 2007 00:33:09 -0500,
Michael Lorenz wrote:
> 
> The SS20's onboard framebuffer has no wscons driver yet so you're stuck 
> with the traditional console or you can use a cg6.

That's another one I could probably help to fix, or at least test.  My
new-to-me multi-sync monitor (normally used on my NCD HMXpro) has dual
inputs so I'm considering stuffing an 8MB VSIMM I have into the SS20 I
currently use just with the bwtwo.

This would be especially nice if I could run it dual-headed with X too,
but I guess I'd need some additional patches from der Mouse to get a
kernel and an Xserver from xsrc-current to work with both framebuffers,
with the cg14 in full 24-bit mode.

How does the SS20 firmware tell which frame buffer to use for the
console again?  The eeprom output just shows the following, but I must
have done something to get it to work by with the bwtwo, I just can't
remember what.

	output-device=screen
	screen-#columns=120
	screen-#rows=52

I still haven't got my sparcs running netbsd-4 either, but maybe that'll
happen in the not too distant future, though it looks like my build
machine is going to be stuck working more slowly over NFS for the time
being as my smtp & dns server is going to need its RAID array replaced
with the one I've been using for the builds.

-- 
						Greg A. Woods

H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>       Secrets of the Weird <woods@weird.com>