From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49E08F6F.8000604@domain.hid> Date: Sat, 11 Apr 2009 14:39:11 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <6C68EA7C-72E4-482D-917A-24C7C6DA31C9@domain.hid> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Running xeno-test List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Martin Shepherd Cc: xenomai@xenomai.org Martin Shepherd wrote: > On Fri, 10 Apr 2009, Steven Seeger wrote: >> It klat.ko installed? > > Yes, assuming that by this you mean xeno_klat.ko. I don't see klat.ko > without the xeno_ prefix in /lib/modules, and I opted for all of the > Xenomai testing drivers to be built by the kernel installation, apart > from irqbench. > > The pertinent section of the kernel .config file is: > > # > # Testing drivers > # > CONFIG_XENO_KLATENCY_MODULE=m > CONFIG_XENO_DRIVERS_TIMERBENCH=m > CONFIG_XENO_DRIVERS_KLATENCY=m > # CONFIG_XENO_DRIVERS_IRQBENCH is not set > CONFIG_XENO_DRIVERS_SWITCHTEST=m > > and lsmod shows the following Xenomai drivers as being loaded: > > $ lsmod | grep xeno > xeno_klat 5168 0 > xeno_timerbench 7172 0 > xeno_switchtest 6924 0 > > Thanks for the help, That is a long standing issue. The name of RTDM device (rttest0, rttest1, etc...) associated with the testing drives (timerbench, switchtest, etc...) is assigned dynamically when the driver is registered. But latency only tries to open the first device (rttest0). So, if by any chance xeno_switchtest was loaded before xeno_timerbench, latency fails to start. The cure is of course, to also try and find the testing device dynamically in latency, but this is not yet implemented. So, in the mean time, you should not load the drivers and let xeno-test load them once at a time when needed. -- Gilles.