From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4C4BE198.7030503@domain.hid>
Date: Sun, 25 Jul 2010 09:02:48 +0200
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
MIME-Version: 1.0
References: <4C43C83F.5030401@domain.hid>
	<4C43D265.9080609@domain.hid>	<4C43FC4F.3010006@domain.hid>
	<4C440D6F.1060204@domain.hid>	<4C44E9C9.3020600@domain.hid>
	<4C454C0C.6000100@domain.hid>	<4C4550C8.3070504@domain.hid>
	<4C45541C.5090507@domain.hid> <4C45CEE6.5000903@domain.hid>
	<4C460506.3010103@domain.hid> <4C46141F.50103@domain.hid>
	<4C468040.3030509@domain.hid> <4C468485.5060408@domain.hid>
	<4C47597F.1010406@domain.hid>
	<4C478313.2030606@domain.hid>
	<4C48C1BB.8080606@domain.hid> <4C48C2CE.1030706@domain.hid>
	<4C4A292F.5040900@domain.hid>
	<4C4ADFC6.1010900@domain.hid> <4C4B35F1.60103@domain.hid>
	<4C4B379F.9040107@domain.hid> <4C4BC6D6.8070806@domain.hid>
In-Reply-To: <4C4BC6D6.8070806@domain.hid>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect)
 on omap-2.6.33
List-Id: Help regarding installation and common use of Xenomai
	<xenomai.xenomai.org>
List-Unsubscribe: <https://mail.gna.org/listinfo/xenomai-help>,
	<mailto:xenomai-help-request@domain.hid>
List-Archive: </public/xenomai-help>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-help-request@domain.hid>
List-Subscribe: <https://mail.gna.org/listinfo/xenomai-help>,
	<mailto:xenomai-help-request@domain.hid>
To: Bob Feretich <bob.feretich@domain.hid>
Cc: xenomai@xenomai.org

Bob Feretich wrote:
>   Test 1 results:
> With the Adeos patch installed, but Adeos disabled, the system ran 
> normally. IRQ 384s were presented and serviced.  (The SD card removal 
> amd insertion was handled correctly.)
> 

That is reassuring.


> (...)
> Test 2 results:
> With the Adeos patch installed,  Adeos enabled, Xenomai disabled, the 
> spurious irpt patch reverted....
> The system ran normally, until an IRQ 384 occurred. Then continuous 
> spurious interrupts occurred.

Ok. So, we have a real issue, which the "fix" was just papering over.
Now, we just have to understand what happens. Thanks.

Note that the board still works when it displays the "spurious
interrupts" messages, only the serial console is rendered unusable by
the messages.

-- 
					    Gilles.