All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Hans-J. Ude" <ude@domain.hid>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] Module loading problems
Date: Wed, 09 Nov 2005 11:36:30 +0100	[thread overview]
Message-ID: <4371D12E.1000706@domain.hid> (raw)
In-Reply-To: <009101c5e516$02bd2a80$1000000a@domain.hid>

Hans-J. Ude wrote:
> I've installed Xenomai 2.0.1 but can't load a module stack for the vxWorks
> skin. Kernel is 2.6.13 with the included ipipe patch and I'm getting the
> following results.
> 
> # insmod xeno_hal.ko
> # insmod xeno_nucleus.ko
> # insmod xeno_vxworks.ko
> # insmod xeno_uvm.ko
> insmod: error inserting 'xeno_uvm.ko': -1 Function not implemented
> 
> # insmod xeno_hal.ko
> # insmod xeno_nucleus.ko
> # insmod xeno_uvm.ko
> # insmod xeno_vxworks.ko
> insmod: error inserting 'xeno_vxworks.ko': -1 Device or resource busy
> 

Vxworks and UVM modules are mutually exclusive. The VxWorks emulation in 
user-space on top of the UVM does not need the former, and even conflicts with 
it when attempting to set up the real-time timer. IOW, just push xeno_hal.ko, 
xeno_nucleus.ko and xeno_uvm.ko.

> I've put some printk's into the nucleus modules and found that in the first
> case there are two pointers which are compared when a subsequent modules is
> loaded. Those pointers are expected to be equal but are unequal and the
> module is rejected. Can someone tell what I can do here? Maybe there is
> something wrong with the modules, with the distro (Suse 9.3) or maybe I'm
> doing something wrong. I think i'm gonna try the original gnu modutils next
> and get rid of that Suse stuff.
> 
> regards,
> Hans
> 
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 

Philippe.


      reply	other threads:[~2005-11-09 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 10:11 [Xenomai-help] Module loading problems Hans-J. Ude
2005-11-09 10:36 ` Philippe Gerum [this message]

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=4371D12E.1000706@domain.hid \
    --to=rpm@xenomai.org \
    --cc=Xenomai-help@domain.hid \
    --cc=ude@domain.hid \
    /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.