From owner-freebsd-hackers Thu Dec 11 18:33:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06546 for hackers-outgoing; Thu, 11 Dec 1997 18:33:17 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06536 for ; Thu, 11 Dec 1997 18:33:10 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id SAA25479; Thu, 11 Dec 1997 18:33:02 -0800 (PST) Message-ID: <19971211183302.28799@hydrogen.nike.efn.org> Date: Thu, 11 Dec 1997 18:33:02 -0800 From: John-Mark Gurney To: Mike Smith Cc: ETX-B-SL Martti Kuparinen , freebsd-hackers@FreeBSD.ORG Subject: Re: panic: npxintr from nowhere References: <19971211175938.41550@hydrogen.nike.efn.org> <199712120210.MAA00359@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199712120210.MAA00359@word.smith.net.au>; from Mike Smith on Fri, Dec 12, 1997 at 12:40:41PM +1030 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith scribbled this message on Dec 12: > > > Hmm, interesting. I would guess that this means that you shouldn't run > > > floating point code in the kernel. > > > > :) yeh... well, I was going to improve the fade screen saver so that > > it wouldn't turn everything to a dull grey... > > Fixed point. Faster too. so we have a fixpoint lib in the kernel now?? :) I could rewrite it to used fix point, but it's that much extra code... would a simple fixpoint lib be useful in the kernel? > > also, if I remeber correctly, there are only two places in the kernel > > that use floating point... one of them is in the Bt848 driver... > > I just looked; where? I looked too, but couldn't find it... must of been an older version of the driver... > > > It probably fails because the FPU initialisation is lazy, and if you > > > haven't initialised it before you use it, you'll die screaming. > > > > is there a routine for the kernel code to use to initalize it? > > You'd have to ask Bruce about that. ok... will do.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD