From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Gorelik, Jacob (335F)" <jacob.gorelik@jpl.nasa.gov>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Linux on ppc440gp
Date: Thu, 07 Oct 2010 10:51:44 +1100 [thread overview]
Message-ID: <1286409104.2463.373.camel@pasglop> (raw)
In-Reply-To: <C8D1D750.272D%Jacob.Gorelik@jpl.nasa.gov>
On Wed, 2010-10-06 at 07:35 -0700, Gorelik, Jacob (335F) wrote:
> UIC0 (32 IRQ sources) at DCR 0xc0
> UIC1 (32 IRQ sources) at DCR 0xd0
That looks bad. Your device-tree probably. Check the DCR bindings.
I'm on vacation right now, I don't have time to review it in details,
but ask me again next week if you don't find some help in the meantime.
Cheers,
Ben.
next prev parent reply other threads:[~2010-10-06 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <75413B9E73E7F04B96503BC6DAF2C5D19054A3F20E@ALTPHYEMBEVSP30.RES.AD.JPL>
2010-10-06 14:35 ` Linux on ppc440gp Gorelik, Jacob (335F)
2010-10-06 23:51 ` Benjamin Herrenschmidt [this message]
2010-10-07 7:32 ` Stefan Roese
2010-10-07 8:03 ` Benjamin Herrenschmidt
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=1286409104.2463.373.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jacob.gorelik@jpl.nasa.gov \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).