| To: | Johannes Stezenbach <js@convergence.de>, Kieran Fulke <kieran@pawsoff.org>, linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: IRQ problem on cobalt / 2.6.6 |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Sun, 16 May 2004 19:04:45 +0200 |
| In-reply-to: | <20040516152113.GA9390@convergence.de> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20040513183059.GA25743@getyour.pawsoff.org> <40A478B0.3070005@bitbox.co.uk> <20040516113622.GA14049@getyour.pawsoff.org> <20040516152113.GA9390@convergence.de> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Sun, May 16, 2004 at 05:21:13PM +0200, Johannes Stezenbach wrote: > In essence, I believe something other than the saa7146 must be asserting > irq 23. Or is it possible that a bug in the PCI init stuff in > saa7146_core.c can > cause this? Any hints how we could debug this would be welcome. arch/mips/cobalt/irq.c:cobalt_irq() looks pretty suspect. It connects CAUSEF_IP7 and interrupt 23 - but the CPU's builtin count / compare interrupt already uses this bit. Sharing the timer interrupt with something else isn't impossible but seems a less than bright thing to do. Somebody with production hw to test should compare this interrupt dispatch function with old working code from 2.2 or 2.4 ... Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IRQ problem on cobalt / 2.6.6, Johannes Stezenbach |
|---|---|
| Next by Date: | Re: IRQ problem on cobalt / 2.6.6, Kieran Fulke |
| Previous by Thread: | Re: IRQ problem on cobalt / 2.6.6, Johannes Stezenbach |
| Next by Thread: | Re: IRQ problem on cobalt / 2.6.6, Kieran Fulke |
| Indexes: | [Date] [Thread] [Top] [All Lists] |