linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: vb <vb@vsbe.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPIC ISU
Date: Fri, 18 Jan 2008 10:44:58 -0800	[thread overview]
Message-ID: <f608b67d0801181044j352ee94dl50ea291164f4cb17@mail.gmail.com> (raw)
In-Reply-To: <57351E05-13DE-48F0-B0E5-28AADEF288A1@kernel.crashing.org>

Kumar,

thank you for your reply!

On Jan 18, 2008 7:54 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> >
> > What is it, at the very least - what does ISU stand for?
> >
> > I would really appreciate any hints,
>
> Interrupt service unit.  I believe its an IBM concept.
>
> For 8245 can you look at what the linkstation port is doing and mimic
> that.  I believe its an 8245 or 8241 so it should be close to what you
> need.
>

what platform is linkstation and what kernel version can I find it in?


TIA,
/vb

>          mpic = mpic_alloc(dnp, paddr, MPIC_PRIMARY |
> MPIC_WANTS_RESET, 4, 32, " EPIC     ");
>          BUG_ON(mpic == NULL);
>
>          /* PCI IRQs */
>          mpic_assign_isu(mpic, 0, paddr + 0x10200);
>
>          /* I2C */
>          mpic_assign_isu(mpic, 1, paddr + 0x11000);
>
>          /* ttyS0, ttyS1 */
>          mpic_assign_isu(mpic, 2, paddr + 0x11100);
>
>          mpic_init(mpic);
>
> - k
>

  reply	other threads:[~2008-01-18 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16  6:03 MPIC ISU vb
2008-01-18 15:54 ` Kumar Gala
2008-01-18 18:44   ` vb [this message]
2008-01-19 16:19     ` Kumar Gala
     [not found]       ` <f608b67d0801201216o60be67a1w3ead9714c3bba5aa@mail.gmail.com>
2008-01-20 20:32         ` Fwd: " vb

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=f608b67d0801181044j352ee94dl50ea291164f4cb17@mail.gmail.com \
    --to=vb@vsbe.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.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).