On Mon, May 23, 2005 at 11:43:48PM -0400, Michael wrote: >Hello, > >> That's good. Even better, especially for the modular driver, would be >> to handle this automatically in the driver at run-time. The mouse >> driver does this and should handle auto-detection of wscons support on >> NetBSD for mouse input without the need for any mouse configuration >> data in the config file. > >I'll have a look how the mouse driver does that and see if I can do >something similar for kbd - I'm not sure that's really necessary though, >the only NetBSD port that could run XFree86 without wscons was i386 - it >switched to wscons ages ago.
My point is only that you shouldn't have to tell the XFree86 server to use wscons for the keyboard driver. It should know without being told, especially on platforms where it is the only viable option. Also, as you noted in your first message on this subject, it should try a default wskbd device if none is specified explicitly in the config file. The wscons support is used for OpenBSD too. I don't remember the details now, but some of the i386 Open/NetBSD test platforms I was using when automating the mouse device/protocol selection either didn't have wscons or it wasn't activated in the default install. See the OpenBSD/NetBSD versions of the FindDevice(), GuessProtocol() and haveWSCons() functions in bsd_mouse.c for how it is handled by the mouse driver. >> >The Sun map had a minor mistake (or feature?)- Props/L3 and >> >ScrollLock were swapped. >> >> Sounds like a bug. > >I wasn't sure, I have only Type 5 keyboards here ( well, one 5 and one >5c, both US ). Anyway, I tested the whole thing on NetBSD/macppc too - >works as expected. Sounds good. David _______________________________________________ Devel mailing list [email protected] http://XFree86.Org/mailman/listinfo/devel
