mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: grant@aerodeck.prestel.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RE: 2.4.5-ac14 through to 2.4.6-ac1 fdomain.c initialisation for shared IRQ
Date: Thu, 5 Jul 2001 19:16:26 +0100 (BST)	[thread overview]
Message-ID: <E15IDfu-00034t-00@the-village.bc.nu> (raw)
In-Reply-To: <000201c1057b$f8ff4600$0101a8c0@heron1> from "Grant Fribbens" at Jul 05, 2001 06:57:23 PM

> I have recently had a problem with the fdomain driver initialisation and
> have found the problem to be the way in which it requests the irq. Here is
> my patch that has so far work ok.

I've seen this patch before. It needs at least one change

> -			     do_fdomain_16x0_intr, 0, "fdomain", NULL);
> +      retcode = request_irq( shpnt->irq,
> +			     do_fdomain_16x0_intr, SA_SHIRQ, "fdomain", shpnt);

Only set SA_SHIRQ if PCI - say -

		pdev?SA_SHIRQ:0

The other problem is that the code doesnt have support for handling IRQ
source checking, so if the line it shares with generates interrupts we might
sometimes do the right thing

I have a long outstanding request with adaptec (who bought future domain)
for the info needed to fix this, but obviously its a dead product, from a
bought company and hardly on their priorities.

I suspect the IRQ handler needs to either

A.	Check bit 0 of the status port and return 

B.	Check bit 4 or bit 9 of the interrupt control register

Without docs someone would need to play with the various combinations and
see what happened


  reply	other threads:[~2001-07-05 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 17:57 Grant Fribbens
2001-07-05 18:16 ` Alan Cox [this message]
2001-07-05 18:26   ` David Weinehall
2001-07-05 18:34     ` Alan Cox

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=E15IDfu-00034t-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=grant@aerodeck.prestel.co.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®