All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] EISA support
Date: Thu, 11 Oct 2001 09:15:00 +0100	[thread overview]
Message-ID: <20011011091500.I11105@linuxcare.com> (raw)
In-Reply-To: <20011010152807.C24923@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Wed, Oct 10, 2001 at 03:28:07PM +0100

On Wed, Oct 10, 2001 at 03:28:07PM +0100, Matthew Wilcox wrote:
> Alternatively, we could hack the 53c710 script to generate CPU interrupts
> directly :-)  Let me just document how that would work (Grant, please
> correct me if I misunderstood):
> 
> Instead of generating a PCI/EISA interrupt, generate a write of an
> allocated value to the CPU's EIRR (External Interrupt register).
> 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.

If we make the scsi script do that, the scsi chip wont realise it
has generated an interrupt, so wont stop processing scripts.  The
driver expects th chip to be halted when the int handler is called.
If we had a driver specific to the 53c710 where the scsi script managed
queues of requests itself, there might be scope for emulating an
INTFLY instruction (which is found on newer chips) that way.  The
53c700 doesn't have the capability of writing memory locations from
script.

Richard

  parent reply	other threads:[~2001-10-11  8:14 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
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 [this message]
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=20011011091500.I11105@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@parisc-linux.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.