From: "Chuck Partridge" <Chuck_Partridge@amx.com>
To: "<" <linuxppc-embedded@lists.linuxppc.org>
Subject: SB Interrupt problem (OT)
Date: Wed, 17 Apr 2002 16:37:23 -0500 [thread overview]
Message-ID: <scbda4cd.072@mx.amx.com> (raw)
This may be off topic, but I am having problem with my custom 8245 board. We migrated an x86 design to a MPC8245 and kept the ALI M1535 Southbridge. the problem is that the 8259 interrupt controllers output always seems to be masked after a warm reset, but everything works fine from a cold boot.
When poking at the 8259 registers, they show that interrupts are ready but the INTR pin is never asserted to the 8245s EPIC, hence no interrupt.
After a cold boot, it will run fine until it resets. Once it resets, there are no interrutps reported by the INTR line to the EPIC (but internal EPIC interrupts like the internal DUART work fine).
Any ideas?
Thanks for indulging me on the OT message but I'm stumped..
CHuck
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-04-17 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 21:37 Chuck Partridge [this message]
2002-04-18 12:03 ` SB Interrupt problem (OT) Jerry Van Baren
-- strict thread matches above, loose matches on Subject: below --
2002-04-18 13:42 Chuck Partridge
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=scbda4cd.072@mx.amx.com \
--to=chuck_partridge@amx.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).