next up previous contents
Next: Threads: Implementation Up: Implementation Framework Previous: rtker Initialization   Contents

Other Porting Issue

Apart from rewriting the three hardware dependent functions, porting rtker to a new CPU architecture also involves the following
  1. Porting the basic C library

    Our kernel requires a basic C interface to the chip for functions like malloc8.3, printf, stdlib functions.

    In case of x86 we took the C library of OSkit and stripped it down8.4. For the other two architectures (arm & trimedia), we used the C library that came with their SDK's.

  2. Writing a boot strap code

    The bootstrap code is responsible for initializing the processor, loading the OS image from ROM and then start executing the OS.

    For x86 we used the bootstrap code of OSkit. For the other two architecture, we didn't require a bootstrap code since we ran our OS on the simulator.

  3. Writing Device Drivers

    For the RTOS to do to any meaningful thing, it needs to interact with external devices, and hence would require device drivers.

    For x86, we ported the device drivers for ethernet, vga and bttv frame graber card to our kernel.

    For the other architecture, we only ran the producer consumer application and hence didn't require any device drivers.


next up previous contents
Next: Threads: Implementation Up: Implementation Framework Previous: rtker Initialization   Contents
Soumyadeb Mitra 2002-08-07