linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Tang Nguyen" <tang@netoriented.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: APC overflow
Date: Wed, 24 Mar 2004 19:33:55 -0800	[thread overview]
Message-ID: <001b01c4121a$00a24260$150a0a0a@netoriented.com> (raw)


Hi all,

I am porting 860sar version 2.2 on my system, which run @100Mhz for system
clock and @50Mhz for Bus clock.  The ESAR driver was initialized very
clean - but when I start passing UBR traffic, I always got APC overflow
interrupt.  The physical rate of my system is 2.3MHz - and I have configured
the PCR to 5424 - It should be OK but I have no idea why I got APC over flow
interrupt.  Any help and suggestion from you would be greatly appreciated.

-t


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

             reply	other threads:[~2004-03-25  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25  3:33 Tang Nguyen [this message]
     [not found] <A2959674806480.19317@webmail2.inner-21cn.com>
2004-03-25 22:05 ` APC overflow Tang Nguyen

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='001b01c4121a$00a24260$150a0a0a@netoriented.com' \
    --to=tang@netoriented.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).