From owner-freebsd-stable@FreeBSD.ORG Mon Oct 16 18:22:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67E9116A4D1 for ; Mon, 16 Oct 2006 18:22:27 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [204.127.225.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DB6043D72 for ; Mon, 16 Oct 2006 18:22:11 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (alnrmhc14) with ESMTP id <20061016182211b1400j7d6oe>; Mon, 16 Oct 2006 18:22:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D184F1FA03A; Mon, 16 Oct 2006 11:22:10 -0700 (PDT) Date: Mon, 16 Oct 2006 11:22:10 -0700 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20061016182210.GA25231@icarus.home.lan> Mail-Followup-To: freebsd-stable@freebsd.org References: <4533BE2E.4080005@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4533BE2E.4080005@icyb.net.ua> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: nfsmb survey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 18:22:27 -0000 On Mon, Oct 16, 2006 at 08:15:26PM +0300, Andriy Gapon wrote: > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. > However, the driver doesn't currently work on all hardware that it is to > support. The problem is with choosing proper BAR registers, which, as it > seems, might be different for different chipsets/SMB controllers. Andriy, Does this issue also cover the situation where if a kernel is built with ichsmb *and* nfsmb, and is run on an NForce2/3/4 board, the ichsmb driver is chosen/bound to one of the two SMBus devices, when in fact nfsmb should bind to both? (Only after removing ichsmb from the kernel configuration did nfsmb bind to both). Just curious -- thanks! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |