Re: [Xenomai-core] [git pull] RTDM fixes and reworks
Jan Kiszka wrote: The following changes since commit 113ea4d56e8b215cb56ae7673013163ea5a5987d: Gilles Chanteperdrix (1): switchtest: increase stack sizes are available in the git repository at: git://git.xenomai.org/xenomai-jki.git for-upstream This is the first of likely three rounds of patches for 2.5.x. It mostly deals with introducing rtdm_rt_capable to replace the __xn_exec_conforming marks of RTDM syscalls and with deprecating RT open/socket/close for RTDM devices. The latter affects quite a few devices in our tree, so I'm CC'ing the maintainers to check if they see any problems in dropping RT creation/closure at this point. Besides some smaller fixes and an irqbench refactoring, this series also contains a solution for the confusions about incompatible rttestn devices. It simply avoids collisions be using different device names for the different device subclasses. switchtest already used another solution for that problem: the different devices use different ioctls. So, IMO we already had a solution for that issue. -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [git pull] RTDM fixes and reworks
Gilles Chanteperdrix wrote: Jan Kiszka wrote: The following changes since commit 113ea4d56e8b215cb56ae7673013163ea5a5987d: Gilles Chanteperdrix (1): switchtest: increase stack sizes are available in the git repository at: git://git.xenomai.org/xenomai-jki.git for-upstream This is the first of likely three rounds of patches for 2.5.x. It mostly deals with introducing rtdm_rt_capable to replace the __xn_exec_conforming marks of RTDM syscalls and with deprecating RT open/socket/close for RTDM devices. The latter affects quite a few devices in our tree, so I'm CC'ing the maintainers to check if they see any problems in dropping RT creation/closure at this point. Besides some smaller fixes and an irqbench refactoring, this series also contains a solution for the confusions about incompatible rttestn devices. It simply avoids collisions be using different device names for the different device subclasses. switchtest already used another solution for that problem: the different devices use different ioctls. So, IMO we already had a solution for that issue. Look at the diffstat of switchtest. I wanted to fix the issue for the rest without replicating code. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [git pull] RTDM fixes and reworks
Gilles Chanteperdrix wrote: Jan Kiszka wrote: Gilles Chanteperdrix wrote: Jan Kiszka wrote: The following changes since commit 113ea4d56e8b215cb56ae7673013163ea5a5987d: Gilles Chanteperdrix (1): switchtest: increase stack sizes are available in the git repository at: git://git.xenomai.org/xenomai-jki.git for-upstream This is the first of likely three rounds of patches for 2.5.x. It mostly deals with introducing rtdm_rt_capable to replace the __xn_exec_conforming marks of RTDM syscalls and with deprecating RT open/socket/close for RTDM devices. The latter affects quite a few devices in our tree, so I'm CC'ing the maintainers to check if they see any problems in dropping RT creation/closure at this point. Besides some smaller fixes and an irqbench refactoring, this series also contains a solution for the confusions about incompatible rttestn devices. It simply avoids collisions be using different device names for the different device subclasses. switchtest already used another solution for that problem: the different devices use different ioctls. So, IMO we already had a solution for that issue. Look at the diffstat of switchtest. I wanted to fix the issue for the rest without replicating code. I would agree with you for patches in xenomai-head. But in that case, this is an ABI breakage. It's internal testing stuff. If you think anyone out there may have written his own back- or front-end, I could make all test devices additionally register under the old rttestn as well. I just don't think it's worth the effort. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [git pull] RTDM fixes and reworks
Gilles Chanteperdrix wrote: Jan Kiszka wrote: Gilles Chanteperdrix wrote: Jan Kiszka wrote: Gilles Chanteperdrix wrote: Jan Kiszka wrote: The following changes since commit 113ea4d56e8b215cb56ae7673013163ea5a5987d: Gilles Chanteperdrix (1): switchtest: increase stack sizes are available in the git repository at: git://git.xenomai.org/xenomai-jki.git for-upstream This is the first of likely three rounds of patches for 2.5.x. It mostly deals with introducing rtdm_rt_capable to replace the __xn_exec_conforming marks of RTDM syscalls and with deprecating RT open/socket/close for RTDM devices. The latter affects quite a few devices in our tree, so I'm CC'ing the maintainers to check if they see any problems in dropping RT creation/closure at this point. Besides some smaller fixes and an irqbench refactoring, this series also contains a solution for the confusions about incompatible rttestn devices. It simply avoids collisions be using different device names for the different device subclasses. switchtest already used another solution for that problem: the different devices use different ioctls. So, IMO we already had a solution for that issue. Look at the diffstat of switchtest. I wanted to fix the issue for the rest without replicating code. I would agree with you for patches in xenomai-head. But in that case, this is an ABI breakage. It's internal testing stuff. If you think anyone out there may have written his own back- or front-end, I could make all test devices additionally register under the old rttestn as well. I just don't think it's worth the effort. No, the point is anyone out there with a 2.5.0 user-space Xenomai should be able to run it with Xenomai 2.5.3. So, there should be at least a Kconfig option to keep the old names. OK, that's fine. Will add a switch to register devices with the old names instead. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] [git pull] RTDM fixes and reworks
Jan Kiszka wrote: Gilles Chanteperdrix wrote: Jan Kiszka wrote: Gilles Chanteperdrix wrote: Jan Kiszka wrote: Gilles Chanteperdrix wrote: Jan Kiszka wrote: The following changes since commit 113ea4d56e8b215cb56ae7673013163ea5a5987d: Gilles Chanteperdrix (1): switchtest: increase stack sizes are available in the git repository at: git://git.xenomai.org/xenomai-jki.git for-upstream This is the first of likely three rounds of patches for 2.5.x. It mostly deals with introducing rtdm_rt_capable to replace the __xn_exec_conforming marks of RTDM syscalls and with deprecating RT open/socket/close for RTDM devices. The latter affects quite a few devices in our tree, so I'm CC'ing the maintainers to check if they see any problems in dropping RT creation/closure at this point. Besides some smaller fixes and an irqbench refactoring, this series also contains a solution for the confusions about incompatible rttestn devices. It simply avoids collisions be using different device names for the different device subclasses. switchtest already used another solution for that problem: the different devices use different ioctls. So, IMO we already had a solution for that issue. Look at the diffstat of switchtest. I wanted to fix the issue for the rest without replicating code. I would agree with you for patches in xenomai-head. But in that case, this is an ABI breakage. It's internal testing stuff. If you think anyone out there may have written his own back- or front-end, I could make all test devices additionally register under the old rttestn as well. I just don't think it's worth the effort. No, the point is anyone out there with a 2.5.0 user-space Xenomai should be able to run it with Xenomai 2.5.3. So, there should be at least a Kconfig option to keep the old names. OK, that's fine. Will add a switch to register devices with the old names instead. We need the other way around too: the new tools should be able to fall back to the old name scheme (so in particular, we should keep the switchtest portion, because it works better with the old name scheme). -- Gilles. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
