Hi, Just out of interest, is there any actual use case here?
>From a technical POV, phones are short on resources and the software is mostly driven by user input. RT, in contrast, is often bad for resource usage and interactive workloads, because you have to expect WCET for many components. So you have to allocate resources for RT tasks, although you probably won't actually need them. In the end you'll achieve the opposite of what you intended. And please note that telephony runs on a separate CPU, which comes with an RT-enabled OS. Best regards Thomas On 28.03.2014 08:35, Debamitro Chakraborti wrote: > Hi Dave, > > On Fri, Mar 28, 2014 at 12:36 PM, Dave Hylands <[email protected] > <mailto:[email protected]>> wrote: > > Both Android and FxOS use garbage collected languages (Java for > Android, JavaScript for FxOS) which don't use realtime garbage > collectors, so even if the OS were realtime, it still wouldn't help > unless the portions of interest were written in languages which > don't need GC (like C or C++). > > > This is exactly what I had in mind. Possible approaches might be: > 1. Allow some apps to be written at a lower level and not use dynamic > memory management and GC > 2. Handle telephony operations by an interrupt, so that calling/texting > always overrides the rest of the app framework > I think we'll build a better mobile OS this way. My humble opinion only. > > Regards, > Debamitro > -- > http://about.me/debamitro > /don't polish your ignorance, it will shine/ > <http://www.ishafoundation.org/> > > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
