From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <55196DB0.8020308@xenomai.org> Date: Mon, 30 Mar 2015 17:37:20 +0200 From: Philippe Gerum MIME-Version: 1.0 References: <55196828.9020207@xenomai.org> <20150330152002.GL32766@hermes.click-hack.org> <55196B64.9010901@xenomai.org> <20150330152957.GN32766@hermes.click-hack.org> In-Reply-To: <20150330152957.GN32766@hermes.click-hack.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] There is XDDP Sockets support in kernel? List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: "Xenomai@xenomai.org" On 03/30/2015 05:29 PM, Gilles Chanteperdrix wrote: > On Mon, Mar 30, 2015 at 05:27:32PM +0200, Philippe Gerum wrote: >> On 03/30/2015 05:20 PM, Gilles Chanteperdrix wrote: >>> On Mon, Mar 30, 2015 at 05:13:44PM +0200, Philippe Gerum wrote: >>>> On 03/30/2015 04:55 PM, Helder Daniel wrote: >>>>> Hi, >>>>> >>>>> When trying to compile a kernel module that sets up a XDDP socket (code >>>>> snippet below) with Xenomai 3.x-rc3 on Cobalt setup, >>>>> rtdm_bind() returns ENOSYS. >>>>> This means that XDDP sockets can not be used in kernel? >>>>> >>>> >>>> No, in this case it likely means that you are calling it from a >>>> real-time context (i.e. a real-time kthread started with >>>> rtdm_task_create()). The binding op can only run from a non-rt context, >>>> e.g. module init code, regular kthread context, _nrt handler. >>> >>> Or that XDDP is not enabled in the kernel configuration, maybe? >>> >> >> It's an intra-kernel call, so it must be there. > > Not sure I follow. If RTDM is enabled in the kernel configuration, > and XDDP is not, then rtdm_bind will return -ENOSYS. > It's a binding operation, so if the code did receive a valid XDDP socket, the XDDP support must be there. -- Philippe.