Apologies if you seen this already but it seems the list ate my previous
On Tuesday 01 July 2003 04:40 am, Neil Brown wrote:
> On Tuesday July 1, firstname.lastname@example.org wrote:
... skip ...
> > 1. Modify mousedev so if an input device announces that it generates both
> > relative and absolute events mousedev will discard all absolute axis
> > events and will rely on device supplied relative events.
> Nah. I have an ALPS dualpoint which generates ABSolute events for the
> touchpad part and RElative events for the pointstick part. I want
> them both.
So pass relative events as is and do conversion of absolute to relatives.
That's what I gonna do about my track stick as well.
Remember that mousedev provides _emulation_ of [Ex]PS/2 mouse protocol for
almost any device, it does not do any advanced tricks it's here to use with
old software that does not have advanced drivers yet, you are not "loosing"
your absolute mode packets, you hav /dev/input/eventX to access them.
> > 2. Add absolute->relative conversion code to touchpad drivers themselves
> > as drivers should know the best how to do that. If they turn out to be
> > similar across different touchpads then the common module could be
> > made.
> > What you think?
> I think that mousedev should be just clever enough to mostly work and
> no cleverer. Anything more interesting should be done in user-space.
Right, and if device says that it can generate relative packets mousedev
should not get in its way and do its own absolute->relative conversion.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 07 2003 - 22:00:13 EST