linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: ashish anand <ashisha@india.infogain.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: sandpoint spurious interrupt problem.
Date: Tue, 01 May 2001 10:57:07 -0700	[thread overview]
Message-ID: <3AEEF8F3.8EDB36A7@mvista.com> (raw)
In-Reply-To: 3AEEF8BC.FE7CFAC@mvista.com


BTW, the linuxppc_2_5 should "just work" for the 750 if you have the switch
settings correct.

Mark
--

"Mark A. Greer" wrote:

> Did you start with the sandpoint port that is a part of linuxppc_2_5?  If not,
> you should.
> If so, double-check your switch settings.
>
> Mark
> --
>
> ashish anand wrote:
>
> > I am working towards porting linux on sandpoint with mpc750
> > I face the problem of continious spurious interrupts on booting
> > as per the base code SIOint is cascaded to EPIC in level triggered
> > mode , problem vanishes when i change it to edge triggered mode
> > also recall written in some intel document that external interrupts from
> > 8259 or equivalent pic's should be cascaded to APIC in edge triggered
> > mode only
> > why this requirement for cascading the interrupts from 8259 or other pic's
> > to APIC/EPIC
> > any comment on this will help me much
> >


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

      reply	other threads:[~2001-05-01 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01  7:39 sandpoint spurious interrupt problem ashish anand
2001-05-01 17:56 ` Mark A. Greer
2001-05-01 17:57   ` Mark A. Greer [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=3AEEF8F3.8EDB36A7@mvista.com \
    --to=mgreer@mvista.com \
    --cc=ashisha@india.infogain.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).