Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulf Carlsson <ulfc@bun.falkenberg.se>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>, ralf@uni-koblenz.de
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: HAL2 interrupt
Date: Thu, 29 Oct 1998 11:12:11 +0100	[thread overview]
Message-ID: <19981029111211.B28553@zigzegv.ml.org> (raw)
In-Reply-To: <19981028232652.A2587@alpha.franken.de>; from Thomas Bogendoerfer on Wed, Oct 28, 1998 at 11:26:52PM +0100

On Wed, Oct 28, 1998 at 11:26:52PM +0100, Thomas Bogendoerfer wrote:
> On Wed, Oct 28, 1998 at 12:59:01AM +0100, Ulf Carlsson wrote:
> > Now I'm asking again, do you know which interrupt number I should request for
> > the PBUS DMA:s. I can't handle the interrupts correctly without the knowledge of
> 
> for me it looks like SGINT_HPCDMA should be the first PBUS DMA interrupt.
> But looking further into the indyIRQ.S and indy_int.c indicates, that these
> interrupts aren't implemented, yet.

The problem is that the sgiseeq and the sgiwd93 use HPC DMA as well, but they're
sharing local interrupt 0 (MIPS IRQ 2), and using some status register to
differentiate them. If I were writing a sgiwd93 driver or a sgiseeq driver, my
first guess would have been that they were using the SGINT_HPCDMA interrupts.

Well, looks like I'm out of luck, I'll do some trial & error.

Ralf?

- Ulf

  reply	other threads:[~1998-10-29 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-27 23:59 HAL2 interrupt Ulf Carlsson
1998-10-28 22:26 ` Thomas Bogendoerfer
1998-10-29 10:12   ` Ulf Carlsson [this message]
1998-10-29 22:10     ` Thomas Bogendoerfer
1998-10-29 22:29       ` Ulf Carlsson

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=19981029111211.B28553@zigzegv.ml.org \
    --to=ulfc@bun.falkenberg.se \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    --cc=tsbogend@alpha.franken.de \
    /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