Design Policy
The design of the µT-Kernel specification is based on the policy of allowing easy optimization and adaptation of the µT-Kernel for small scaled embedded systems. However, taking compatibility with T-Kernel into account, it is also designed to improve the distribution and portability of device drivers or middleware.
For easy optimization and adaptation, functions not used in small systems and functions that add to the overheads of the whole system have been omitted. Functions for using resources effectively have been added. Also, unlike the T-Kernel, instead of retaining the unity of source code, the specification allows you to develop µT-Kernel in accordance with the requirements of the target systems.
For improving distribution and portability, similar to the T-Kernel, strong standardization of µT-Kernel ensures portability between different µT-Kernels. Further, unification of the interface with T-Kernel maintains high compatibility with T-Kernel. Specifically, the functions present in both µT-Kernel and T-Kernel are defined by the same interface, and the data type definitions in µT-Kernel are also common to T-Kernel. Therefore, using only the functions common to both µT-Kernel and T-Kernel, and writing programs according to the porting guidelines, allows you to port the program only by recompiling. A function present only in µT-Kernel may be a functional enhancement for T-Kernel, but it is a natural enhancement based on the T-Kernel format. So, when porting a program with that function to the T-Kernel, the program rarely needs to be modified.
Further, the purpose of including the device driver management system in the specification is to ensure distribution and portability. This allows you to create and utilize device drivers in the format common to T-Kernel, improving the distribution and portability of device drivers and applications.
Comments
Click here to Post a Comment