Did somebody had problems with Android on NAND memory?

I'm facing some different behaviors in some points when compared to
boot from SD card (i.e Wi-fi connection, from NAND the system can't
resolve and IP address even detecting the AP and authenticating). I'm
guessing that is something related to system permissions. Maybe I'm
confusing the way I created UBI partition, by now I got
out/target/product/imx51_bbg/{root,system} [moving system/ to root/]
and created one UBIFS partition. My input configuration file for is:

  [system]
  mode=ubi
  image=rootfs.img
  vol_id=0
  vol_size=220MiB
  vol_type=dynamic
  vol_name=system
  vol_alignment=1

Using just one volume is the right choice? First I considered just
editing init.rc a creating a big "rootfs" volume (plus a "recovery"
one) but I'm considering if it's the best approach. Should I create
many entries like [root], [system], ... and:

mkfs.ubifs [...] -r root/ root.img
mkfs.ubifs [...] -r system/ system.mg
...

and finally "ubinizing":

ubinize -v -o android.ubi" [...] ubi.ini

My concern (besides the issues previously cited) is how I'll manage
the update. I would like to hear opinions on that.

Thanks.

--tm

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to