Hi,
An Android program is typically run as a non-privileged process (with unique
user ID) from the perspective of the Linux kernel.
As a result, one solution to allow the program to access the device driver
is to grant read/write permission to the device files or sysfs files.
For example, assume y
I am calling the driver from an Android program (OMAP4/Blaze). It
calls a c++ program via JNI which then calls the device driver.
When I open the driver and write to it, I get a 'bad file number'
error.
Someone suggested it might be a permissions problem - the program is
running in user mode.
on B