From owner-freebsd-bugs Sat Nov 21 11:10:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11205 for freebsd-bugs-outgoing; Sat, 21 Nov 1998 11:10:05 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11144 for ; Sat, 21 Nov 1998 11:09:59 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id LAA11122; Sat, 21 Nov 1998 11:10:00 -0800 (PST) Date: Sat, 21 Nov 1998 11:10:00 -0800 (PST) Message-Id: <199811211910.LAA11122@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Kevin Day Subject: Re: kern/6630 Reply-To: Kevin Day Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/6630; it has been noted by GNATS. From: Kevin Day To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/6630 Date: Sat, 21 Nov 1998 13:05:32 -0600 (CST) I have also experienced this behavior, and confirmed with Cyrix what Christopher has said in this PR. In the 5510 and 5520 support chips for the MediaGX and MediaGXm, the LATCH command to the 8254 does nothing. While his patch works, it's still not perfect. It brings the 8254 to within 1% accuracy, which is good enough for my uses though. (It sees my 233 GXm as 209 MHz....) If I write a detection check to see if the 5510 or 5520 is present, could that be useful? Where would this be called though, if the 8254 check is done so soon, vendor/device ID's haven't yet been probed at that time..... Suggestions? Kevin Day To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message