All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Martin Shepherd <mcs@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Running xeno-test
Date: Sat, 11 Apr 2009 14:39:11 +0200	[thread overview]
Message-ID: <49E08F6F.8000604@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0904101729031.4820@domain.hid>

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.


  reply	other threads:[~2009-04-11 12:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 23:08 [Xenomai-help] Selecting the TSC Martin Shepherd
2009-04-09  0:11 ` Martin Shepherd
2009-04-09  2:49   ` Steven Seeger
2009-04-10 22:15   ` [Xenomai-help] Xeno-test bug Martin Shepherd
2009-04-11  0:20     ` [Xenomai-help] Running xeno-test Martin Shepherd
2009-04-11  0:24       ` Steven Seeger
2009-04-11  0:35         ` Martin Shepherd
2009-04-11 12:39           ` Gilles Chanteperdrix [this message]
2009-04-11 20:00             ` Martin Shepherd
2009-04-11 20:07               ` Gilles Chanteperdrix
2009-04-12  2:02                 ` Martin Shepherd
2009-04-12  9:11                   ` Gilles Chanteperdrix
2009-04-12 17:40                     ` Gilles Chanteperdrix
2009-04-12 19:10                     ` Martin Shepherd
2009-04-12 19:23                       ` Gilles Chanteperdrix
2009-04-16  3:20                         ` Martin Shepherd
     [not found]                           ` <4F0B1E98-862D-4031-B22E-D7DAEA554EEB@comcast.net>
     [not found]                             ` <Pine.LNX.4.64.0904161059220.24221@domain.hid>
2009-04-16 18:43                               ` Steven Seeger
2009-04-16 22:18                                 ` Martin Shepherd
2009-04-17  2:50                                 ` Martin Shepherd
     [not found]                           ` <1239872431.5845.25.camel@domain.hid>
     [not found]                             ` <Pine.LNX.4.64.0904161537400.26955@domain.hid>
2009-04-17  8:01                               ` Vikesh Rambaran
2009-04-17 12:57                           ` Gilles Chanteperdrix
2009-04-17 23:34                             ` Martin Shepherd
2009-04-19  5:15                             ` Martin Shepherd
2009-04-12 10:31     ` [Xenomai-help] Xeno-test bug Gilles Chanteperdrix
2009-04-12 10:36     ` Gilles Chanteperdrix
2009-04-12 18:52       ` Martin Shepherd
2009-04-12 19:25         ` Gilles Chanteperdrix
2009-04-13  0:42           ` Martin Shepherd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49E08F6F.8000604@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=mcs@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.