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

Hello,

On Feb 26, 2007, at 15:14, Greg A. Woods wrote:

> At Mon, 26 Feb 2007 14:37:46 -0500,
> Michael Lorenz wrote:
>>
>> Several people volunteered to write wscons drivers for other
>> framebuffers but so far no code made it back to us - I already wrote
>> drivers for all SBus graphics hardware I have access to.
>
> Now that I'm sitting with another rejuvianted hires monitor in front of
> me (thanks very much to my friend and video wizard Doug Lee!) I could
> mabye try to do the job for bwtwo though, if there were some good notes
> and/or internal documentation on what needs to be done to wscons to get
> it to work, and provided that I don't have to frob the actual bwtwo
> driver itself much or at all (as I don't have any hardware specs for it
> to work from, though if someone has those they would be handy!).

The bwtwo is unaccelerated monochrome, isn't it? In that case attaching 
a wsdiaplay is trivial, all you need to do is find out some information 
on geometry / data organization ( width, height, bytes per line, fb 
address ), fill in a struct rasops_info and that's pretty much it. 
Vesafb might be a good starting point.

> In the world of CRT displays there's nothing easier on the eyes than a
> nice paper-white high-resolution long-persistence phosphor (zero
> flicker) monitor.

Indeed, I had one of those hooked up to an IPX running X in StaticGrey.

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

iQEVAwUBReNG2MpnzkX8Yg2nAQKGDwgAgcjr/SfZRhLK47MufaDtufeLVBFPtvSL
GtfE8lt0ArCfn3/DDVcxfHPPqI9NvTV/4MHmFbQOm0c8jqOgwEOkaPKr4QnkQ5A5
lrhiT8Vfot+1EDVqpJLegTnDRCshoMaL7GyByLMHsVkDaBZxUGv16HACXna3ju52
Q5MoimpvQUOHkNPVSzud38B/ZGA4LKUPE2mYjVYDShJCjHNTVwRMPyHNSmF4dYyH
rKLzhMATVKmBbogsgWcLnKtkAbV0cMWIn//d+PmjzzPNbX6u9oBFqlW7Jj/kdfsI
6RvLOkKA2Lz6/nCXmnqWD/3T+WpqmJMkMH7DLp3QBNwWq3I74vqMVQ==
=aHSe
-----END PGP SIGNATURE-----