From: Tom Rini <trini@kernel.crashing.org>
To: "Dayton, Dean" <deand@aiinet.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Irq 0 problem
Date: Sat, 7 Sep 2002 08:29:25 -0700 [thread overview]
Message-ID: <20020907152925.GA917@opus.bloom.county> (raw)
In-Reply-To: <638AA0336D7ED411928700D0B7B0D75B0189BAFA@aimail.aiinet.com>
On Fri, Sep 06, 2002 at 01:32:12PM -0400, Dayton, Dean wrote:
> I have been trying to port Linux 2.4.18-pre2 to the MPC8266ADS board. I
> grabbed the SCC uart.c from 2.5.31.
Why did you grab a file from 2.5.31? And is there any reason you aren't
using 2.4.18 final or 2.4.19 final instead ?
> The kernel loads and runs, the ramdisk is uncompressed and mounted. Then I
> take an interrupt with SIVEC=0. SIVEC is now 0 everytime it is read, this
> causes do_IRQ() to go into an endless loop.
[snip]
> - if (irq >= 0)
> + if (irq > 0)
> ppc_irq_dispatch_handler()
[snip]
> This appears to solve (or at least hide) my problem. Has anyone else run
> into this? I think it is occuring during the open of the console port (SCC
> 1). I ran into the same thing while trying to run on an EST8260 using an SMC
> as the console. Am I simply covering up a problem with a misconfigured
> device driver?
I think the problem is you're using a kernel which doesn't have the 8260
irq function updated to return -1 when there's nothing pending.. Can
you verify that this is a problem with 2.4.19 or 2.4.18 ?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-09-07 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 17:32 Irq 0 problem Dayton, Dean
2002-09-07 15:29 ` Tom Rini [this message]
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=20020907152925.GA917@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=deand@aiinet.com \
--cc=linuxppc-embedded@lists.linuxppc.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).