From owner-freebsd-hackers  Sun Jun 18  9:36:32 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by hub.freebsd.org (Postfix) with ESMTP id 5EBAF37B6CE
	for <hackers@freebsd.org>; Sun, 18 Jun 2000 09:36:26 -0700 (PDT)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from libr.scitec.kobe-u.ac.jp (cs22101.ppp.infoweb.ne.jp [202.219.4.17])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id BAA85197;
	Mon, 19 Jun 2000 01:37:47 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id BAA14195; Mon, 19 Jun 2000 01:29:50 +0900 (JST)
From: takawata@shidahara1.planet.sci.kobe-u.ac.jp
Message-Id: <200006181629.BAA14195@libr.scitec.kobe-u.ac.jp>
To: wc.bulte@chello.nl, hackers@freebsd.org
Subject: Re: SM bus on VIA KX133 chipset? 
In-reply-to: Your message of "Sun, 18 Jun 2000 14:01:23 +0200."
             <20000618140122.A73008@freebie.wbnet> 
Date: Mon, 19 Jun 2000 01:29:48 +0900
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20000618140122.A73008@freebie.wbnet>, Wilko Bulte wrote:
>On Sun, Jun 18, 2000 at 10:49:08AM +0200, Wilko Bulte wrote:
>> Since yesterday I finally have my Abit KA7 Athlon board online (I *hate*
>> backordered CPUs..). It works like a charm, but I'd like to see if wmhm
>> (hardware monitoring) can be made to work. Sofar starting wmhm gives me:
1.There is no SMBus support for Athron Chipset,and SMBus that connected to
mother board cannot be controled with Bt8X8 I2C Bus,that is connected to
TV tuner,etc.

>
><hmpf, what use is a kernel.debug if you don't make use of it.. more 
>useful bt follows>

>#5  0xc017439a in device_get_softc (dev=0x0) at ../../kern/subr_bus.c:986
>#6  0xc01452d3 in smbus_request_bus (bus=0x0, dev=0xc0bdcd00, how=3)
>    at ../../dev/smbus/smbconf.c:131
>#7  0xc0218688 in bti2c_iic_callback (dev=0xc0bdcd00, index=1,
>data=0xc94efd28)
>    at ../../dev/bktr/bktr_i2c.c:275
>#8  0xc0145d28 in IICBB_CALLBACK (dev=0xc0bdcd00, index=1, 
>    data=0xc94efd28 "\003") at iicbb_if.c:27
>#9  0xc0145b2a in iicbb_callback (dev=0xc0bdcc80, index=1, 
>    data=0xc94efd28 "\003") at ../../dev/iicbus/iicbb.c:236
>#10 0xc014655c in IICBUS_CALLBACK (dev=0xc0bdcc80, index=1, 
>    data=0xc94efd28 "\003") at iicbus_if.c:37
>#11 0xc0146779 in iicbus_request_bus (bus=0xc0bdcc00, dev=0xc0bdcb80, how=3)
>    at ../../dev/iicbus/iiconf.c:108
>#12 0xc0145f54 in iicsmb_callback (dev=0xc0bdcb80, index=1, 
>    data=0xc94efd78 "\003") at ../../dev/iicbus/iicsmb.c:242
>#13 0xc0144ec4 in SMBUS_CALLBACK (dev=0xc0bdcb80, index=1, 
>    data=0xc94efd78 "\003") at smbus_if.c:37
>#14 0xc01452ed in smbus_request_bus (bus=0xc0bdcb00, dev=0xc0bdca80, how=3)
>    at ../../dev/smbus/smbconf.c:136

2. I think it is bktr driver's bug related to I2C interface.
bktr driver has two way to access I2C Bus:one is I2C bit bang interface,
another is controller access that issues I2C bus request. And it seems
a bug of I2C Bit Bang interface.

Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 



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