From owner-freebsd-hardware Tue Apr 17 18:10:59 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from zogbe.tasam.com (hc6526bd1.dhcp.vt.edu [198.82.107.209]) by hub.freebsd.org (Postfix) with ESMTP id BA32337B423 for ; Tue, 17 Apr 2001 18:10:53 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (hc6526bd1.dhcp.vt.edu [198.82.107.209]) by zogbe.tasam.com (8.11.3/8.11.3) with SMTP id f3I1Aoh03664; Tue, 17 Apr 2001 21:10:50 -0400 (EDT) Message-ID: <003001c0c7a4$66d457d0$dc02010a@battleship> From: "Joseph Gleason" To: "Michael VanLoon" , Cc: "Paul" References: Subject: Re: AMD MB + I/O address -> /dev/mem byteoffset question Date: Tue, 17 Apr 2001 21:10:46 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know healthd didn't seem to support my chipset. It gave me a bunch of non-sensical values for everything. I assume it was reading the wrong I/O addresses. Can someone point me towards what exactly SMB is? I think I know, but I am certainly not sure. ----- Original Message ----- From: "Michael VanLoon" > If I remember correctly, I/O space is separate from memory space on Intel > chips (i.e. I/O is not memory-mapped). You cannot read/write it with a > memory address. You need to use I/O functions to do so. > > There are at least two daemons that already do this. One is healthd, and I > forget the name of the other one. I believe you need to check into SMBus > protocol to work with these as well. > > > From: Joseph Gleason [mailto:clash@tasam.com] > > Sent: Tuesday, April 17, 2001 5:44 PM > > > > This brings up a somewhat unrealated point. In the manual it says: > > "Hardware monitoring features for temperatures, fans and voltages will > > occupy I/O address from 294H to 297H." > > > > Can I access that memory block by reading from a byte offset > > in /dev/mem? > > If so, what offset? Can someone explain the XXXH notation in terms of > > actual memory or point me somewhere that does? > > > > I am intersted in writing a little peice of software that > > will query these > > values. If I can read the appropriate chunk, I'm sure I can > > figure out > > exactly what byte is what by seeing what values change when I > > do diffrent > > things. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message