On Wed, Jul 30, 2003 at 01:39:31PM +0400, "Andrey Borzenkov" wrote:
> yes, using /dev/input/mice on both 2.4 and 2.6 would help w.r.t.
> interoperability. Unless we care about 2.2.
PPC is already using this. /dev/usbmouse is a symlink to
/dev/input/mice. Works nicely and makes all of us laptop
[...]
> >
> > I do not understand the question. configuration method is drakmouse
> > or whatever. it does not depend on kernel. but it must emit something
> > suitable for both kernels.
>
> sorry for not being clear,
> what i meant is mousedrake makes a single configuration file,
> and probably
Quoting "\"Andrey Borzenkov\" " <[EMAIL PROTECTED]>:
>
> I probably have to add signature - I do not receive Cooker. Cc to me
> if you want me to respond.
>
> > just a short and dumb question,
> > how will be chosen the configuration method to use(2.4 or 2.6)
>
> I do not understand the questio
I probably have to add signature - I do not receive Cooker. Cc to me
if you want me to respond.
> just a short and dumb question,
> how will be chosen the configuration method to use(2.4 or 2.6)
I do not understand the question. configuration method is drakmouse
or whatever. it does not depend o
Pixel, are you back?
Problem.
In 2.4 every mouse device have own input driver with own major/minor.
So to configure mouse you just have to point it to correct device name -
it will be autoloaded by CONFIG_KMOD white magic or devfsd. I guess
some people may have never realized it :)
In 2.6 inpu
