From owner-freebsd-hackers  Sun May  9  1:25: 7 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id E1FF314DBA
	for <hackers@freebsd.org>; Sun,  9 May 1999 01:25:05 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id BAA05764;
	Sun, 9 May 1999 01:24:51 -0700 (PDT)
Date: Sun, 9 May 1999 01:24:49 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Gary Jennejohn <garyj@muc.de>
Cc: hackers@freebsd.org
Subject: Re: Advice on terrible hacky PCI driver. 
In-Reply-To: <199905080930.LAA32929@peedub.muc.de>
Message-ID: <Pine.BSF.3.95.990509012428.18573A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Sat, 8 May 1999, Gary Jennejohn wrote:

> Julian Elischer writes:
> >
> >
> >I have a driver for a device that exists onthe PCI bus..
> >unfortunatly (don't ask) it has a separate interrupt as well that runs
> >directly to int6 of the 8259. (not via the PCI bus and not configured in
> >by the bios etc.)
> >
> >I've tried the following terrible hack in the driver, but it didn't seem
> >to work.  any thoughts? 
> >
> >
> >
> >static void
> >pwrfailPCIattach( pcici_t config_id, int unit)
> >{       
> >        sc_p    scp;
> >        scp = sca[unit];
> >        
> >        config_id->intline = 6; /* pretend the chip said irq 6 */
> >        config_id->intpin = 4;  /* pretend it's pin D */
> >        /*
> >         * Allocate our (hardwired) interrupt.
> >         */
> >        if (!pci_map_int(config_id, pwrfailintr, scp, &bio_imask)) {
> >                printf("pwrfail%d: couldn't map interrupt\n", unit);
> >        } else {
> >                printf("pwrfail%d: interrupt %d mapped\n",
> >                                        unit, config_id->intline);
> >        }
> >}
> >
> >
> >It get's the success message, but the interrupt is never delivered to the 
> >routine pwrfailintr().
> >
> 
> it seems like this should work, but the new-bus code is such a maze of
> twisty little passages, all alike, that I can't wrap my head around it.

This is in 3.1

julian

> 
> ---
> Gary Jennejohn
> Home - garyj@muc.de
> Work - garyj@fkr.dec.com
> 
> 
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message