linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sarnath  Kannan" <sparc64@rediffmail.com>
To: "ashish anand" <ashisha@india.infogain.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Re: "OpenPIC versus EPIC" in MPC8240 !
Date: 12 Nov 2001 08:41:14 -0000	[thread overview]
Message-ID: <20011112084114.25202.qmail@mailFA3.rediffmail.com> (raw)


Hi Ashish,
  what I felt was, populating reserved areas
is a bug. Thats what I accentuated. Moreover
I has said that this could be a __possible__
cause for getting bogus interrupts. I would
say there is 80% possibility.
 Moreover if u can read the EPIC manual,
u can notice that IVPR and SVPR both start
at  offset 0x50200. ( So the IVPR space is
not a continous 24 entries. It is actually
overalapped and discontinous )
 The EPIC manual clearly says "EPIC" is __adopted__
from OpenPIC specification . It never says it
conforms to the OpenPIC spec.
  I have no idea of hurting people. But if a bug
is pointed out, there is no harm in accepting it.

  lets put an end to this topic. I no more
want to discuss anything about this.

Good Luck
Sarnath


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

             reply	other threads:[~2001-11-12  8:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12  8:41 Sarnath  Kannan [this message]
2001-11-12 16:41 ` "OpenPIC versus EPIC" in MPC8240 ! Dan Malek
2001-11-12 16:51   ` Dag Nygren
2001-11-12 16:58     ` Dan Malek
2001-11-12 18:00       ` Dag Nygren
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13  4:00 Sarnath  Kannan
2001-11-07 14:11 Sarnath  Kannan

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=20011112084114.25202.qmail@mailFA3.rediffmail.com \
    --to=sparc64@rediffmail.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).