Symbian OS Internals (PDF)

Symbian Press Acknowledgments. About this Book. About the Authors. 1 Introducing EKA2. 1.1 The history of EKA2. 1.2 Basic OS concepts. 1.3 Symbian OS design. 1.4 Summary. 2 Hardware for Symbian OS. 2.1 Inside a Symbian OS phone. 2.2 System-on-Chip (SoC). 2.3 Random Access Memory (RAM). 2.4 Flash memory. 2.5 Interrupts. 2.6 Timers. 2.7 Direct Memory Access (DMA). 2.8 Liquid Crystal Display (LCD). 2.9 Audio. 2.10 Power management. 2.11 Summary. 3 Threads, Processes and Libraries. 3.1 What is a thread? 3.2 Nanokernel threads. 3.3 Symbian OS threads. 3.4 What is a process? 3.5 DProcess class. 3.6 Scheduling. 3.7 Dynamically loaded libraries. 3.8 Summary. 4 Inter-thread Communication. 4.1 Client-server ITC. 4.2 Asynchronous message queues. 4.3 Kernel-side messages. 4.4 Publish and subscribe. 4.5 Shared chunks and shared I/O buffers. 4.6 Summary. 5 Kernel Services. 5.1 Objects and handles. 5.2 Services provided to user threads. 5.3 Example user-accessible services. 5.4 Services provided by the kernel to the kernel. 5.5 Timers. 5.6 Summary. 6 Interrupts and Exceptions. 6.1 Exception types. 6.2 Exceptions on real hardware. 6.3 Interrupts. 6.4 Aborts, traps and faults. 6.5 Summary. 7 Memory Models. 7.1 The memory model. 7.2 MMUs and caches. 7.3 The memory model interface. 7.4 The memory models. 7.5 Programmer APIs. 7.6 Memory allocation. 7.7 Low memory. 7.8 Summary. 8 Platform Security. 8.1 Introduction. 8.2 Unit of trust. 8.3 Capability model. 8.4 Data caging. 8.5 Summary. 9 The File Server. 9.1 Overview. 9.2 The file server client API. 9.3 The file server. 9.4 File systems. 9.5 Summary. 10 The Loader. 10.1 E32 image file format. 10.2 ROM image file format. 10.3 The loader server. 10.4 Kernel-side code management. 10.5 Summary. 11 The Window Server. 11.1 The kernel's event handler. 11.2 Different types of events. 11.3 How WSERV processes events. 11.4 Processing key events. 11.5 Processing pointer events. 11.6 Client queues. 11.7 A simple handwriting animation DLL. 11.8

Jane Sales, Lead Author

Jane joined Symbian (then Psion) in 1995 to lad the team whose
goal was to create a new 32-bit operating system, now known as
EKA1. This goal was realized two years later, when the Psion Series
5 was released. Since then, Jane has taken on variety of roles
within Symbian, Including product management, systems architecture
and setting up a small product -focused research group in
Japan.

Jane Studied at Jesus college, Oxford, where she gained an NA in
mathematics in 1982. After that, she became part of a small team
building a microcomputer to which they ported CCPIM, It was he
start of a long-lasting love of systems programming.

In 2003, Jane Moved to the South of France and Began work on
this book She would like to thank her husband, Roger, for his moral
and financial support over the Succeeding 18 months.

Corinne Dive-Reclus

Corinne joined Symbian in 2001 after several years at Baltimore
Ltd, where she designed the embedded software of ACCE ( Advanced
Configurable Crypto Environment), a cryptographic hardware module
certified FIPS 140-1 Level 4.

In 1987, her first job was as a presales engineer at Sun
Microsystems France where she was exposed to the concept of Network
Computing & Internet and to its very first remote attacks - at
a time when this was still confidential. Being more interested in
development than presales, she subsequently worked as a software
engineer for Concepts and Implicit, developing an RAD )Rapid
Application Development) Programming Language for the creation of
distributed data-oriented applications. Since joining Symbian,
Corinne has been the Platform Security System Architect, and has
worked on the platform security architecture from its initial
design to its implementation in Symbain V9. To ensure that all
layers of the operating system will contribute to its overall
security, she worked extensively with Andrew Thoelke and Dennis May
to validate the security features of

Dieses eBook können Sie uneingeschränkt auf allen Geräten der tolino Familie lesen. Zum Lesen auf sonstigen eReadern und am PC benötigen Sie eine Adobe ID.