I don't know if the 0/1 is enabled/disabled - looking at the source, that corresponds to a field called "prefix", which I think may have a different meaning - something to do with permissions. Neither the tree that I downloaded from google, or the tree from hackndev have a drivers/android/pmem.c file, but there's one here:
http://git.android.com/?p=kernel.git;a=tree;f=drivers/android;h=1612ef4de84a6a7f2639c235fdc3541983583dec;hb=HEAD What's up with that? On Nov 12, 3:37 pm, NickDG <[EMAIL PROTECTED]> wrote: > I too searched through the source for /dev/pmem and found this section > in system/core/init/devices.c > > { "/dev/pmem", 0660, AID_SYSTEM, AID_GRAPHICS, 0 }, > { "/dev/pmem_gpu", 0660, AID_SYSTEM, AID_GRAPHICS, 1 }, > { "/dev/pmem_adsp", 0660, AID_SYSTEM, AID_AUDIO, 1 }, > { "/dev/pmem_camera", 0660, AID_SYSTEM, AID_CAMERA, 1 }, > > Looks like 3 are enabled and 1 is disabled. I am going to disable the > other 3, re-compile and see if that will get us past the surface > flinger problem. > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
