Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Matthew Wilcox <willy@debian.org>
Cc: Richard Hirst <rhirst@linuxcare.com>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] EISA support
Date: Thu, 11 Oct 2001 02:40:10 +0100	[thread overview]
Message-ID: <20011011024010.C13932@parcelfarce.linux.theplanet.co.uk> (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:
> I haven't written that code yet.  Basically, I need to allocate a new IRQ
> region for EISA interrupts, then on receipt of Asp irq 21 read the EISA
> interrupt number from 0xfc01f000.  It seems there may be some extra gunk
> needed to handle the TI chipset, but I'll have a go at getting interrupts
> to work later today.

Turns out it's unsufferably ugly to do this right now, due to Mongoose
being a _sibling_ of Asp, not a _child_.  So I've put a nasty patch at
ftp://puffin.external.hp.com/pub/parisc/src/eisa-irq.c which works enough
that it seems to claim the IRQs; but the hp100 driver just allocates
IRQ3 and doesn't allow any kind of fixup, so I haven't actually tested it.

I have a plan to allocate Mongoose's IRQ in a nicer way, but that will
have to wait until tomorrow.  What do you think the best way would be
to fix EISA card IRQs?  I have a couple of thoughts:

 * Introduce a new EISA_IRQ_BASE macro that most architectures
   define to 0.
 * Reserve IRQ region 0 for EISA

Any better ideas?

-- 
Revolutions do not require corporate support.

  parent reply	other threads:[~2001-10-11  1: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
2001-10-11  1:40     ` Matthew Wilcox [this message]
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=20011011024010.C13932@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=rhirst@linuxcare.com \
    /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