On 27.06.23 23:37, Kinsey Moore wrote:
     >   This directive blocks the calling task for the specified
    ``ticks`` of clock
     >   ticks if the value is not equal to
    :c:macro:`RTEMS_YIELD_PROCESSOR`.  When the
     > -requested interval has elapsed, the task is made ready.  The
    clock tick
> +requested number of ticks has elapsed, the task is made ready. The clock tick
     >   directives automatically updates the delay period.  The calling
    task may give
     >   up the processor and remain in the ready state by specifying a
    value of
     > -:c:macro:`RTEMS_YIELD_PROCESSOR` in ``ticks``.
     > +:c:macro:`RTEMS_YIELD_PROCESSOR` in ``ticks``.  Applications
    requiring use of a
     > +time base instead of system ticks should make use of
    ``nanosleep()`` or
     > +``clock_nanosleep()``.

    What is a time base?


A delay specified in some subunit of seconds instead of clock ticks.

What about:

Applications requiring use of a clock (CLOCK_REALTIME or CLOCK_MONOTONIC) instead of clock ticks should make use of the ...

--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to