linux-mips
[Top] [All Lists]

RE: PNX8550 Broken on Linux 2.6.24 - Interrupt issues?

To: <linux-mips@linux-mips.org>
Subject: RE: PNX8550 Broken on Linux 2.6.24 - Interrupt issues?
From: "Nico Coesel" <ncoesel@DEALogic.nl>
Date: Thu, 28 Feb 2008 14:05:11 +0100
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Thread-index: Ach6CZPq+1tVfxp4SauI+uOFteL44QAAL6mg
Thread-topic: PNX8550 Broken on Linux 2.6.24 - Interrupt issues?
Daniel,
I've had similar problems on the AU1100 platform. It turned out the
interrupt enumeration was faulty. You might want to check this.

Nico Coesel
 

> -----Oorspronkelijk bericht-----
> Van: linux-mips-bounce@linux-mips.org 
> [mailto:linux-mips-bounce@linux-mips.org] Namens Daniel Laird
> Verzonden: donderdag 28 februari 2008 13:58
> Aan: linux-mips@linux-mips.org
> Onderwerp: PNX8550 Broken on Linux 2.6.24 - Interrupt issues?
> 
> Hi all.
> 
> I have been happily using Linux 2.6.22.1 for ages on PNX8550 (STB810).
>  I have recently decided to step up and move onto Linux 2.6.24 series.
> However I am not getting very far. :-(
> It seems that all the clock stuff has changed again (since 
> 2.6.22.1) and this is causing issues.
> The board crashes as soon as local_irq_enable is called in main.c
> 
> I was wondering if anyone out there might also be running on 
> an STB810/JBS PNX8550 based system and have any ideas as to 
> why I am crashing.
> I know that PNX8550 does not enable the R4K Clock source 
> stuff as the chip is a bit 'special' and requires the two 
> timers to be used instead of one.
> 
> As far as I can see I think my interrupts are not being setup.
> 
> Any help, ideas etc are appreciated.
> 
> Daniel Laird
> 
> 

<Prev in Thread] Current Thread [Next in Thread>