linux-mips
[Top] [All Lists]

Re: Mycable XXS board

To: "Pete Popov" <ppopov@mvista.com>
Subject: Re: Mycable XXS board
From: "Eric DeVolder" <eric.devolder@amd.com>
Date: Tue, 11 Mar 2003 15:43:38 -0600
Cc: "Bruno Randolf" <br1@4g-systems.de>, linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <3E689267.3070509@prosyst.bg> <20030307133919.P26071@mvista.com> <3E691514.7000907@embeddededge.com> <200303111130.57387.br1@4g-systems.de> <1047395856.5198.127.camel@zeus.mvista.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
Check linux/arch/mips/au1000/common/irq.c, in function init_IRQ().
Currently all the interrupt assignment are conditionalized per-board,
rather than per-cpu where appropriate. Unless you've changed this
file, I suspect many IRQ setups may be wrong.

Eric

Pete Popov wrote:
On Tue, 2003-03-11 at 02:30, Bruno Randolf wrote:
  
On Friday 07 March 2003 22:54, Dan Malek wrote:

    
That's what I wanted to clarify.  Are we discussing one of the on-chip
peripheral USB controllers of the Au1xxx, or is it a PCI USB controller
that was plugged into the Au1500.  In the case of the on-chip controller,
there aren't any interrupt routing problems, it's identical (and the same
code) on all Au1xxx boards.
      
we are discussing the on-chip USB controller for the mycable board. and its 
little endian...

any ideas where the assignment errors could come from in this case?
    
There wouldn't be any. So the problem is not irq assignment related.

I'm not what to suggest here but it feels like it might be a hardware
issue.  Try adding some printks (the abatron bdi jtag debugger works
great if you have one) and narrow down what's going on. Do you have any
jumpers on the board that are not setup correctly?


Pete



  

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