> Am 27.06.2015 um 15:14 schrieb Gilles Chanteperdrix 
> <[email protected]>:
> 
> On Sat, Jun 27, 2015 at 03:09:19PM +0200, Philippe Gerum wrote:
>> On 06/27/2015 02:22 PM, Michael Haberler wrote:
>>> ATM we're sorting through the machinekit xenomai3 transition on debian
>>> 
>>> I assume that users will continue to run xenomai2 kernels for a long time, 
>>> so we work towards separate (but hopefully coexisting-in-peace) packages 
>>> for Xenomai2 and Xenomai3 (startup is driven by kernel autodetection, so 
>>> booting a different kernel chooses the right runtime)
>>> 
>>> The libxenomai-dev and libxenomai1 in debian are all xenomai2 atm, but I 
>>> assume Xenomai3 equivalents will appear eventually
>>> 
>>> I hope these will be able to co-reside on the same host?
>>> 
>>> Ideally suggesting the Xenomai3 packages would be separate, be named 
>>> differently, and not supersede any installed Xenomai2 packages?
>>> 
>>> 
>>> (or am I blundering and I can run applications linked against the Xenomai3 
>>> libraries on a Xenomai2 kernel? my tests so far indicate - not)
>>> 
>> 
>> Not possible. Xenomai 2 uses kernel services provided by the I-pipe
>> compiled for legacy operation mode. Xenomai 3 wants this mode disabled.
> 
> The two kernels have different ABIs anyway. I think what Michael
> wants to do is to also have the two patched kernels installed and
> reboot (or kexec?) to switch from one to the other.

yes, it's a potential support issue, mostly for the folk installing from 
packages (I'm less concerned about those which install from source, and we can 
use configure.ac tests if something is obviously afoul)

what I see unfolding is:

- folks with a xeno2 package-based install want to try a xeno3 kernel, run 
apt-get upgrade etc, pull in kernel, and updated libraries
- something is not to their liking, and they step back to boot a xeno2 kernel - 
maybe just by changing the bootloader entry or by removing the xeno3 kernel
- if the first step has wiped the xeno2 userland support by upgrading, we have 
a support issue
- if xeno2 and xeno3 userland co-reside peacefully and separate, no issue

doing everything through the xeno wrapper looks doable, but I guess backporting 
this wrapper to xeno2 will be unpopular

what about completely separating the names, like /usr/xenomai3 ? sledgehammer 
approach (that is, in the best tradition of yankee engineering ;), but 
certainly effective.


- Michael




> 
> -- 
>                                           Gilles.
> https://click-hack.org


_______________________________________________
Xenomai mailing list
[email protected]
http://xenomai.org/mailman/listinfo/xenomai

Reply via email to