Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@puffin.external.hp.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Richard Hirst <rhirst@linuxcare.com>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] EISA support
Date: Wed, 10 Oct 2001 11:36:17 -0600	[thread overview]
Message-ID: <200110101736.LAA19917@puffin.external.hp.com> (raw)
In-Reply-To: Message from Matthew Wilcox <willy@debian.org> of "Wed, 10 Oct 2001 15:28:07 BST." <20011010152807.C24923@parcelfarce.linux.theplanet.co.uk>

> Instead of generating a PCI/EISA interrupt, generate a write of an
> allocated value to the CPU's EIRR (External Interrupt register).

Correct. That's what txn_alloc_irq() is for.
That interface needs to change slightly if someone really wants to start
using it on a broad range of platforms and busses. FWIW, this could
work on any platform which a "local SAPIC" (ie IA64).

> This way, the CPU jumps straight to the scsi chip's interrupt handler
> rather than Asp's, which then has to decode which Asp IRQ it was;
> then jump to the EISA interrupt handler, decode which EISA IRQ it was,
> finally calling the scsi interrupt handler.

excalty - this also cuts out a bunch of IO space reads (and possibly writes).

> We might need to work out some other infrastructure to handle this,
> but it's something we should look into at some point.  Clearly I need
> to get EISA interrupts working anyway :-)

I think all the needed functions are in place already.

grant

  reply	other threads:[~2001-10-10 17:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10  6:24 [parisc-linux] EISA support Matthew Wilcox
2001-10-10  8:32 ` Michael S.Zick
2001-10-10 11:01   ` Alan Modra
2001-10-10 14:11     ` Michael S.Zick
2001-10-10 14:48   ` Matthew Wilcox
2001-10-10 15:38     ` Matthew Wilcox
2001-10-10 16:57       ` Michael S.Zick
2001-10-10 12:45 ` Richard Hirst
2001-10-10 14:28   ` Matthew Wilcox
2001-10-10 17:36     ` Grant Grundler [this message]
2001-10-11  1:40     ` Matthew Wilcox
2001-10-11  3:56       ` Grant Grundler
2001-10-11 11:23       ` Richard Hirst
2001-10-11 20:22         ` Matthew Wilcox
2001-10-11  8:15     ` Richard Hirst
2001-10-12  6:44 ` Matthew Wilcox
2001-10-12  8:47   ` Richard Hirst
2001-10-12  9:01     ` Richard Hirst
2001-10-16 19:17 ` Tom
2001-10-16 19:46   ` Jochen Friedrich
2001-10-16 20:00     ` Matthew Wilcox
2001-10-16 22:26       ` Jochen Friedrich
2001-10-16 22:32         ` Matthew Wilcox
2001-10-18 14:31 ` Tom
2001-10-18 15:08   ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2001-10-10 11:37 Pedot, Wolfgang

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=200110101736.LAA19917@puffin.external.hp.com \
    --to=grundler@puffin.external.hp.com \
    --cc=parisc-linux@parisc-linux.org \
    --cc=rhirst@linuxcare.com \
    --cc=willy@debian.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