-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Feb 28, 2007, at 15:45, Greg A. Woods wrote:

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

You can do that with XFree86 as well, they have a cg14 driver but for 
lack of hardware I never tried it. It does support 24bit IIRC. My U1 
runs dual head XFree86 with two cgsix.

> How does the SS20 firmware tell which frame buffer to use for the
> console again?

output-device

> 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' is a devalias pointing at the actual device node. Either add 
your own devalias or use the actual device path.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBReXt7cpnzkX8Yg2nAQI4OAgAsMIAne+clAnByuF9CDTRF5Ftvld1HRmg
e33aTFi7o5oVX7tBCZSblcuSpzQPFRGoC3Y73wHgDZtOBanQTld0S7KjIZx09sg6
OGDdD2GPPU9LiukBzWVYwFqnfSqsyQ5BRU9OhsincXxg/PV3elmNXPMPIM5B3ukK
jW7sJ9HXIgRTeVl5a2hngYOUm0pfpZwyv5dTPK480cK4iOQtbNlKduknq3Qgh+20
wjKuGoAZLoOcR9w9F2fsuICFcUBvO+HdwX5o6bATiLqfKAA5od2WqRaP+MehqRYe
ZFo6zc9MiMqglJ+qzPpcGqRJP1kz6shqQbc8Fh7b7yS4UrdLmAkMcw==
=ViG8
-----END PGP SIGNATURE-----