All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Ivan Kalatchev <ivan.kalatchev@domain.hid>
Cc: 'Xenomai help' <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Viper board (ARM XScale) problems with	Xenomai-2.4.10
Date: Tue, 12 Jan 2010 17:16:54 +0100	[thread overview]
Message-ID: <4B4CA076.1050205@domain.hid> (raw)
In-Reply-To: <002101ca93a1$a39d4050$ead7c0f0$@kalatchev@domain.hid>

Ivan Kalatchev wrote:
>> Ok, what version of gcc/binutils ? You can workaround this build
>> issue, by using the generic implementation of xnarch_nodiv_llimd.
>> In incldude/asm-arm/arith.h, replace
>> 
>> #if __LINUX_ARM_ARCH >= 4 with #if __LINUX_ARM_ARCH >= 4 &&
>> __GNUC__ >= 4
>> 
> 
> 
> my gcc is 3.3.4
> 
> I changed arith.h as you suggested, and it compiled, but then linker
> couldn't find rthal_arm_nodiv_ullimd definition, as there is no  code
> for it for __GNUC__ < 4.

Ok, you need to change the other #ifdef a bit further.

> 
> 
>> Please try what I told you: replacing handle_irq with 
>> __ipipe_handle_irq
> 
> I need CPLD MUX interrupts (which are ISA interrupts in my case) to
> be real-time. How that should be done then - request real-time CPLD
> interrupt with empty handler and request each ISA interrupt as
> real-time handler as well?

No, just requet the ISA interrupt you want to use. Do not touch the mux
interrupts parent. This should work transparently.

-- 
Gilles Chanteperdrix, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com


  reply	other threads:[~2010-01-12 16:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 22:04 [Xenomai-help] Viper board (ARM XScale) problems with Xenomai-2.4.10 Ivan Kalatchev
2010-01-11 23:01 ` Gilles Chanteperdrix
2010-01-12 10:29   ` Gilles Chanteperdrix
     [not found]   ` <001f01ca9390$5fa20db0$1ee62910$@kalatchev@domain.hid>
2010-01-12 14:18     ` Gilles Chanteperdrix
2010-01-12 15:12       ` Ivan Kalatchev
2010-01-12 15:35         ` Gilles Chanteperdrix
2010-01-12 16:09           ` Ivan Kalatchev
2010-01-12 16:16             ` Gilles Chanteperdrix [this message]
2010-01-12 17:39               ` Ivan Kalatchev
2010-01-12 17:43                 ` Gilles Chanteperdrix
2010-01-12 20:04                 ` Gilles Chanteperdrix
2010-01-12 20:34                   ` Ivan Kalatchev
2010-01-12 22:40                   ` Ivan Kalatchev
2010-01-12 22:42                     ` Gilles Chanteperdrix
2010-01-12 22:48                       ` Ivan Kalatchev
2010-01-12 22:52                         ` Gilles Chanteperdrix
2010-01-12 23:28                         ` Gilles Chanteperdrix
2010-01-13  0:20                         ` Gilles Chanteperdrix
2010-01-13 13:55                           ` Ivan Kalatchev
2010-01-13 13:59                             ` Gilles Chanteperdrix
2010-01-12 21:07           ` Ivan Kalatchev
2010-01-12 21:09             ` Gilles Chanteperdrix
2010-01-12 21:27               ` Ivan Kalatchev
2010-01-12 21:30                 ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2010-01-11 18:22 Ivan Kalatchev
2010-01-11 18:28 ` 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=4B4CA076.1050205@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=ivan.kalatchev@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.