cvs commit: src/sys/dev/kbdmux kbdmux.c
maksim.yevmenkin at gmail.com
Mon Feb 27 14:33:58 PST 2006
On 2/27/06, Marius Strobl <marius at alchemy.franken.de> wrote:
> On Sat, Feb 25, 2006 at 02:43:11PM -0800, Maksim Yevmenkin wrote:
> > Scott,
> > [...]
> > > So what do we need to do to get this enabled and running by default and
> > > get rid of the USB keyboard hack in the loader, as well as make the
> > > keyboard flags sane and predictable?
> > i think this should do it. any comments?
> FYI, in order to make kbdmux(4) work on sparc64 the endian bugs in
> the keyboard IOCTLs of syscons(4) and probably elsewhere need to
> be fixed. In order to make it work with Sun RS232 keyboards (sparc64
could you please point me to the keyboard ioctl with the endian bugs
you are talking about?
> uses AT, Sun RS232 and USB keyboards) kbdmux(4) needs to get rid of
> the assumption that a slave keyboard driver returns AT keyboard
> scancodes in K_RAW mode. The latter probably also applies to powerpc
> once there is support for ADB keyboards.
imo, that is not just kbdmux(4) assumption. it seems like a more
general assumption, i.e. ukbd(4), for example, translates usb
scancodes into at scancodes by default.
we should make a decision which scancodes keyboard drivers should be
returning and change kbdmux(4), syscons(4) etc. to support it.
until then, i'm afraid, sun rs232 and powerpc adb keyboard drivers
will have to translate their own scancodes into at scancodes (just
like ukbd(4) does).
More information about the cvs-src