On Sun, Dec 6, 2020 at 9:15 PM chensong via Xenomai <[email protected]> wrote:
> hi Philippe, > > As far as i know, some vxworks customers like xenomai because they can > move their RT processes from vxworks to linux without rewriting their > code by the help of vxworks skin. > > These are legacy vxworks applications? > If we "Excluding the legacy RTOS emulators such as VxWorks", we will > lose them. It could depend on the balance of the request and effort. > It might make sense to only support the vxworks skin, would any of these users be willing to help with support? -Greg > > BR > > song > > On 2020年12月06日 18:46, Philippe Gerum via Xenomai wrote: > > > > The common Xenomai platform specification is about defining the > > commonalities among future Xenomai releases starting from 3.3, including > > the Xenomai 4 series based on a next generation (EVL) core. A common API > > available to applications for issuing requests to the real-time core is > > part of this specification. > > > > Implementing such interface would not preclude other APIs from > > co-existing in particular releases. However, use of this common API > > only would guarantee portability > Excluding the legacy RTOS emulators > such as VxWorks and pSOS, Xenomai > > 3.x provides two main APIs, a POSIX-compliant one (libcobalt) and a > > custom RTOS API aka Alchemy (libalchemy) on top of the Copperplate > > interface. > > > > PROPOSAL: Pick libcobalt as the common API defined by the CXP. > > > > As a consequence, Xenomai 4 would provide two direct interfaces to the > > underlying EVL core: via the libevl API [1] which is readily > > available, and its own implementation of libcobalt as part of a CXP > > compliance. > > > > applications > > .................................... > > libalchemy libevl libcobalt > > | | | > > | | | > > libcopperplate | | > > | | | > > | | | > > libcobalt | | > > | | | > > v v v > > (Cobalt core) (EVL core) > > ----------- --------- > > Xenomai 3.x Xenomai 4 > > > > > > Thanks, > > > > [1] https://evlproject.org/core/user-api/ > > > >
