From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <451D18B2.3060007@domain.hid>
Date: Fri, 29 Sep 2006 08:59:30 -0400
From: "J.D. Yamokoski" <yamokosk@domain.hid>
MIME-Version: 1.0
Subject: Re: [Adeos-main] Problems booting after Adeos patch
References: <451AEEED.1050708@domain.hid> <451B0978.5020108@domain.hid>	
	<451BD6FC.9080205@domain.hid> <451BDADC.30101@domain.hid>	
	<1159454661.4982.20.camel@domain.hid> <451C0171.3020508@domain.hid>	
	<1159475242.4982.46.camel@domain.hid> <1159475501.4982.49.camel@domain.hid>
In-Reply-To: <1159475501.4982.49.camel@domain.hid>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: General discussion about Adeos <adeos-main.gna.org>
List-Unsubscribe: <https://mail.gna.org/listinfo/adeos-main>,
	<mailto:adeos-main-request@domain.hid>
List-Archive: </public/adeos-main>
List-Post: <mailto:adeos-main@gna.org>
List-Help: <mailto:adeos-main-request@domain.hid>
List-Subscribe: <https://mail.gna.org/listinfo/adeos-main>,
	<mailto:adeos-main-request@domain.hid>
To: rpm@xenomai.org
Cc: adeos-main@gna.org

Philippe Gerum wrote:
> On Thu, 2006-09-28 at 22:27 +0200, Philippe Gerum wrote:
> 
>> Ok, thanks. Just for the purpose of finding some grip on this issue,
>> could you:
>> 1) apply the patch below; I suspect some unwanted IRQ migration issue,
>> but can't prove it right now.
>> 2) if this patch does not solve the boot problem with CONFIG_PCI_MSI
>> enabled, then does disabling CONFIG_SMP improve the situation?
>>
>> TIA,
>>
> 
> Actually, this patch would be better for the purpose of testing.
> 
> --- 2.6.17-ipipe/kernel/irq/migration.c.orig	2006-09-28 22:28:20.000000000 +0200
> +++ 2.6.17-ipipe/kernel/irq/migration.c	2006-09-28 22:30:13.000000000 +0200
> @@ -17,6 +17,10 @@
>  	cpumask_t tmp;
>  	irq_desc_t *desc = irq_descp(irq);
>  
> +#ifdef CONFIG_IPIPE
> +	return;
> +#endif /* CONFIG_IPIPE */
> +
>  	if (likely(!desc->move_irq))
>  		return;
>  

Real quick, does it matter if I was using the Adeos I-pipe patch for 
kernel 2.6.15 when I ran into my problems? That patch looks like it is 
for 2.6.17 - But I can try either one.