From owner-freebsd-current@freebsd.org Mon Mar 13 21:26:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30213D0ABFD for ; Mon, 13 Mar 2017 21:26:33 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 10ED518FC; Mon, 13 Mar 2017 21:26:33 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 9EBFE10A82D; Mon, 13 Mar 2017 17:26:31 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Roberto Rodriguez Jr , "avg@freebsd.org" Subject: Re: SMBus driver Date: Mon, 13 Mar 2017 14:01:42 -0700 Message-ID: <2999456.G2ZksF5gie@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-STABLE; KDE/4.14.10; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 13 Mar 2017 17:26:31 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2017 21:26:33 -0000 On Sunday, March 12, 2017 12:31:53 AM Roberto Rodriguez Jr wrote: > Hi, > > pciconf -lvbe > > none0@pci0:0:20:0: class=0x0c0500 card=0x21f7103c chip=0x780b1022 > rev=0x3a hdr=0x00 > vendor = 'Advanced Micro Devices, Inc. [AMD]' > device = 'FCH SMBus Controller' > class = serial bus > subclass = SMBus > > I have 'device smbus' in KERNCONF. > I would love to know how to correct this. I looked in sys/dev/smbus but > have no idea which file to edit or where to begin understanding why its > none0. I think this device is supported by the intpm(4) driver? -- John Baldwin