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

Hello,

On Dec 28, 2006, at 00:57, Aaron J. Grier wrote:

> On Wed, Dec 27, 2006 at 04:22:21AM -0500, Michael Lorenz wrote:
>>> I was under the assumption that there is no wscons driver which
>>> provides both accelerated text mode _and_ safe framebuffer access,
>>> hence the "safety vs speed" choice faced at the moment.
>>
>> They all should also work with wsfb.
>
> that would be the x11/xf86-video-wsfb in pkgsrc, correct?

Yes.

> how does that work without underlying framebuffer support from the
> driver wsdisplay is attached to?

What do you mean? You can either mmap() the part of the framebuffer 
that wsdisplay uses at offset 0 or the graphics chip's 
PCI/SBus/whatever resource with their respective offsets, on most 
platforms both work. Sparc64 is such an exception, PCI resources might 
collide with the wsdisplay fb mainly because some ATI firmware likes to 
map registers to 0x2000 in memory ( on macppc for instance this can't 
happen because all PCI memory resources are required to be between 
0x80000000 and 0xff000000 )

> does x11/xf86-video-wsfb work with:
>
> wsdisplay* at ega? console ?
> wsdisplay* at vga? console ?
> wsdisplay* at pcdisplay? console ?

No. It only works with drivers that actually use a framebuffer.

> I'm guessing it will only with:
>
> wsdisplay* at vesafb? console ?
> wsdisplay* at pfb? console ?
> wsdisplay0 at ofb? console ?

There are a few more these days, like igsfb, chipsfb, machfb, voodoofb 
and radeonfb.
It should also work with ffb and cgsix although that doesn't make too 
much sense since both have accelerated xfree drivers and neither has 
any sort of DMA.

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

iQEVAwUBRZODxMpnzkX8Yg2nAQLitAf+LcACsCEi6fICEVr3R7vAPPCvlz6dnVl7
H/2ifhZjomvMPGnaOVOVLf8wwtRMC4i0l9H85j6ToYlCgTjN9ivNUWJ0+ucH8kNN
EW9Gmg2PyWxKBmeteIdV8iOmod6vqJfyWk3G3gl15IpYlRROXK2H3Xn6SJ4s7SV6
VAj4IHJmUEYEwjiYdOyHxeJjSSABTLrtDO301X85lb1MZDHB2d7NEv0Df9rEXz8T
wYLaAGEpQvQ3dYdG+nak5I4fftDVFPi77qVec5MQMnxSiIEWq6GAB2Ze2cbodPg5
uGQvw93zuQ5NfSjsWyofJpGphA4ba3jvdpp7qfhlHr1YfCL4njxgAA==
=HPWg
-----END PGP SIGNATURE-----