From: Tom Rini <trini@kernel.crashing.org>
To: Anders Blomdell <anders.blomdell@control.lth.se>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PrPMC800 interrupt problem
Date: Thu, 24 Oct 2002 10:26:42 -0700 [thread overview]
Message-ID: <20021024172642.GL669@opus.bloom.county> (raw)
In-Reply-To: <37671D04-E772-11D6-A4F1-0003931C2BFA@control.lth.se>
On Thu, Oct 24, 2002 at 07:01:19PM +0200, Anders Blomdell wrote:
>
> When trying to use the linuxppc_2_4_devel on a PrPMC800, the system stops
> responding to external interrupts after the first serial interrupt. Many
> things works, since the system correctly gets its IP address via DHCP.
>
> The system handles a little more than 100 interrupts that gets routed to
> 'e100intr', then it starts up my shell that does a write to the console.
> This write triggers an interrupt that gets routed to 'rs_interrupt_single'
> . After this no more interrupts are received, but 'rs_interrupt_single' is
> called from the timer task in the serial driver, but the ethernet is
> totally dead. Anybody that has a good idea what to do about this?
Did you update the prpmc800_openpic_initsenses[] table and related?
(Look at how the lopec or sandpoint work now).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-24 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 17:01 PrPMC800 interrupt problem Anders Blomdell
2002-10-24 17:26 ` Tom Rini [this message]
2002-10-25 15:15 ` Anders Blomdell
2002-10-25 15:40 ` Tom Rini
2002-10-25 15:50 ` Anders Blomdell
2002-10-25 16:04 ` Tom Rini
2002-10-25 16:51 ` Matt Porter
2002-10-25 15:44 ` Anders Blomdell
2002-10-25 16:00 ` Tom Rini
2002-10-25 16:42 ` Anders Blomdell
2002-10-26 1:39 ` Tom Rini
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=20021024172642.GL669@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=anders.blomdell@control.lth.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.