On Tue, May 04, 2010 at 01:40:41PM -0700, Tony Lindgren wrote: > * Janusz Krzysztofik <jkrzyszt@xxxxxxxxxxxx> [100427 18:09]: > > The patch introduces a serio driver that supports a keyboard serial port found > > on the Amstrad Delta videophone board. > > > > After initializing the hardware, the driver reads its input data from a buffer > > filled in by the board FIQ (Fast Interrupt Request) handler. > > > > Standard AT keyboard driver (atkbd) will be used on top of the serio layer for > > handling the E3 keyboard (called mailboard) connected to the port. Since the > > device generated scancodes differ from what the atkbd expects, a custom key > > code to scan code table must be loaded from userspace for the keyboard to be > > useable. What's the rationale for this approach? There's no requirement for the atkbd driver to be used for all keyboards. It seems very obscure (and backward) way to do things. Why not implement the serio driver for the IO level, and a separate keyboard driver which can handle the protocol and interpret the scancodes? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
