All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <kiszka@domain.hid>
To: "Martijn Hazenberg (GOVA)" <martijn@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: FW: [Xenomai-help] insmod: error inserting './xeno_posix.ko': -1         Unknown symbol in module
Date: Thu, 08 Dec 2005 13:35:33 +0100	[thread overview]
Message-ID: <43982895.6000701@domain.hid> (raw)
In-Reply-To: <439826C4.5010009@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

Heikki Lindholm wrote:
> 
>> Is the order in which the modules are loaded defined or can they be
>> loaded
>> at random order ?
> 
> Not random. First hal, then nucleus, then any of the skins. I have no
> experience with the 16550 serial module, though, and don't remember
> whether it was converted to use RTDM or not. If it wasn't, it'll
> probably come after hal, if you need it.

xeno_16550A is built on top of RTDM, so you need xeno_rtdm loaded first.
BTW, you can typically guess what module is missing by looking at the
unresolved symbol warnings in the kernel log. In case of 16550A, you
would get a bulk of unknown rtdm_xyz.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2005-12-08 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 11:42 FW: [Xenomai-help] insmod: error inserting './xeno_posix.ko': -1 Unknown symbol in module Martijn Hazenberg (GOVA)
2005-12-08 12:27 ` Heikki Lindholm
2005-12-08 12:35   ` Jan Kiszka [this message]
2005-12-08 12:42   ` Martijn Hazenberg (GOVA)
2005-12-08 12:45     ` Heikki Lindholm
2005-12-08 12:53     ` Gilles Chanteperdrix
2005-12-08 14:24       ` FW: [Xenomai-help] insmod: error inserting './xeno_posix.ko':-1 " Martijn Hazenberg (GOVA)
2005-12-08 16:42         ` Heikki Lindholm

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=43982895.6000701@domain.hid \
    --to=kiszka@domain.hid \
    --cc=martijn@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.