On Mon, Jul 26, 2010 at 07:59:56AM +0200, Cedric Sodhi wrote: > The device responds on the axes and the data is provided by X (xinput test > returns a 6 dimensional motion vector), the problem is that only two axes can > be CONFIGURED (for example button mapped) - at least the manual only mentions > X and Y axes, mouse still had a Z-axes for scroll which was one more. > > I can only attach my XOrg.log in a week or so because the computer where all > this setup was done is currently out of order but again, there should be no > problem, certainly no errors or warnings, evdev is loaded properly without > any complaints. > > Thanks for your reply!
So is what you're trying to say that it works fine in terms of passing all the axis events through, but you want to be able to map the other axes to buttons, actions, or? I still don't really understand what your actual problem is. Cheers, Daniel
signature.asc
Description: Digital signature
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
