All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Luc Pamart <jlpamart@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] version of __ipipe_restore_pipeline_head
Date: Sat, 21 Apr 2007 22:20:48 +0200	[thread overview]
Message-ID: <462A7220.2020200@domain.hid> (raw)

Jean-Luc Pamart a écrit :
> Gilles Chanteperdrix a écrit :
>> Jean-Luc Pamart wrote:
>>  
>>> (...)
>>> realtimedriver: disagrees about version of symbol 
>>> __ipipe_restore_pipeline_head
>>> realtimedriver: Unknown symbol __ipipe_restore_pipeline_head
>>>
>>> My configuration :
>>> xeno 2.3
>>> hal 1.6-03
>>>     
>>
>> I hope you mean Adeos I-pipe 1.7-03, right ?
>>
>>   
>
> Well, not :-(   !
> I use the Adeos I-pipe 1.6-03 which is embedded with the xeno 
> distribution ...
> So, I decided to pass to linux 2.6.20 and Adeos I-pipe 1.7-03
> but after problems of compilation (My linux box is a 2.4 kernel one 
> apparently there is a binutils issue with the 2.4 kernel) I have tried 
> 2.6.19 and  Adeos I-pipe 1.7-03.
>
>  
>>> My linux version is 2.6.19
>>>
>>>
>>> We have __ipipe_restore_pipeline_head symbol in
>>> the kernel :
>>>
>>> c013f7b0 T __ipipe_restore_pipeline_head
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_native]
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_nucleus]
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_rtdm]
>>> c013f7b0 U __ipipe_restore_pipeline_head    [xeno_posix]
>>>
>>> but the module realtimedriver I want to insmod has
>>> been builded with the same sources.
>>>
>>>
>>> So what may I do ?
>>>     
>>
>> You likely changed a kernel option and recompiled the kernel without
>> recompiling the "realtimedriver" module. Try recompiling the module.
>>   
>
> Ok, I have change to 2.6.19 - Adeos I-pipe 1.7-03. After 2 days of
> building my emdedded distribution : all right !
> The realtimedriver can be load and user can be run.
>
> Nevertheless I have a slight but strange problem :
> When trying the user program with Timer int (#0)
> it says "cannot open demodev0"
> But when I change only inc.h like this :
> #define TIMER_INT       14 // for the hard disk
> or
> #define TIMER_INT       11 // for the net board
> it's ok : I have WRITE, READ etc. accordingly with
> the amount of work of the devices.
>
> I have a 100 Hz timer int.
> Perhaps too fast for the realtimedriver ???
> A idea ?
>
>
>
>
>




             reply	other threads:[~2007-04-21 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21 20:20 Jean-Luc Pamart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-18 13:19 [Xenomai-help] version of __ipipe_restore_pipeline_head Jean-Luc Pamart
2007-04-18 14:49 ` Gilles Chanteperdrix

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=462A7220.2020200@domain.hid \
    --to=jlpamart@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.