wscons for FreeBSD?
Gordon Bergling
gbergling at 0xfce3.net
Thu Oct 27 10:07:32 PDT 2005
* Thus spake M. Warner Losh (imp at bsdimp.com):
> In message: <20051027134919.GA858 at node26.0xfce3.net>
> Gordon Bergling <gbergling at 0xfce3.net> writes:
> : * Thus spake Poul-Henning Kamp (phk at phk.freebsd.dk):
> : > In message <20051027133336.GA740 at node26.0xfce3.net>, Gordon Bergling writes:
> : > >I am currently working on project, which refactors a lot of FreeBSDs
> : > >console code.
> : >
> : > Sorry for nitpicking, but just to make sure we're clear about what we
> : > talk about here:
> : >
> : > When you say "console", do you mean
> : > "vga+keyboard" ?
> : > or
> : > "printf(9) destination" ?
> : > or
> : > "/dev/console" ?
> : > or all of the above ?
> :
> : What I mean was 'all of the above'. My projects aims to modernize
> : FreeBSDs console in a big picture. That whould range from "simple" vga
> : + keyboard to a possible machine indepent framebuffer API.
>
> wscons in NetBSD can be a console (as in /dev/console) destination.
> Much like sio(4) can be a console in FreeBSD. However, it is really a
> framework for integrating one or more frame buffers (vga), with zero
> or more keyboards and mice into a coherent input system.
>
> It is more of a syscons replacement than a solution to the 'console'
> issues that you've been keen on working out.
With other words, its something desireable to have at FreeBSD?
best regards,
Gordon
--
Gordon Bergling <GBergling at 0xfce3.net> http://www.0xFCE3.net/
PGP Fingerprint: 7732 9BB1 5013 AE8B E42C 28E0 93B9 D32B C76F 02A0
RIPE-HDL: MDTP-RIPE "There is no place like 127.0.0.0/8"
More information about the freebsd-arch
mailing list