Re: [android-porting] resume issue

2011-04-19 Thread Robert Beckett
getting before the next suspend occurs. On 19/04/11 11:38, Ben Dooks wrote: On 19/04/11 10:17, Robert Beckett wrote: Im not sure what was intended in this situation, but the way I interpreted it was that this is as expected. If you are resumed because of an RTC alarm (e.g. something wants to

Re: [android-porting] resume issue

2011-04-19 Thread Robert Beckett
Im not sure what was intended in this situation, but the way I interpreted it was that this is as expected. If you are resumed because of an RTC alarm (e.g. something wants to check for updates at a given time), then it will want to go back in to suspend asap after checking its updates. If you

Re: [android-porting] How to download firmware in init?

2011-01-31 Thread Robert Beckett
unfortunately androids init process does not start processing firmware events until after it has started the early-init and init sections of the init.rc. The current behaviour will serialise all of the insmods in your init section, causing your driver to wait for a long timeout on the firmware.

Re: [android-porting] Thread Local Storage and GDB server

2010-11-15 Thread Robert Beckett
d_internal_t * pthi = (pthread_internal_t *)thread; +return pthi->tls; +} + On 04/11/10 15:41, Robert Beckett wrote: Hi, In porting android to our A8 cortext based board, we have enabled TLS. This works fine with bionic in general, however, it seems to cause problems with gdbserver. Looking a

[android-porting] Thread Local Storage and GDB server

2010-11-04 Thread Robert Beckett
Hi, In porting android to our A8 cortext based board, we have enabled TLS. This works fine with bionic in general, however, it seems to cause problems with gdbserver. Looking at the gdbserver source, it tries to get an address for td_thr_tls_get_addr, which is not implemented in bionics threa

[android-porting] Re: Anybody can tell me how the /dev/ folder under linux is mounted into android

2009-09-11 Thread Robert Beckett
The devices are created from system/core/init/devices.c as part of the init process. You can change the names in there if you wish. The names by default come from the uevent that the init process receives, but there is no reason why you couldnt change the name, or better still keep the default

[android-porting] Re: vold mounting non-mmc driver based disk

2009-09-01 Thread Robert Beckett
oogle please reply? > Or will we have to look inside vold code alone? > > Thks > > Tom > > > > > On 24 août, 13:15, Robert Beckett wrote: > >> Hello all, >> >> Does anyone know ifvoldcan be used like mountd to mount any generic >> bloc

[android-porting] vold mounting non-mmc driver based disk

2009-08-24 Thread Robert Beckett
Hello all, Does anyone know if vold can be used like mountd to mount any generic block device? I have an sd host that is not SD Host Controller Spec compliant, and the driver is not based on the linux mmc subsystem. With mountd it was trivial to get it to mount any block device. Is there a si