npxintr(): this function does the right thing if we don't try to clear

the interrupt latch (which is probably done by the hypervisor, linux/xen
doesn't do it either). Now the "fputest" configure test from pkgsrc/math/yorick
works as expected.
Thanks to Christian Limpach for the hint.
This commit is contained in:
bouyer 2005-03-20 13:12:59 +00:00
parent 34b167fb9e
commit 83e1dbf7bb

View File

@ -1,4 +1,4 @@
/* $NetBSD: npx.c,v 1.3 2004/05/07 13:48:32 cl Exp $ */
/* $NetBSD: npx.c,v 1.4 2005/03/20 13:12:59 bouyer Exp $ */
/* NetBSD: npx.c,v 1.103 2004/03/21 10:56:24 simonb Exp */
/*-
@ -68,7 +68,7 @@
*/
#include <sys/cdefs.h>
__KERNEL_RCSID(0, "$NetBSD: npx.c,v 1.3 2004/05/07 13:48:32 cl Exp $");
__KERNEL_RCSID(0, "$NetBSD: npx.c,v 1.4 2005/03/20 13:12:59 bouyer Exp $");
#if 0
#define IPRINTF(x) printf x
@ -381,12 +381,6 @@ npxintr(void *arg, struct intrframe iframe)
uvmexp.traps++;
IPRINTF(("%s: fp intr\n", ci->ci_dev->dv_xname));
panic("not supported\n");
/*
* Clear the interrupt latch.
*/
bus_space_write_1(sc->sc_iot, sc->sc_ioh, 0, 0);
/*
* If we're saving, ignore the interrupt. The FPU will generate