From: ashish anand <ashisha@india.infogain.com>
To: Sarnath Kannan <sparc64@rediffmail.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: "OpenPIC versus EPIC" in MPC8240 !
Date: Mon, 12 Nov 2001 05:26:36 +0530 [thread overview]
Message-ID: <3BEF1034.EBBE37BC@india.infogain.com> (raw)
In-Reply-To: 20011107141124.12482.qmail@mailweb22.rediffmail.com
Sarnath Kannan wrote:
sorry for jumping in between as i was out on long leave.
there is absoluetely no relation of bogus interrupts
with "openpic_init" is populating reserved memory areas of EPIC.
even i agree "openpic_init" is populating reserved memory areas of EPIC may
need a second thought.
you should refrain from saying so firmly without tech. support for that.
Best Regards
Ashish
> Its not a "HACK" dan. Its a bug. Just verify
> the register layout of OpenPIC and EPIC. You
> will find that "openpic_init" is populating
> reserved memory areas of EPIC. No wonder, we get
> bogus interrupts. You can verify this in the code.
> Moreover Had the code really wanted seperation
> of vector spaces of OpenPIC and EPIC, it should have
> called "openpic_init" with
> "offset value = "NUM_8259_INTERRUPTS"
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-11 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 14:11 Re: "OpenPIC versus EPIC" in MPC8240 ! Sarnath Kannan
2001-11-11 23:56 ` ashish anand [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 6:42 James F Dougherty
2001-11-13 7:17 ` Dag Nygren
2001-11-12 8:41 Sarnath Kannan
2001-11-12 16:41 ` Dan Malek
2001-11-12 16:51 ` Dag Nygren
2001-11-12 16:58 ` Dan Malek
2001-11-12 18:00 ` Dag Nygren
2001-11-01 10:13 Sarnath Kannan
2001-11-01 17:13 ` Dan Malek
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=3BEF1034.EBBE37BC@india.infogain.com \
--to=ashisha@india.infogain.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sparc64@rediffmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.