From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ulf Carlsson <ulfc@bun.falkenberg.se>, ralf@uni-koblenz.de
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: HAL2 interrupt
Date: Thu, 29 Oct 1998 23:10:09 +0100 [thread overview]
Message-ID: <19981029231009.A3756@alpha.franken.de> (raw)
In-Reply-To: <19981029111211.B28553@zigzegv.ml.org>; from Ulf Carlsson on Thu, Oct 29, 1998 at 11:12:11AM +0100
On Thu, Oct 29, 1998 at 11:12:11AM +0100, Ulf Carlsson wrote:
> The problem is that the sgiseeq and the sgiwd93 use HPC DMA as well, but they're
yes, but they aren't using PBUS DMA channels, because they aren't connected
to the PBUS.
> 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.
SCSI and ethernet are special HPC devices, so they get handled in a different
way.
> Well, looks like I'm out of luck, I'll do some trial & error.
try interrupt 12, which should be the HPC3 interrupt (sgint23.h). After
getting an HPC3 interrupt you have to look in HPC3 register istat0 and
istat1 for the interrupt source. I guess DaveM wanted to map these
interrupt sources to SGINT_HPCDMA, but never got to implement it.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next prev parent reply other threads:[~1998-10-29 22:14 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
1998-10-29 22:10 ` Thomas Bogendoerfer [this message]
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=19981029231009.A3756@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
--cc=ulfc@bun.falkenberg.se \
/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