From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4FFBF7A0.7070601@xenomai.org> Date: Tue, 10 Jul 2012 11:36:32 +0200 From: Philippe Gerum MIME-Version: 1.0 References: <4FFBEA93.5070202@xenomai.org> <4FFBF197.4050203@xenomai.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] XDDP and inter-driver API. List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sunetra Sashi Cc: xenomai@xenomai.org On 07/10/2012 11:17 AM, Sunetra Sashi wrote: > > > On Tue, Jul 10, 2012 at 5:10 AM, Philippe Gerum > wrote: > ... > > I am making these calls from within the kernel, not from user space. > Hence I ended up using rtdm calls instead > > > > /dev/rtp0 is a non-real-time user-space endpoint for the > communication, between a regular linux application and a real-time > component. It does not make sense to open it from kernel space. > > > My intent here is to set up something similar to xddp-echo.c (RT - Non > RT communication) but in kernel space instead. How should I go about > creating the Linux endpoint for XDDP in the kernel? > There is no direct way for that, this device/protocol is not intended for this purpose. This is a regular linux application to Xenomai real-time communication path, nothing else. Regular linux applications live in userland, only. We don't recommend building applications in kernel space. > > > > > > Do I need to install any specific xenomai modules for > this to work? > > > Obviously, yes. Check IPC drivers in the "Drivers" sub-menu > of the > Xenomai configuration. You need to have > CONFIG_XENO_DRIVERS_RTIPC_XDDP enabled. > > > I already checked this in the configuration, It is enabled. > Should this > also be set to y? CONFIG_XENO_DRIVERS_RTIPC. In my configuration > it is > set to m. > > > Did you load the xeno_rtipc module then? > > > It is not loaded. But I got an error when I did that. > Xenomai: assertion failed at /.../kernel/xenomai/skins/) > Xenomai: RTDM: missing open handler It does not make any sense. This assertion can only trigger for a named device, not a protocol device. RTIPC is a protocol device. - did you change any of the driver code? - what command did you use to load the module, verbatim? > insmod: error inserting 'xeno_rtipc.ko': -1 Invalid parameters > > > > Should I see any modules loaded in > /proc/xenomai/rtdm/protocol___devices? > > > Yes. > > > > > Thanks > Shweta > ___________________________________________________ > Xenomai mailing list > Xenomai@xenomai.org > > > http://www.xenomai.org/____mailman/listinfo/xenomai > > > > > > > -- > Philippe. > > > > > > -- > Philippe. > > > -- Philippe.