From owner-freebsd-current@FreeBSD.ORG Fri May 11 02:43:15 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6832316A400 for ; Fri, 11 May 2007 02:43:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by mx1.freebsd.org (Postfix) with ESMTP id 20FBF13C455 for ; Fri, 11 May 2007 02:43:14 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so820228wra for ; Thu, 10 May 2007 19:43:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=JSBzq+Vs9lAb2VQuPdNUsjRfpWls2Hw8Dg8uiLqCHJiGo661znzzzrfnYiBzzoKW78ZWCwJ4NxOrev+x6Oj7IkFc45Q77HpxHUvabumD48VQJnuq6jFO/aMQaPLMfjkv2nXLWtUI1DHJeMJdZqoMWUghrgFTU4ea1ntRfzbIY7Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=r04Opf8YqRVTrHSy6A/Avv5bWdOm8iolTaHsnL/bLGPKxUE34jDGOi/x2W0icNb2rEBOaoM1v1+rQFnReSxTnHwXLzJDwzapZo5TlEC0pMQ6ngV5NcQlQ/iFdtsFeFLTZCdiU59IRWJXS5QvfF1WNlzc5OR2cyU8h0L+1/AhZnQ= Received: by 10.114.89.1 with SMTP id m1mr807330wab.1178851393945; Thu, 10 May 2007 19:43:13 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id y25sm18356pod.2007.05.10.19.43.10; Thu, 10 May 2007 19:43:12 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l4B2h6fe074354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 May 2007 11:43:06 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l4B2h54d074353; Fri, 11 May 2007 11:43:05 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 11 May 2007 11:43:05 +0900 From: Pyun YongHyeon To: "O. Hartmann" Message-ID: <20070511024304.GA74182@cdnetworks.co.kr> References: <46437F07.3040006@mail.zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46437F07.3040006@mail.zedat.fu-berlin.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: nfe(4) on nVidia CK804/MCP9: MSI/MSI-X supported? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 02:43:15 -0000 On Thu, May 10, 2007 at 10:22:31PM +0200, O. Hartmann wrote: > Sorry, > lost the initial posting. Tried the nfe-related stuff for if_nfe posted > by Pyun YongHyeon these days and this is the result of a verbose boot > for my ASUS A8N32-SLI mainboard: > > nfe0: port 0x9480-0x9487 > mem 0xddcf6000-0xddcf6fff irq 22 at device 19.0 on pci0 > nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xddcf6000 > miibus1: on nfe0 > nfe0: bpf attached > nfe0: Ethernet address: > nfe0: [MPSAFE] > nfe0: [FILTER] > > mskc0: port 0xd800-0xd8ff mem > 0xddefc000-0xddefffff irq 17 at device 0.0 on pci2 > mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xddefc000 > mskc0: MSI count : 2 > mskc0: attempting to allocate 2 MSI vectors (2 supported) > mskc0: using IRQs 256-257 for MSI > mskc0: RAM buffer size : 48KB > mskc0: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff) > mskc0: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff) > msk0: on mskc0 > msk0: bpf attached > msk0: Ethernet address: 00:15:f2:a2:79:aa > miibus0: on msk0 > mskc0: [MPSAFE] > mskc0: [FILTER] > msk0: link state changed to UP > > > > All right, is looks like MSI isn't supported by the onboard MCP9 NIC or > the driver isn't supporting this NIC, but it seems the nfe() driver does > support NICs based on MCP55-based boards/chipsets. What's up with the > MCP9 NIC on CK804/nForce4 chipsets? > It seems that your nVidia NIC does not have MSI capability so the nfe(4) driver fall back on traditional interrupt delivery mechanism. However your Marvell NIC has MSI capability and msk(4) successfully configured to use MSI. "pciconf -lvc" will show you what capabilities are supported by the hardware. -- Regards, Pyun YongHyeon