diff options
author | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2011-12-29 12:52:15 +0000 |
---|---|---|
committer | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2011-12-29 12:52:15 +0000 |
commit | e136368c1f2ee43476e597014900392023f3737d (patch) | |
tree | 39a24c0f788e5439a598b20bce102bcf471d44f2 /nuttx/TODO | |
parent | 67c0262d13cb87fa0898cf6d8aacc09c2c8b21db (diff) | |
download | px4-firmware-e136368c1f2ee43476e597014900392023f3737d.tar.gz px4-firmware-e136368c1f2ee43476e597014900392023f3737d.tar.bz2 px4-firmware-e136368c1f2ee43476e597014900392023f3737d.zip |
Correct last set of changes to configuration logic
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4237 7fd9a85b-ad96-42d3-883c-3090e2eb8679
Diffstat (limited to 'nuttx/TODO')
-rw-r--r-- | nuttx/TODO | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/nuttx/TODO b/nuttx/TODO index 4d65e6ce8..a4e9f1174 100644 --- a/nuttx/TODO +++ b/nuttx/TODO @@ -94,6 +94,23 @@ o Task/Scheduler (sched/) next interesting event time. That is one way to both reduce the timer interrupt overhead and also to increase the accuracy of delays. + + Current timer processing is in sched/sched_processtimer.c: + + 1) Calls clock_timer() which just increments a counter (the system + timer -- basically "up-time"). This is only used when code asks + for the current time. In a tickless OS, some substitute answer + for the question "What time is it?" would need to be developed. + You could use an RTC? Or maybe logic that gets the time until the + next interval expiration and computes the current time. The + solution is not too difficult, but depends on a hardware solution. + + 2) Calls wd_timer() which handles the link list of ordered events: + Each timer event is saved with the delta time to the next event + in the list. So an interval timer would be perfect to implement this. + + 3) sched_process_timeslice(). Then there is round-robin time-slicing. + Status: Open Priority: Low |