The recently posted input-ps2 patch breaks if the serio and serport
object files in drivers/char/joystick are required only for PS/2
(i.e. they weren't enabled already for joysticks). And that brings
up the question: What the heck are those files doing in the joystick
driver dir in the first place?!
It seems to me that serio.c and serport.c belong in drivers/input more
than anywhere else. I'm enclosing a patch that handles just such a
relocation. The patch doesn't actually move the files ... that would
just inflate the patch, and it's a lot easier to just "mv" them.
Share & Enjoy!
--
Chip Salzenberg - a.k.a. - <[email protected]>
"We have no fuel on board, plus or minus 8 kilograms." -- NEAR tech
> The recently posted input-ps2 patch breaks if the serio and serport
> object files in drivers/char/joystick are required only for PS/2
> (i.e. they weren't enabled already for joysticks). And that brings
> up the question: What the heck are those files doing in the joystick
> driver dir in the first place?!
Well originally the only serial input devices where joysticks. As time
goes on this is not true any longer. We have several non joystick serio
based devices in CVS. Plus we use the serio setup for non serial but PIO
type input devices. PS/2 is a good example of such hardware. So yes I
agree serio.c and serport.c should be moved into drivers/input. I had this
problem when developing the h3600 touchscreen driver for the iPAQ using
the input api.
> It seems to me that serio.c and serport.c belong in drivers/input more
> than anywhere else. I'm enclosing a patch that handles just such a
> relocation. The patch doesn't actually move the files ... that would
> just inflate the patch, and it's a lot easier to just "mv" them.
Actually I like to see all input devices in drivers/input but last time I
suggested that it was shot down. In time they will be moved there. Either
that or drivers/char will be 95% input drivers.