diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html index eb5a9509d3..e76b2ce0a5 100644 --- a/Documentation/NuttxPortingGuide.html +++ b/Documentation/NuttxPortingGuide.html @@ -2541,7 +2541,7 @@ config ARCH_SIM

Since timers are a limited resource, the use of two timers could be an issue on some systems. - The job could be done with a single timer if, for example, the single timer were kept in a free-running at all times. Some timer/counters have the capability to generate a compare interrupt when the timer matches a comparison value but also to continue counting without stopping. If your hardware supports such counters, one might used the CONFIG_SCHED_TICKLESS_ALARM option and be able to simply set the comparison count at the value of the free running timer PLUS the desired delay. Then you could have both with a single timer: An alarm and a free-running counter with the same timer! + The job could be done with a single timer if, for example, the single timer were kept in a free-running at all times. Some timer/counters have the capability to generate a compare interrupt when the timer matches a comparison value but also to continue counting without stopping. If your hardware supports such counters, one might used the CONFIG_SCHED_TICKLESS_ALARM option and be able to simply set the comparison count at the value of the free running timer PLUS the desired delay. Then you could have both with a single timer: An alarm and a free-running counter with the same timer!

In addition to these imported interfaces, the RTOS will export the following interfaces for use by the platform-specific interval timer implementation: @@ -3041,7 +3041,7 @@ VxWorks provides the following comparable interface:

4.4.4 up_addrenv_select()

Function Prototype:

Description:

Returned Value:

@@ -3065,7 +3065,7 @@ VxWorks provides the following comparable interface:

4.4.5 up_addrenv_restore()

Function Prototype:

Description:

Input Parameters:

Returned Value: