summaryrefslogtreecommitdiffstats
path: root/doc/bsp_howto/clock.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>2007-12-11 15:51:35 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>2007-12-11 15:51:35 +0000
commitc52d534512079263e545b5aea1d41c98d293cab0 (patch)
tree5d834943cfbb5f80edad0016a3850c9a61bd7d87 /doc/bsp_howto/clock.t
parent2007-12-11 Joel Sherrill <joel.sherrill@OARcorp.com> (diff)
downloadrtems-c52d534512079263e545b5aea1d41c98d293cab0.tar.bz2
2007-12-11 Joel Sherrill <joel.sherrill@OARcorp.com>
* bsp_howto/clock.t, bsp_howto/init.t: Eliminate copies of the Configuration Table. Use the RTEMS provided accessor macros to obtain configuration fields.
Diffstat (limited to 'doc/bsp_howto/clock.t')
-rw-r--r--doc/bsp_howto/clock.t6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/bsp_howto/clock.t b/doc/bsp_howto/clock.t
index ee80ed228b..24a6812d4c 100644
--- a/doc/bsp_howto/clock.t
+++ b/doc/bsp_howto/clock.t
@@ -59,9 +59,9 @@ used as the source of the clock tick.
The device should be programmed such that an interrupt is generated
every @i{m} microseconds, where @i{m} is equal to
-@code{BSP_Configuration.microseconds_per_tick}. Sometimes the periodic interval
-timer can use a prescaler so you have to look carefully at your user's
-manual to determine the correct value.
+@code{rtems_configuration_get_microseconds_per_tick()}. Sometimes
+the periodic interval timer can use a prescaler so you have to look
+carefully at your user's manual to determine the correct value.
You must use the RTEMS primitive @code{rtems_interrupt_catch} to install
your clock interrupt service routine: