From: Dan Malek <dan@mvista•com>
To: John F Davis <johndavi@us•ibm.com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: 405GP cat /proc/interrupts
Date: Mon, 22 Oct 2001 14:40:28 -0400 [thread overview]
Message-ID: <3BD4681C.C3FE8A8C@mvista.com> (raw)
In-Reply-To: OF8E67EA1A.B526D51D-ON85256AED.0064781F@raleigh.ibm.com
John F Davis wrote:
> .... With that said, why does cat /proc/interrupts say that I am
> using Edge Sensitive interrupts when I have
> modified the TR register to be Level sensitive?
Because the information printed by /proc/interrupts doesn't come directly
from the hardware registers, but rather (and irrelevant in this case) part
of the irq descriptor structure. You could set a bit in the irq descriptor
to make the print out pretty, but it won't have any effect on the system.
The proper solution is to set the the information in the irq descriptor,
and have the controller initialization read this and program the hardware
registers properly. You just skipped to the last step.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-10-22 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 18:24 405GP cat /proc/interrupts John F Davis
2001-10-22 18:40 ` 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=3BD4681C.C3FE8A8C@mvista.com \
--to=dan@mvista$(echo .)com \
--cc=johndavi@us$(echo .)ibm.com \
--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