On Wed, 30 Aug 2000, Trevor Woolven wrote:
[... (in)compatibilities between RTL and RTAI...]
> However, LineoISG (for whom I work - formerly called Zentropix) have
> developed a Common API compatibility layer (it's actually a header
> file) which allows users to write one set of code that can then be
> used to run either RTAI or RTL.
>
> The general idea is that users can now take the same application
> code and use whichever underlying Real-Time Linux they want. They
> can also migrate between them as functionality and features
> change/improve etc.
How well does this common API follows the evolution of both forks? I
mean, if RTL comes out with version 3.0, how fast will the common API
follow this new version? Or will it, by definition, be a greatest
common divisor of the functionality of both forks?
> We would like to see a *real* common API but that starts to get far
> too political, so for the forseeable future we will maintain our
> compatibility header and try to keep up with the changes.
Shouldn't this *real* API be the POSIX-compliant one that RTL is
trying hard to follow as far as reasonably possible? Or am I stating
things a bit too simply here...
--
[EMAIL PROTECTED] (Ph.D.) Fax: +32-(0)16-32 29 87
Dept. Mechanical Eng., Div. PMA, Katholieke Universiteit Leuven, Belgium
Real Time and Embedded HOWTO:
<http://www.mech.kuleuven.ac.be/~bruyninc/rthowto/index.html>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
