From owner-freebsd-current Sat Dec 26 13:57:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06475 for freebsd-current-outgoing; Sat, 26 Dec 1998 13:57:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06462 for ; Sat, 26 Dec 1998 13:57:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01495; Sat, 26 Dec 1998 13:55:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812262155.NAA01495@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: K6-2 (3?) CPU_WT_ALLOC In-reply-to: Your message of "Thu, 24 Dec 1998 21:46:56 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Dec 1998 13:55:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > CPU_WT_ALLOC does not work correctly for K6-2s of model 8+ and probably K6-3s > (when they appear on the market soon). In addition, print_AMD_info() incorrectly > printfs write allocation's size. I've fixed them, so they now Do The Right > Thing, and added a "NO_MEMORY_HOLE" option to easily allow 15-16mb range > handling for us K6 and K6-2 users. A patch follows in cleartext and encoded > forms. Can anyone else using this patch speak up about their experiences? It'd be good to see it committed, but I have no hardware on which to test it... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message