From: Steve.Ferri@radisys.com
To: <acurtis@onz.com>
Cc: "Jean-Denis Boyer" <jdboyer@mediatrix.com>,
linuxppc-embedded@lists.linuxppc.org,
owner-linuxppc-embedded@lists.linuxppc.org
Subject: RE: Unhandled interrupt 0, disabled
Date: Fri, 3 May 2002 13:22:43 -0400 [thread overview]
Message-ID: <OFDC1ED295.5E02AFDD-ON85256BAE.005E00E8@radisys.com> (raw)
Allen,
We are using a PMC board that has the B.3 version of the 8260 along with
the
Tundra PowerSpan 420. I haven't seen any CP hang problems
with regards the on board PCI controller. The PowerSpan is connected to
the
8260's external interrupt line IRQ3. We are using a custom PCI driver
for host to daughter card communication, where the 8260 card is acting as
a daughter card.
Now working with the MCC devices on the B.3 version of the 8260 is another
story...
Regards,
Steve
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Ferri Radisys Corporation
Tel: 856 642-9229 x239 520 Fellowship Rd.
Fax: 856 642-0252 Suite C-304
www.radisys.com Mt. Laurel, NJ 08054
"Allen Curtis" <acurtis@onz.com>
Sent by: owner-linuxppc-embedded@lists.linuxppc.org
05/03/02 11:31 AM
Please respond to acurtis
To: "Jean-Denis Boyer" <jdboyer@mediatrix.com>, <Steve.Ferri@radisys.com>
cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Unhandled interrupt 0, disabled
> Just put the 'sync' in __sti().
> It seems to fix the problem on both 2.4.10 and 2.4.18,
> which are the versions I have tested.
>
> > I am using the B.3 version of the 8260
I know that this is unrelated but could you confirm whether B.3 and higher
fixes the CP hang problem when using an external PCI controller such as
the
PowerSpan.
Thanks
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-05-03 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 17:22 Steve.Ferri [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 15:22 Unhandled interrupt 0, disabled Jean-Denis Boyer
2002-05-03 15:31 ` Allen Curtis
2002-05-03 14:09 Jean-Denis Boyer
2002-05-03 13:03 Steve.Ferri
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=OFDC1ED295.5E02AFDD-ON85256BAE.005E00E8@radisys.com \
--to=steve.ferri@radisys.com \
--cc=acurtis@onz.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=owner-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).