Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Peter Horton <phorton@bitbox.co.uk>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Kieran Fulke <kieran@pawsoff.org>, linux-mips@linux-mips.org
Subject: Re: IRQ problem on cobalt / 2.6.6
Date: Mon, 17 May 2004 09:40:33 +0100	[thread overview]
Message-ID: <40A87A81.5070100@bitbox.co.uk> (raw)
In-Reply-To: <20040516170445.GA4793@linux-mips.org>

Ralf Baechle wrote:

>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 ...
>
>  
>

I've got no hardware here but the code looks roughly similiar

As the Cobalt's use Galileo timer 0 for clock interrupts we could use 
Galileo rather than count/compare for the HPT.

Precision would be 50MHz rather than 125MHz but that shouldn't be a 
problem :-)

P.

  parent reply	other threads:[~2004-05-17  8:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 18:30 IRQ problem on cobalt / 2.6.6 Kieran Fulke
2004-05-14  7:43 ` Peter Horton
2004-05-16 11:36   ` Kieran Fulke
2004-05-16 15:21     ` Johannes Stezenbach
2004-05-16 15:21       ` Johannes Stezenbach
2004-05-16 17:04       ` Ralf Baechle
2004-05-16 17:11         ` Kieran Fulke
2004-05-16 17:21         ` Johannes Stezenbach
2004-05-16 18:04           ` Kieran Fulke
2004-05-17  8:40         ` Peter Horton [this message]
2004-05-17 11:46           ` Kieran Fulke
2004-05-17 11:57             ` Peter Horton
2004-05-17 12:04               ` Kieran Fulke
2004-05-17 12:20                 ` Peter Horton
2004-05-17 15:07 ` Stuart Longland
2004-05-18  7:34 ` Peter Horton
2004-05-18 17:39   ` Kieran Fulke
2004-05-18 20:59   ` Kieran Fulke
2004-05-18 21:09     ` Kieran Fulke
2004-05-18 21:12     ` Peter Horton
     [not found]       ` <20040518211810.GA29636@getyour.pawsoff.org>
2004-05-18 21:19         ` Kieran Fulke
2004-05-18 21:46           ` Kumba
2004-05-18 21:38         ` Peter Horton
2004-05-18 22:02           ` Kieran Fulke
2004-05-19 11:23     ` Maciej W. Rozycki
2004-05-19 12:57       ` Peter Horton
  -- strict thread matches above, loose matches on Subject: below --
2004-05-16 17:37 Kieran Fulke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40A87A81.5070100@bitbox.co.uk \
    --to=phorton@bitbox.co.uk \
    --cc=kieran@pawsoff.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox