What is the exact purpose of CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER?

Joel Sherrill joel.sherrill at OARcorp.com
Tue May 13 14:19:54 UTC 2008


Fabrício de Novaes Kucinskis wrote:
>
> In RTEMS 4.7.1 C User’s Guide, item “Device Driver Table”, the 
> description of CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER is wrong – the 
> description there is the one for the 
> CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER.
>
>  
>
> I checked the on-line version of RTEMS 4.8.99 User’s Guide 
> (http://www.rtems.com/onlinedocs/doc-current/share/rtems/html/c_user/c_user00422.html), 
> and found something worse. This page has TWO descriptions for 
> CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER: the same one (and wrong) 
> described above, and this one, which I just couldn’t understand:
>
>  
>
> |“CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER| is defined when the 
> application does **NOT** want the Clock Device Driver and is **NOT** 
> using the Timer Driver. The inclusion or exclusion of the Clock Driver 
> must be explicit in typical user applications. This is intended to 
> prevent the common user error of using the Hello World example as the 
> baseline for an application and leaving out a clock tick source”
>
>  
>
> So, if I doesn’t want a Clock Driver, I say to RTEMS “application 
> needs clock driver”? Sorry, but I’m a little bit confused here.
>

Typo.  I recently added a macro which must be defined if you do not
want the clock driver configured.  It is a common user error to
build up from hello world and forget to add the clock driver.  With this
addition, it should be somewhat more difficult to make that mistake.

Thanks for reporting this.  The CVS online docs will update automatically
in a few hours.

Index: conf.t
===================================================================
RCS file: /usr1/CVS/rtems/doc/user/conf.t,v
retrieving revision 1.42
diff -u -r1.42 conf.t
--- conf.t      17 Apr 2008 22:45:57 -0000      1.42
+++ conf.t      13 May 2008 14:17:39 -0000
@@ -359,7 +359,7 @@
 defined.
 
 @findex CONFIGURE_APPLICATION_DOES_NOT_NEED_CLOCK_DRIVER
- at item @code{CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER} is defined
+ at item @code{CONFIGURE_APPLICATION_DOES_NOT_NEED_CLOCK_DRIVER} is defined
 when the application does @b{NOT} want the Clock Device Driver
 and is @b{NOT} using the Timer Driver.  The inclusion or
 exclusion of the Clock Driver must be explicit in typical


> Thanks in advance and best regards,
>
>  
>
>  
>
> Fabrício de Novaes Kucinskis - DEA / INPE
> --------------------------------------------------------------------
> Onboard Data Handling Group - SUBORD
> Aerospace Electronics Division
> Brazilian National Institute for Space Research
>
>  
>


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985





More information about the users mailing list