From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ivan Kalatchev" References: <001101ca930a$1052fa70$30f8ef50$@kalatchev@domain.hid> <4B4BADDD.7070900@domain.hid> <001f01ca9390$5fa20db0$1ee62910$@kalatchev@domain.hid> <4B4C84AC.3020207@domain.hid> <002001ca9399$99b07c40$cd1174c0$@kalatchev@domain.hid> <4B4C96D5.7060902@domain.hid> <003e01ca93cb$45fb6d30$d1f24790$@kalatchev@domain.hid> <4B4CE50D.20907@domain.hid> In-Reply-To: <4B4CE50D.20907@domain.hid> Date: Tue, 12 Jan 2010 16:27:47 -0500 Message-ID: <003f01ca93ce$170e7550$452b5ff0$@kalatchev@domain.hid> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: en-ca Subject: Re: [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: 'Gilles Chanteperdrix' Cc: 'Xenomai help' >=20 > Chained interrupt and muxed interrupt are the same thing. >=20 Then may be for Viper __ipipe_mach_irq_mux_p should be __ipipe_mach_irq_mux_p(irq)(((irq)=3D=3D IRQ_GPIO_2_x) || = ((irq)=3D=3Dgpio_to_irq(VIPER_CPLD_GPIO))) ? Then it would take care of viper handling CPLD IRQ automatically. Regards, Ivan