Re: [android-kernel] Android Build

2012-09-13 Thread Chinmay V S
Some of the build steps can exceed the address space of 32-bit processes. e.g. handling the entire set of *.java source files in a single pass. Thus one might run into build errors due to the limitations of the 32bit system. This was rare in the days of FroYo. Starting with GB the recommended build

Re: [android-kernel] input framework and input_sync

2012-02-03 Thread Chinmay V S
Good :-) On Fri, Feb 3, 2012 at 3:23 PM, ajay wrote: > thanks ! It works now!! > On Feb 2, 2012 12:33 PM, "Chinmay V S" wrote: > >> AFAIK, input_sync() is always called after reporting input_report_xxx() >> functions. >> This way input events are

Re: [android-kernel] input framework and input_sync

2012-02-02 Thread Chinmay V S
AFAIK, input_sync() is always called after reporting input_report_xxx() functions. This way input events are flushed i.e reported to the userspace *immediately * as they occur in the hardware. This i have done in sensors and touchscreen kernel-drivers for Android. What is the problem you are facin