[PATCH] c-user: Add RTEID and ORKID references

[Joel Sherrill]

On Wed, Jun 19, 2019 at 6:17 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> ---
>  c-user/preface.rst | 14 ++++++++------
>  common/refs.bib    | 18 ++++++++++++++++++
>  2 files changed, 26 insertions(+), 6 deletions(-)
>
> diff --git a/c-user/preface.rst b/c-user/preface.rst
> index 47b030a..8723ed6 100644
> --- a/c-user/preface.rst
> +++ b/c-user/preface.rst
> @@ -27,12 +27,14 @@ been expended to provide standards addressing the
> needs of the real-time
>  community.  Several organizations have addressed this need during recent
> years.
>
>  The Real Time Executive Interface Definition (RTEID) was developed by
> Motorola
> -with technical input from Software Components Group.  RTEID was adopted
> by the
> -VMEbus International Trade Association (VITA) as a baseline draft for
> their
> -proposed standard multiprocessor, real-time executive interface, Open
> Real-Time
> -Kernel Interface Definition (ORKID).  These two groups are currently
> working
> -together with the IEEE P1003.4 committee to insure that the functionality
> of
> -their proposed standards is adopted as the real-time extensions to POSIX.
> +with technical input from Software Components Group
> +:cite:`Motorola:1988:RTEID`.  RTEID was adopted by the VMEbus
> International
> +Trade Association (VITA) as a baseline draft for their proposed standard
> +multiprocessor, real-time executive interface, Open Real-Time Kernel
> Interface
> +Definition (ORKID) :cite:`VITA:1990:ORKID`.  These two groups are
> currently
> +working together with the IEEE P1003.4 committee to insure that the
> +functionality of their proposed standards is adopted as the real-time
> +extensions to POSIX.
>

I don't know that we should say currently. This happened over 20 years ago.
It was also more like consensus could not be achieved by the RTOS vendors
participating and their attention shifted to POSIX as a more open standard.
Or at least one not based on their competition's API set.

Neither was officially adopted. They never left draft status.

insure -> ensure.

>
>  This emerging standard defines an interface for the development of
> real-time
>  software to ease the writing of real-time application programs that are
>

Let's change "emerging" to "proposed"


> diff --git a/common/refs.bib b/common/refs.bib
> index 7cc5121..25e4503 100644
> --- a/common/refs.bib
> +++ b/common/refs.bib
> @@ -16,6 +16,15 @@
>    year        = {1987},
>    url         = {
> http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf},
>  }
> + at manual{Motorola:1988:RTEID,
> +  author       = {Motorola},
> +  title        = {{Real Time Executive Interface Definition}},
> +  organization = {Motorola Inc., Microcomputer Division and Software
> Components Group, Inc.},
> +  note         = {DRAFT 2.1},
> +  year         = {1988},
> +  month        = {January},
> +  url          = {
> https://ftp.rtems.org/pub/rtems/people/joel/RTEID-ORKID/RTEID-2.1/RTEID-2_1.pdf
> }
> +}
>  @inproceedings{Lehoczky:1989:RM,
>    author      = {Lehoczky, J. and Sha, L. and Ding, Y.},
>    booktitle   = {Real-Time Systems Symposium},
> @@ -46,6 +55,15 @@
>    volume      = {39},
>    pages       = {1175-1185},
>  }
> + at manual{VITA:1990:ORKID,
> +  author       = {VITA},
> +  title        = {{Open Real-Time Kernel Interface Definition}},
> +  organization = {VITA, the VMEbus International Trade Association},
> +  note         = {Draft 2.1},
> +  year         = {1990},
> +  month        = {August},
> +  url          = {
> https://ftp.rtems.org/pub/rtems/people/joel/RTEID-ORKID/ORKID-2.1/ORKID-2_1.pdf
> }
> +}
>  @ARTICLE{Burns:1991:Review,
>    author      = {Burns, A.},
>    journal     = {Software Engineering Journal},
> --
> 2.16.4
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190619/4545c487/attachment-0002.html>