From owner-freebsd-hardware@FreeBSD.ORG  Mon Oct 16 17:15:33 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: freebsd-hardware@freebsd.org
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 00A2416A412;
	Mon, 16 Oct 2006 17:15:33 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EAF3243D53;
	Mon, 16 Oct 2006 17:15:28 +0000 (GMT) (envelope-from avg@icyb.net.ua)
Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA08731;
	Mon, 16 Oct 2006 20:15:26 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Message-ID: <4533BE2E.4080005@icyb.net.ua>
Date: Mon, 16 Oct 2006 20:15:26 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 1.5.0.7 (X11/20060915)
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: nfsmb survey
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Oct 2006 17:15:33 -0000


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.

If you have a system based on NForce2/3/4, could you please share the
following information:

1. find out pci handle of your SMB controller:
$ pciconf -l | fgrep 0x0c0500
and also note chip field value, it should match 00(64|84|d4|e4|52)10de.
E.g.:
nfsmb0@pci0:1:1:        class=0x0c0500 card=0x1c02147b chip=0x006410de
rev=0xa2 hdr=0x00

2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like
follows:
$ pciconf -r pci0:1:1 0x20
$ pciconf -r pci0:1:1 0x24
$ pciconf -r pci0:1:1 0x50
$ pciconf -r pci0:1:1 0x54
using your pci handle instead of pci0:1:1, e.g.:
$ pciconf -r pci0:1:1 0x20
00000000
$ pciconf -r pci0:1:1 0x24
00000000
$ pciconf -r pci0:1:1 0x50
00001001
$ pciconf -r pci0:1:1 0x54
00001041

3. send chip id and register values here.

Thank you very much in advance.

-- 
Andriy Gapon