For application style permissions, what you generally do is define a new gid that your device is published under (so it is not world readable/writeable), add an entry to etc/permissions.xml mapping that gid to a permission string, and add an item in the frameworks AndroidManifest.xml describing that permission.
(Sorry about not giving full paths to these things, I don't yet have these things at the tip of my fingers in the new tree layout we moved to for the open source release. :p) On Sun, Dec 7, 2008 at 10:48 AM, Luca Belluccini <[EMAIL PROTECTED]>wrote: > > I'm trying to create a fake character device. > I want to make it usable within the provided Android emulator. > > Firstly, I recompiled the Android Kernel editing the .config file, > adding CONFIG_MODULES. > Then, I wrote a module managing "/dev/mydev" (it acts as a 80 char > buffer) and crosscompiled it for arm architecture. > I ran the emulator and pushed busybox (for creating the /dev/mydev > with mknod) and loaded the module with insmod. > > Now, both shell and common activities can interact with it, by using > standard open/close/write/etc... > > I would like to create a specific permission for that device and make > it not readable from common Activities. > Is there some documentation/hints/links? > > I know Android has a specific HAL but there's no documentation. > Thank you. > > Luca > > > -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
