From: Vojtech P. <vo...@su...> - 2001-07-10 10:00:27
|
On Tue, Jul 10, 2001 at 10:22:09AM +0200, Richard Zidlicky wrote: > On Mon, Jul 09, 2001 at 08:12:03AM -0700, James Simmons wrote: > > > > > > > Do you know who know the atari and hp300 input hardware (keyboard, > > > > > mice, joysticks) well so we can port the drivers to the input layer for > > > > > ruby. I really like to wrap up support for this platform. > > > > > > > > The m68k kernel hackers of course :-) > > > > > > I can help about the atari input devices ... If you need help about > > > anything, just ask me. > > > > Great!! We pretty much toke code from the m68k tree and placed it into > > CVS:-( It needs to be converted over. How well do you understand the > > input api? > > isn't the input thing supposed to go into 2.5 ? I am responsible for > drivers/char/q40_keyb.c, will be probably pretty easy switch for me. > There is just a simple irq handler that produces AT scancodes and > acknowledges the irq. What makes the current driver so big is the > conversion AT->PC of scancodes which I hope will be done by the > input thing? Yes, exactly so. Actually the input AT keyboard driver uses AT (as opposed to PC/XT) scancodes natively, so no conversion needs to happen. Now, if you could do the switch before 2.5 (in the ruby tree), that'd help integrating the input stuff into 2.5 faster once 2.5 is out. Its hard adding infrastructure and breaking working drivers even in a development kernel, namely if the drivers are as important for use as keyboard or console. -- Vojtech Pavlik SuSE Labs |