All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 25 Oct 2002 18:39:09 -0700	[thread overview]
Message-ID: <20021026013909.GD30713@opus.bloom.county> (raw)
In-Reply-To: <BC199E78-E838-11D6-A4F1-0003931C2BFA@control.lth.se>


On Fri, Oct 25, 2002 at 06:42:22PM +0200, Anders Blomdell wrote:

> >What you're suggesting brings back the old hacking behavior.  Again I
> >say, look at what lopec_setup.c does for handling interrupts, look at
> >the manual for the prpmc800 (and the MPC107 (OpenPIC/EPIC related bits)
> >or MPC8240 (again, OpenPIC/EPIC)) manuals.
>
> OK, hope this is a correct solution then (it works, which is a good thing)
> . Thanks for your patience, all the levels in the interrupt handling are a
> bit hairy to understand.

This looks much better, I will commit this monday.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-10-26  1:39 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
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 [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=20021026013909.GD30713@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.