JFFS2 supports only read-only mmap. If that is a problem, you could try
UBIFS.
Now when mounting rootfs as yaffs2, the servicemanager dies/exits
almost immediately on android startup, and logcat output is shown
below. However, when mounting same rootfs via NFS, I don't see this
problem
is present
(/dev/ashmem), etc..
...Kd
-Original Message-
From: twebb [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 10:09 AM
To: Adrian Hunter
Cc: Deacon, Keith; linux-omap@vger.kernel.org Mailing List;
[EMAIL PROTECTED]; Mat Johnson
Subject: Re: android on omap
Ashmem is the Android shared memory subsystem. You can find it in the kernel
under mm/ashmem.c. There is a config option to turn it on and off. The
error indicates that it's having trouble with the driver - although it's not
specific as to exactly what. Make sure it's enabled, the
; linux-omap@vger.kernel.org Mailing List
Subject: Re: android on omap
Had problems with using NFS because Android tries to set specific
permission and ownership of files - and has a nasty habit of testing those
permissions frequently. If you have any local storage options - that
would help. Also
Had problems with using NFS because Android tries to set specific permission
and ownership of files - and has a nasty habit of testing those permissions
frequently. If you have any local storage options - that would help. Also,
check your init.rc file for things like mount trying to
seems to be fallout because it can't do what it wants
to now.
...Kd
-Original Message-
From: twebb [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2008 4:46 PM
To: Deacon, Keith; linux-omap@vger.kernel.org Mailing List
Subject: Re: android on omap
Had problems with using NFS
twebb,
As far as I know Android root file system cannot reside on
jffs2 partition as jffs2 does not have support for memory mapped IO.
One workaround may be to create an EXT2 image for the Android root FS
and place it in the jffs2 partition and try mounting it as loop
device. A brief
There is too little information to say much. Try running logcat (or just cat
/dev/log/main) to get more info. Since dalvik started, it probably has
something to do with the input config files or runtime database. File
permissions can also be and issue. Cleaning out the /data and
[Brian Swetland [EMAIL PROTECTED]]
I'm hoping to get a public git repository put together with the
various android-specific kernel patches (binder, logger, alarm drivers,
goldflish platform support, etc) soon. This should at least make
it easier for folks to merge various drivers 'n things
Hi,
Android is up and running on Mistral's OSK2530 EVM (based on
OMAP2430 SoC). We got the HW keypad functional for Android and we are
able to execute the the default applications shipped along with the
m5-rc14 sdk. The next thing would be to get the touchscreen and
networking
Hi,
Android is up and running on Mistral's OSK2530 EVM (based on
OMAP2430 SoC). We got the HW keypad functional for Android and we are
able to execute the the default applications shipped along with the
m5-rc14 sdk. The next thing would be to get the touchscreen and
networking functional
11 matches
Mail list logo
