From owner-freebsd-hackers Wed Jun 12 19:38:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA25819 for hackers-outgoing; Wed, 12 Jun 1996 19:38:50 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA25812 for ; Wed, 12 Jun 1996 19:38:46 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (smurf@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with ESMTP id TAA12634 for ; Wed, 12 Jun 1996 19:38:53 -0700 Message-Id: <199606130238.TAA12634@soda.CSUA.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: Nexgen chip and freebsd support Date: Wed, 12 Jun 1996 19:38:36 -0700 From: Scott MacFiggen Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just got though discussing this on the freebsd-questions list and it seems Freebsd does not have any support for the Nexgen nX586 chip. My question, it is possible to get someone clued to hack in support for the Nexgen chip? I was looking at the Linux patch for nexgen chip supprt and it does not seem all that complicated. FreeBSD works fine on the chip when configured for a 386 but from looking at the linux patch, it implies that this causes a performance hit because some of the chips features are not being taken advantage of. Next question, is the above true? Is the chip being underutilzed having the kernel being configured for a 386? I am currently working as a contracter at Nexgen as a sysadmin so I might be able to get support from the inside if someone is interested in working on this. -Scott