From 508b7bc93297fcb74af43b11b1435aa96add3c85 Mon Sep 17 00:00:00 2001 From: gdisirio Date: Thu, 25 Feb 2010 16:48:00 +0000 Subject: git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@1675 35acf78f-673a-0410-8e92-d51de3d6d3f4 --- docs/src/concepts.dox | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-) (limited to 'docs/src/concepts.dox') diff --git a/docs/src/concepts.dox b/docs/src/concepts.dox index b6a9e8630..e1d5f6156 100644 --- a/docs/src/concepts.dox +++ b/docs/src/concepts.dox @@ -18,8 +18,8 @@ */ /** - * @page concepts Concepts and Architecture - * @brief ChibiOS/RT Concepts and Architecture + * @page concepts Kernel Concepts + * @brief ChibiOS/RT Kernel Concepts * - @ref naming * - @ref api_suffixes * - @ref interrupt_classes @@ -28,7 +28,6 @@ * - @ref thread_states * - @ref priority * - @ref warea - * - @ref architecture * . * @section naming Naming Conventions * ChibiOS/RT APIs are all named following this convention: @@ -52,10 +51,10 @@ * @section interrupt_classes Interrupt Classes * In ChibiOS/RT there are three logical interrupt classes: * - Regular Interrupts. Maskable interrupt sources that cannot - * preempt the kernel code and are thus able to invoke operating system APIs - * from within their handlers. The interrupt handlers belonging to this class - * must be written following some rules. See the @ref system APIs group and - * @ref article_interrupts. + * preempt (small parts of) the kernel code and are thus able to invoke + * operating system APIs from within their handlers. The interrupt handlers + * belonging to this class must be written following some rules. See the + * @ref system APIs group and @ref article_interrupts. * - Fast Interrupts. Maskable interrupt sources with the ability * to preempt the kernel code and thus have a lower latency and are less * subject to jitter, see @ref article_jitter. Such sources are not @@ -246,17 +245,4 @@ * . * See the @ref core documentation for details, the area may change on * the various ports and some structures may not be present (or be zero-sized). - * - * @section architecture Architectural Diagram - * The following diagram shows the relationships among the hardware, the - * various ChibiOS/RT subsystems and the application code. - *

- * @image html arch.png - *
- * In this diagram the device drivers are at the same level of the application - * code because both have access to the system services and can directly - * access the hardware.
- * Of course it is possible to create in the application architecture several - * extra layers, this is just not part of the kernel architecture but part of - * the overall system design. */ -- cgit v1.2.3