public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista•com>
To: Ian Abbott <abbotti@mev•co.uk>
Cc: "'linuxppc-embedded@lists•linuxppc.org'"
	<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Possible bug in CPM interrupt handling
Date: Thu, 12 Oct 2000 12:53:02 -0400	[thread overview]
Message-ID: <39E5EC6E.D1CF00E2@mvista.com> (raw)
In-Reply-To: 00933BFA237CD2119B3400409543582704A275@MEV01


Ian Abbott wrote:
>
> In function cpm_interrupt (commproc.c), the last line is:
>
>         ((immap_t *)IMAP_ADDR)->im_cpic.cpic_cisr |= (1 << vec);

Oh crap, it that _still_ there?  Yes, you are correct, and I don't
know why I can't make this modification stick.  I'm going to push
it into the 2.4 BK tree right now.......

> If there are nested interrupts (are these allowed?) this makes sure
> only the specific interrupt we are dealing with is acknowledged.

Yes, they are allowed and this is a bug.  Thanks.


	-- Dan

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

      reply	other threads:[~2000-10-12 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-12 13:35 Possible bug in CPM interrupt handling Ian Abbott
2000-10-12 16:53 ` Dan Malek [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=39E5EC6E.D1CF00E2@mvista.com \
    --to=dan@mvista$(echo .)com \
    --cc=abbotti@mev$(echo .)co.uk \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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