|This article needs additional citations for verification. (May 2007) (Learn how and when to remove this template message)|
|License||Eclipse Public License|
Like its predecessor, EKA1, it has pre-emptive multithreading and full memory protection. The main differences are:
- Real-time guarantees (each API call is quick, but more importantly, time-bound)
- Multiple threads inside the kernel as well as outside
- Pluggable memory models, allowing better support for later generations of ARM instruction set.
- A "nanokernel" which provides the most basic OS facilities upon which other "personality layers" can be built
The main advantage of EKA2 was its ability to run full telephone signalling stacks. Previously, on Symbian phones, these had to run on a separate CPU. Such signalling stacks are extremely complex and rewriting them to work natively on Symbian OS is typically not an option. EKA2 therefore allows "personality layers" to emulate the basic primitives of other operating systems, thus allowing existing signalling stacks to run largely unchanged.
Real-time guarantees are a pre-requisite of signalling stacks, and also help with multimedia tasks. However, as with any real-time operating system, a full analysis of all threads is required before any real-time guarantees can be offered to anything except the highest-priority thread. (Higher priority threads may prevent lower-priority threads from running). Any multimedia task is likely to involve graphics, storage and/or networking activity, all of which are more likely to disrupt the stream than the kernel is.
Inside the kernel, EKA1 only allowed a single thread (plus a 'null' idle thread). EKA2 allows many threads. This makes it much easier to write device drivers that involve complex state machines, such as those for memory sticks or USB. Interrupts are handled with an interrupt service routine, which may request an immediate deferred function call (called as soon as the interrupts are processed), or a deferred function call, which is queued to run on a kernel thread. Either may in turn communicate with user-side threads.
Power management in EKA2 was largely unchanged from EKA1. The exact scheme varies between phones, but generally the null thread puts the CPU and peripherals to sleep, after having requested a wake-up whenever the next timer is due to expire.
EKA2 runs on ARM CPUs and the "WINS" emulator. (Unofficial ports exist for other CPUs). On the emulator, EKA2 provides somewhat better emulation than EKA1, in particular for the RProcess APIs which Symbian OS uses to represent processes. In EKA1 they didn't work at all on the emulator, which runs as a single Windows process.
Much of the credit for EKA2 goes to a single Symbian kernel engineer, who began the project as an experiment many years before it became an official part of Symbian OS.