Hi, Thanks for info, I loaded from "init.rc" with "insmod" command and mount at prompt; And I can read and write to the partition,which it works. Why do you think it did not load completely?
Thanks, -Sean On Sun, Jan 17, 2010 at 5:34 PM, feiyang yun <csd...@gmail.com> wrote: > hi, > maybe the driver isn't loaded completely(ie. the partition hasn't been > recognize) when mount execute > > 2010/1/16 sean <scr...@gmail.com> > >> Hi, >> I am trying to mount a formated ext3 partition on actual HW (zoom2 and >> qualcomm) >> after insmod inside of init.rc but it fails to mount. I tried >> different >> cases such as: >> 1. I did load module (insmod) followed by mount at user prompt; >> mount was successful. >> 2. I did load module (insmod) inside of init.rc and mount at user >> propmt; >> again it is successful to mount. >> 3. Build the driver inside of kernel and do mount inside of init.rc; >> result is successful to mount >> 4. Try to Load module (insmod) followed by mount inside of init.rc; >> result is failure to mount. >> >> My question is if there is any limitation to that in android >> environment? >> Would anybody have any suggestion to solve the issue of installing >> loadable >> module and mount at "init" section of the android initialization? >> -Sean >> >> -- >> unsubscribe: >> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >> website: http://groups.google.com/group/android-porting >> > > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting >
-- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
