From owner-freebsd-current@FreeBSD.ORG Mon Oct 30 07:59:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B6F16A403 for ; Mon, 30 Oct 2006 07:59:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id E948343D45 for ; Mon, 30 Oct 2006 07:59:27 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1187806wxd for ; Sun, 29 Oct 2006 23:59:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=Uw6BvFMWKHvECRt/FusVOHFrWl4wdeRpxQXy55Wj01LgNFohlf2v/PFFPQfKCgGRsek0nNrcn+MLn4v+MIEVIzC5xvDYbvX1X+J13Jj/upE6srM0F07f1kOVPFC8FLtj/NDKTEFh0b8GWIy2sBYGx/5wht4IjaGt1EaDdEZSf98= Received: by 10.70.95.19 with SMTP id s19mr4374545wxb; Sun, 29 Oct 2006 23:59:27 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 67sm4253323wra.2006.10.29.23.59.24; Sun, 29 Oct 2006 23:59:26 -0800 (PST) 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 k9U81FuF053336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Oct 2006 17:01:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k9U81Fxt053335; Mon, 30 Oct 2006 17:01:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 30 Oct 2006 17:01:14 +0900 From: Pyun YongHyeon To: "O. Hartmann" Message-ID: <20061030080114.GE51632@cdnetworks.co.kr> References: <20060926002916.GA5975@cdnetworks.co.kr> <4833C999-9C20-4C40-814F-214BCE90494E@tamu.edu> <20061029213433.GB1106@fasolt.home.paeps.cx> <20061030044121.GB51632@cdnetworks.co.kr> <4545AEC7.2080205@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4545AEC7.2080205@zedat.fu-berlin.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.org, Philip Paeps Subject: Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers. 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: Mon, 30 Oct 2006 07:59:29 -0000 On Mon, Oct 30, 2006 at 08:50:31AM +0100, O. Hartmann wrote: > Pyun YongHyeon wrote: > >On Sun, Oct 29, 2006 at 10:34:33PM +0100, Philip Paeps wrote: > > > The driver seems to work for me, but only when I put it in the kernel > > proper. > > > If I try to load it as a module, it gives ENOMEM when trying > > bus_dmamem_alloc() > > > for the jumbo buf (line 2177 of if_msk.c). > > > > > > >If there is no cotiguous DMA memory requried by the driver you have > >to reboot to get it. Alternatively, you can put the driver in the > >kernel instead of using kernel module as you mentioned. > > > > > Two things I'm curious about: > > > > > > msk0: flags=8843 mtu 1500 > > > options=9a > > > inet6 fe80::211:11ff:fe59:1333%msk0 prefixlen 64 scopeid 0x1 > > > inet 172.16.1.2 netmask 0xffffff00 broadcast 172.16.1.255 > > > inet6 2001:6f8:32f:10:211:11ff:fe59:1333 prefixlen 64 autoconf > > > ether 00:11:11:59:13:33 > > > media: Ethernet autoselect (100baseTX ) > > > status: active > > > > > > What are flag0 and flag1 in the media: line? > > > > > > >AFAIK there is no official way to indicate negotiated Rx/Tx > >flow-control status in ifconfig(8). So I used flag0 to indicate > >Rx flow-control and flag1 to denote Tx flow-control. It just means > >the driver will flow-control(Rx, Tx) with its link-partner(usually > >switch). > > > > > The kernel also prints "mskc0: Uncorrectable PCI Express error" after > > bringing > > > the interface up. It doesn't seem to cause any harm, but it feels > > fishy. I > > > haven't looked at the source for this. > > > > > > >You can safely ignore the error message unless the error shows > >endlessly. > > > > Is this driver also gonna be used in STABLE/6.2? > ATM the driver is only for CURRENT. It needs more tests/feedbacks from users and poor Rx performance issue should be fixed before hitting src tree. Since RELENG_6 lacks some APIs used on this driver it also need more changes to use it on RELENG_6. -- Regards, Pyun YongHyeon