Re: Full m68k support.

[Franz S. <Fra...@la...>]

At 10:22 10.07.2001, 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?

It's really easy to write an input driver, just register your device to the 
input layer on module insertion and then use input_report_key() if you have 
a keypress/keyrelease to report. And you report "Linux" keycodes (already 
in 2.4 include/linux/input.h) which are linear (!) and thus usually easy to 
create using a table. In the ruby CVS there is a file named 
utils/scancodes.h which should be (is?) the reference for all the tables in 
the input layer. To use it, just run for example:

         cd utils
         gcc -Dfrom=atari -Dto=code gencodes.c -o gencodes_atari_to_linux
         ./gencodes_atari_to_linux

You get a nice table you can just copy and paste into your source.

Franz.