Re: [Xenomai-core] [patch 0/4] Support for select-like services.
On Mon, Feb 11, 2008 at 8:28 AM, Johan Borkhuis [EMAIL PROTECTED] wrote: Gilles, Gilles Chanteperdrix wrote: Hi, here comes a third edition of the patchset adding support for select. Could you tell me against which version this patch is tested? Would it work with 2.4.1, or do I need the latest version from SVN? The patch is against trunk. We would need to rework it a bit to adapt it to 2.4.1, but since it adds a new syscall, I do not know if it will be backported, though adding a syscall does not really break the ABI. -- Gilles Chanteperdrix ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] [patch 0/4] Support for select-like services.
Hi, here comes a third edition of the patchset adding support for select. The core support now depends on a CONFIG_XENO_OPT_SELECT option, whereas the posix support depends on a CONFIG_XENO_OPT_POSIX_SELECT option. The support for using rtdm_event_t and rtdm_sem_t objects is now built-in to these objects without creating new objects types (only if CONFIG_XENO_OPT_SELECT is enabled). The rtdm_context_get modification, allowing to check that the caller of a service belongs to the same process as the file descriptor it uses, is now made in __rtdm_context_get while rtdm_context_get passes a NULL first argument to this new service. When implementing these modifications, a few questions arise: - RTDM support currently depends on the CONFIG_XENO_OPT_SELECT option, should we add an RTDM specific option ? - in order to avoid numerous #ifdefs, and especially in drivers code, the new callback added to device operations for binding RTDM file descriptors to selector blocks is always there even if CONFIG_XENO_OPT_SELECT is disabled. Is it the right thing to do ? Regards. -- Gilles Chanteperdrix. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
