On Fri, 30 Jul 1999 22:40:36 +0200
Lennart Augustsson <lennart@augustsson.net> wrote:
> Could you tell me what your configuration is? It might be some
> combination of ws* that I've not tested.
wsdisplay* at tga?
wsdisplay* at vga?
...this was by far the biggest problem.
> I've just fixed this problem. I'll commit it as soon as I've tested it.
> I didn't realize that the needs-count would force a needs-count on wsdisplay
> as well.
Okay. I've committed a kludge in the mean time.
> Every wsdisplay has an implicit mux, even if you don't have any other
> muxes in the kernel. This mux will get fed from the console keyboard
> regardless of how you set up things. I.e., the console keyboard is "glued"
> to the display. Any further keyboard can either be attached directly to
> the wsdisplay (using wsconscfg -k N) or by first feeding them into
> another mux (probably using the mux locator) which is then attached
> to the wsdisplay (using wsconscfg -m N).
Does the display then take inputs from two different muxes? Or, do you have
to detach the console keyboard from the display's implicit mux, and attach
it to the other mux?
-- Jason R. Thorpe <thorpej@nas.nasa.gov>