From e3fa663a571ea5cbd4b43a37cc8de4e17ac7eebf Mon Sep 17 00:00:00 2001 From: scipio Date: Tue, 6 Feb 2007 00:16:15 +0000 Subject: [PATCH] MORE clarification. --- doc/html/tep107.html | 8 ++++++++ doc/txt/tep107.txt | 10 +++++++++- 2 files changed, 17 insertions(+), 1 deletion(-) diff --git a/doc/html/tep107.html b/doc/html/tep107.html index 907c5754..aa762beb 100644 --- a/doc/html/tep107.html +++ b/doc/html/tep107.html @@ -538,6 +538,14 @@ all three criteria. LED configuration is a special case: while it nominally meets all three criteria, the most important one is the third: as LEDs are often needed during SoftwareInit initialization, they must be set up before it is invoked.

+

Note that not all code which meets some of these criteria is wired through +PlatformC. In particular, criterion 1 is typically necessary but not +sufficient to require PlatformC. For example, a timer system that +configures overflow and capture settings or a UART stack that sets the +baud rate and transmission options can often be wired to SoftwareInit. +They are encapsulated abstractions which will not be invoked or +started until the boot event, and only need to be configured if the +system includes their functionality.

Components whose initialization does not directly depend on hardware resources SHOULD wire to MainC.SoftwareInit. If a component requires a specific initialization ordering, then it is responsible for diff --git a/doc/txt/tep107.txt b/doc/txt/tep107.txt index 3ea5ec68..221a8aa1 100644 --- a/doc/txt/tep107.txt +++ b/doc/txt/tep107.txt @@ -242,7 +242,6 @@ PlatformInit is for a small subset of initializations whose properties requires that they be performed separately. Initializations invoked through PlatformC meet some or all of the following criteria: - 1. The initialization requires configuring hardware resources. This implies that the code is platform-specific. 2. The initialization should always be performed. @@ -260,6 +259,15 @@ nominally meets all three criteria, the most important one is the third: as LEDs are often needed during SoftwareInit initialization, they must be set up before it is invoked. +Note that not all code which meets some of these criteria is wired through +PlatformC. In particular, criterion 1 is typically necessary but not +sufficient to require PlatformC. For example, a timer system that +configures overflow and capture settings or a UART stack that sets the +baud rate and transmission options can often be wired to SoftwareInit. +They are encapsulated abstractions which will not be invoked or +started until the boot event, and only need to be configured if the +system includes their functionality. + Components whose initialization does not directly depend on hardware resources SHOULD wire to MainC.SoftwareInit. If a component requires a specific initialization ordering, then it is responsible for -- 2.39.2