From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4AF17E50.1000707@domain.hid> Date: Wed, 04 Nov 2009 14:14:56 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <20091020113724.9069.23594.stgit@domain.hid> <20091020113725.9069.28060.stgit@domain.hid> <1256404942.2862.498.camel@domain.hid> <1257177854.2065.616.camel@domain.hid> <4AEF0BCC.2020208@domain.hid> <1257180716.2065.618.camel@domain.hid> <4AEF0F7F.2060603@domain.hid> <4AEF1E91.6030407@domain.hid> <4AEF22C3.4070303@domain.hid> <4AEF273B.3090402@domain.hid> <20091102201924.5f392e15@domain.hid> <4AEF5D4B.2090106@domain.hid> <20091103082204.248eed59@domain.hid> In-Reply-To: <20091103082204.248eed59@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Xenomai on ARMadeus List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xenomai help gwenhael.goavec wrote: > On Mon, 02 Nov 2009 23:29:31 +0100 > Gilles Chanteperdrix > wrote: > >> gwenhael.goavec wrote: >>> On Mon, 02 Nov 2009 19:38:51 +0100 >>> Gilles Chanteperdrix >>> wrote: >>> >>>> By the way, did you make any change to the I-pipe patch to get it >>>> running on this board? >>> The only change realized, is made because Armadeus and >>> I-pipe does the same change on >>> mach-imx/include/mach/imxfb.h : >>> >>> --- a/arch/arm/mach-imx/include/mach/imxfb.h >>> +++ b/arch/arm/mach-imx/include/mach/imxfb.h >>> @@ -14,7 +14,6 @@ >>> #define PCR_BPIX_8 (3 << 25) >>> #define PCR_BPIX_12 (4 << 25) >>> #define PCR_BPIX_16 (4 << 25) >>> +#define PCR_BPIX_MASK (7 << 25) >>> #define PCR_PIXPOL (1 << 24) >>> #define PCR_FLMPOL (1 << 23) >>> #define PCR_LPPOL (1 << 22) >>> >>> I take this opportunity to ask a question: >>> on APF27 with imx27, I found that the system freeze >>> when an interrupt handler is in place and an >>> interruption happens. >>> if interrupt handler is in place without interruption no >>> problems and if interruption happens without interrupt >>> handler it's ok too. >>> >>> If someone could help or advise me. >>> thank you very much The reason I knew for this problem was if handle_edge_irq was used for some interrupts. But problems of this kind for IMX GPIOs are fixed in 1.3-03. Do you have this problem with in-kernel or out-of-tree drivers? With real-time or non real-time interrupts? Could you show us /proc/interrupts before the system freezes? -- Gilles