From owner-freebsd-hackers Wed Jul 18 18: 8:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 3523637B414; Wed, 18 Jul 2001 18:08:33 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA26143; Wed, 18 Jul 2001 21:08:32 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA04984; Wed, 18 Jul 2001 21:08:31 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA04980; Wed, 18 Jul 2001 21:08:31 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Wed, 18 Jul 2001 21:08:31 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: pci device driver writing newbie Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm currently trying to write a driver for the hardware monitoring function of the Via 686a/b chipset, but I have a problem. I'm trying to get my module (which right now does mostly nothing except probing and attaching) to detect the ACPI function of this chip, but right now pciconf -l shows it as "chip0". I found the devid in /usr/src/sys/pci/pcisupport.c, (0x30571106) and commented that case out, recompiled my kernel, and rebooted, but no luck, it still detects as chip0. What can I do to keep this from happening. This is the only way I can accurately probe and attach this device and find it's base i/o address. Once I have this chip probing and attaching, and have the base io address, I can do the rest of the hardware monitoring functions of this driver on my own. (as a note, to avoid doing floating point calculations in the kernel, and to avoid doing some really nasty hacks that I found in the linux version of this driver, I'll be making the driver return the raw values from the registers, and I'll be writing a library that takes care of making the values that come from the registers useful.) Thanks ahead of time :-) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message