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. Message-ID: <Pine.BSF.3.95.990509012428.18573A-100000@current1.whistle.com> In-Reply-To: <199905080930.LAA32929@peedub.muc.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.990509012428.18573A-100000>