Thanx for your fast response.
I looked up the msm_defconfig and found that indeed both drivers are
active.
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_FUJITS
On Fri, Jan 8, 2010 at 9:07 AM, mibo wrote:
> And now the question: When I look at the board configuration file /
> android/msm/arch/arm/mach-msm/board-sapphire.c (I think this is for
> the HTC Dream phone) I can see there are two touchscreen drivers
> active:
>
> static struct i2c_board_info i2c_
Hi,
currently I'm trying to understand the chain how an input event from
touchscreen hardware is handled in the kernel and then reaches the
android stack and the applications.
So far I know that the chain downwards is:
User space:
InputDeviceReader (KeyInputQueue.java)
<== android_server_KeyInp
perumal316 wrote:
> Hi,
>
> I am writing a module that will print out the parameters of system
> calls. I want to do this for different system calls.
>
> Is it possible to write a config file to generalise the process? I
> tried searching the net but couldn't find any reference on doing such
> a
On Thu, Jan 7, 2010 at 11:58 PM, perumal316 wrote:
> Hi,
>
> I am writing a module that will print out the parameters of system
> calls. I want to do this for different system calls.
No, you really do not want to do that, just use strace instead if you
need this information.
See this very list y
Here is an example of a modules.conf I had lying around:
"# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignore
