On Thu, May 07, 2009 at 09:07:42AM -0700, azilatlong wrote: > On Thu, May 7, 2009 at 4:14 AM, Sven Neumann <s.neum...@raumfeld.com> wrote: > > Hi, > > > > attached is a patch that implements driver_get_axis_info() for the > > linux-input driver. If we can reach consensus that this is a good thing > > to do, then I'd like to push this change to the git repository. > > > > > > Sven > > I tired something similar on my device but the values were never > populated... No matter what, they always returned invalid values, > that's why I made the limits parameters in the rc. I do like the idea > of pulling the info from the device approach much better but then > you're dependent on proper device driver initialization in populating > those values. Wouldn't it be a good idea to enable a third option to > override the EVIOCGABS? > > To put numbers to what I'm talking about - min/max values I'd record > out of my screen were ~30/900 while the min/max values obtained from > EVIOCGABS was 0/~1400. The end result was that I could only point to > ~ 62% of the screen.
You can change what the kernel will report w/ EVIOCSABS so need for ugly hacks in DirectFB. -- Ville Syrjälä syrj...@sci.fi http://www.sci.fi/~syrjala/ _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
