From owner-freebsd-bugs  Tue May  5 15:22:49 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA25171
          for freebsd-bugs-outgoing; Tue, 5 May 1998 15:22:49 -0700 (PDT)
          (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 PAA25147
          for <freebsd-bugs@FreeBSD.org>; Tue, 5 May 1998 15:22:39 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id PAA06485;
	Tue, 5 May 1998 15:20:02 -0700 (PDT)
Date: Tue, 5 May 1998 15:20:02 -0700 (PDT)
Message-Id: <199805052220.PAA06485@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Stefan Esser <se@FreeBSD.ORG>
Subject: Re: kern/6481: Patches for VIA Socket 7 chipsets
Reply-To: Stefan Esser <se@FreeBSD.ORG>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/6481; it has been noted by GNATS.

From: Stefan Esser <se@FreeBSD.ORG>
To: "Greg A. Woods" <woods@zeus.leitch.com>, FreeBSD-gnats-submit@freebsd.org
Cc: freebsd-bugs@freebsd.org, Stefan Esser <se@freebsd.org>
Subject: Re: kern/6481: Patches for VIA Socket 7 chipsets
Date: Tue, 5 May 1998 23:53:21 +0200

 On 1998-05-04 18:40 -0400, "Greg A. Woods" <woods@zeus.leitch.com> wrote:
 > The following hunk of code (in sys/pci/pcisupport.c:chipset_probe() from
 > 2.2.6) shows a bit more detail on the FIC PA-2012 motherboard w/VIA-VP3
 > that we're testing....  Chip revision details were derived from the
 > on-line datasheets at www.via.com.tw.  Seems a bit silly to do all this
 > just for the probe messages, but it is kinda neat to see it all and know
 > you've got what you think you have.  It might be nice if the probe
 > message in which these strings appear used hex for the "rev" value too...
 
 I'll look into this when I have some spare time.
 There is code to print messages based on the contents
 of arbitrary configuration registers (see what's done
 for the Intel Saturn chip-set, for example, that's the
 one I implemented the feature for, originally ...)
 
 But in fact I think those register dumps should be 
 moved out of the kernel and into a user-land program,
 which accesses the configuration registers through the
 ioctl interface (/dev/pci), see pciconf.
 
 Regards, STefan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message