' one solution to allow the program to access the device driver' Are there other solutions? (interested in knowing the options) I shall try chmod.
On Oct 15, 2:16 am, "William W.-Y. Liang" <[email protected]> wrote: > 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 you have the device file named /dev/my_devfile. Set it > with the following command: chmod 0666 /dev/my_devfile. > > BRs, > William W.-Y. Liang > > 2011/10/15 Anil <[email protected]> > > > > > 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 Blaze board, /system/bin > > # ls -l > > -rwxrwxrwx system system 7636 2011-09-30 03:53 mydriver > > > What permissions does AndroidManifest.xml need to access a custom > > device driver? > > > Anil > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-kernel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
