Re: [Xenomai-help] Adeos patch prevents IRQ 384 (MMC Chip Detect) on omap-2.6.33

[Bob Feretich <bob.feretich@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

  Let me make sure I understand.
The most recent report from me contained console logs of two boots.
The first was 2.6.33 with no Adeos patch applied.
The second was 2.6.33 with the Adeos patch and Xenomai enabled 
(CONFIG_IPIPE=y) and CONFIG_XENOMAI=y).

You want me to perform to tests:

   1. 2.6.33 with the Adeos patch applied, but .config edited to turn
      off CONFIG_IPIPE and CONFIG_XENOMAI.
   2. Assuming test #1 passes the interrupts successfully, 2.6.33 with
      the Adeos patch applied, CONFIG_IPIPE=y, CONFIG_XENOMAI off, and
      revert the change to drivers/i2c/busses/i2c-omap.c.

Is that correct?

Regards,
Bob Feretich


On 7/24/2010 5:42 AM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>>    I have started a new thread with a name that better describes the
>> failure I am seeing. This may or may not be the reason I was seeing root
>> file system mount hang on omap-2.6.31 (previous thread).
> Ok. In the case where you have Adeos without Xenomai, do you have
> CONFIG_IPIPE enabled, if yes, then please verify that when CONFIG_IPIPE
> is disabled, you return in the same situation as without the I-pipe
> patch. Please also try enabling CONFIG_IPIPE and only removing the
> commit which "fixes" the spurious irqs.
>
>

[-- Attachment #2: Type: text/html, Size: 1844 bytes --]