linuxconsole-dev

Full m68k support.

[James S. <jsi...@tr...>]

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.

Re: Full m68k support.

[Geert U. <ge...@li...>]

On Sun, 8 Jul 2001, 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 :-)

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: Full m68k support.

[<fg...@en...>]

On Mon, 9 Jul 2001, Geert Uytterhoeven wrote:

> On Sun, 8 Jul 2001, 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.
>=20
> The m68k kernel hackers of course :-)

I can help about the atari input devices ... If you need help about
anything, just ask me.

just to know ... What's "ruby" ? :)


- Fran=E7ois Galea -

Re: Full m68k support.

[James S. <jsi...@tr...>]

> > > 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?

> just to know ... What's "ruby" ? :)

Ruby is the name of the kernel tree for the linux console project. The
linux console project is about rewriting the console system in the
following ways:

1) A new api for framebuffer drivers. Makes driver writing much easier 
   and it seperates the console layer from the framebuffer layer allowing
   the fbdev layer to run without a console system.

2) Use the input api has the backbone for the console system on the input
   side. It has the advantage of a simpler api, universal keymap, and
   access to a keyboard without a console system. 

3) Rewriting the serial layer in a similar fashion to parport. 

Other things come out of it like multihead.

Re: Full m68k support.

[Richard Z. <Ric...@st...>]

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?

Bye
Richard

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.

Re: Full m68k support.

[Vojtech P. <vo...@su...>]

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

Re: Full m68k support.

[James S. <jsi...@tr...>]

> isn't the input thing supposed to go into 2.5 ? 

Yes and no. You could convert it now and incorporate it into 2.4.X if
linus is willing to accept it.