From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ivan Kalatchev" Date: Mon, 11 Jan 2010 13:22:15 -0500 Message-ID: <000101ca92eb$0146fdc0$03d4f940$@kalatchev@domain.hid> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01CA92C1.1870F5C0" Content-Language: en-ca Subject: [Xenomai-help] Viper board (ARM XScale) problems with Xenomai-2.4.10 List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xenomai-help@domain.hid This is a multi-part message in MIME format. ------=_NextPart_000_0002_01CA92C1.1870F5C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I was trying to upgrade my application running on Viper (2.6.16.28 kernel with xenomai 2.3.1) to kernel 2.6.30.10 with xenomai 2.4.10 and ran into couple of problems. 1. My application uses real-time hook to CPLD interrupt, which is chained interrupt. Xenomai 2.4.10 for some reason assigns general purpose interrupt handler to I-pipe acknowledgment handler : in kernel/irq/chip.c: ------=_NextPart_000_0002_01CA92C1.1870F5C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I was trying to upgrade my application running on = Viper (2.6.16.28 kernel with xenomai 2.3.1)  to

kernel 2.6.30.10 with xenomai 2.4.10 and ran into = couple of problems.

 

1. My application uses real-time hook to CPLD = interrupt, which is chained interrupt.

   Xenomai 2.4.10 for some reason assigns = general purpose interrupt handler to I-pipe  acknowledgment handler = :

 

in kernel/irq/chip.c:

 

         &= nbsp;    

 

------=_NextPart_000_0002_01CA92C1.1870F5C0--