2007/4/17, Marcel Moolenaar <[EMAIL PROTECTED]>:
Thanks for detailed useful reply.
As for vtc(4): I've not been working on input devices because of the lack of a generic layer. Note that vtc(4) deals with the low-level console as much as it deals with user-visible terminals, so from that point of view, a user space stack will not address the need for having console input when there's no (functional) user space -- this includes early boot, the kernel debugger and single-user mode. I therefore doubt that it will sufficiently (or at all) solve problems we already have.
Yup. That's what I'm thinking about right now. One of possible decisions is to move stacking into the kernel and have an optional usermode part 'stacked' through a 2 'stub' drivers.
Also, while multiplexing is an important feature I think that de- multiplexing is important too.
I guess, demux can be done by 'top' driver or by drivers layout. There are several ways, that have little impact on the total design. Thanks, - Maxim _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
