linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: paulus@samba.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: OpenPIC_NumInitSenses
Date: Thu, 24 Jan 2002 21:42:29 -0500	[thread overview]
Message-ID: <3C50C615.7090503@embeddededge.com> (raw)
In-Reply-To: 15439.64102.68217.293733@argo.ozlabs.ibm.com


Paul Mackerras wrote:

> Who was it that wanted this horrible hack in open_pic.c?

RTFA (archives :-).  We have discussed this enough in the past.

Just like the comment states, we need it because of the way the
107/EPIC maps on the "standard" OpenPIC structure.  The simple
answer is the interrupts are offset by 16 on the EPIC, so the
interrupt numbers don't match the offset value.  The EPIC may
say there are only 24 vectors, but for the code to work we need
to tell the OpenPIC code there are up to 16 more than that.


> I am about to add an openpic_set_sources function which will let us
> handle the distributed openpic in IBM pSeries machines more cleanly
> and also allow us to remove this hack.

There have been posts about better OpenPIC updates, but I guess they
have been ignored?

> Thus if you want to say how many interrupt sources there are, ....

I can't discuss much right now because I'm travelling with basically only
e-mail access.  I'll look at some code, but I guess you should just
make the changes and we'll try again to make EPIC fit :-).

Thanks.


	-- Dan


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

  parent reply	other threads:[~2002-01-25  2:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24 12:13 OpenPIC_NumInitSenses Paul Mackerras
2002-01-24 17:54 ` OpenPIC_NumInitSenses Adrian Cox
2002-01-25  2:42 ` Dan Malek [this message]
2002-01-25  4:04   ` OpenPIC_NumInitSenses Paul Mackerras
2002-01-25 17:07     ` OpenPIC_NumInitSenses 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=3C50C615.7090503@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.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).