X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=README.bertos;h=65edccce173bdbd65b734aafc134564f61c7e98c;hb=refs%2Ftags%2F2.2.0;hp=5abaa06dce362e39fb971cc637280fc446018878;hpb=943539779aa9509626c0c7a825c600d9a949839f;p=bertos.git diff --git a/README.bertos b/README.bertos index 5abaa06d..65edccce 100644 --- a/README.bertos +++ b/README.bertos @@ -1,14 +1,11 @@ /*! - -\if DEVELOPER_NOTE_ON - + \mainpage @@ -24,10 +21,11 @@ environments, from 8-bit processor to Linux and Win32 hosted application \section history History and Motivation -BeRTOS was born as a collection of useful, highly optimized and fine-tuned -libraries for embedded systems. Each library had its own scope and could be -used singularly in a project, though they were also meant to cooperate to -build the whole underlying software layer commonly called "operating system". +BeRTOS was born as a extremely modular, highly optimized and fine-tuned +operating system for embedded programming. +As a result, each module has its own scope and can be used alone or in +cooperation with other modules. +It's even possible to use most of the drivers without activating the kernel module. We have grown it following our guidelines: simplicity and beauty. These guidelines made it possible to evolve it in a full-featured real @@ -36,7 +34,7 @@ without giving up reliability and performace. To achieve the highest possible reusability, most BeRTOS components are designed for fine-grained modularity and minimal external dependencies. -Most non-essential features can be configured out for application with small +Most non-essential features can be configured out for applications with small memory footprint requirements. \section features Features