From owner-freebsd-current@FreeBSD.ORG Sat Apr 11 11:23:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AF2A1065670 for ; Sat, 11 Apr 2009 11:23:54 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.tele2.se [212.247.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1A28FC13 for ; Sat, 11 Apr 2009 11:23:53 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=V2t1Xvdoi9YDM8ZpLs8A:9 a=aCSwj9I0BMOxGEqLVfzC-IBESCMA:4 a=LY0hPdMaydYA:10 a=MSl-tDqOz04A:10 Received: from [193.217.167.6] (account mc467741@c2i.net HELO [10.0.0.188]) by mailfe13.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 834377419; Sat, 11 Apr 2009 13:23:52 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 11 Apr 2009 13:26:24 +0200 User-Agent: KMail/1.9.7 References: <2e77fc10903280259s5a761cacs398b88649a2367fe@mail.gmail.com> <20090409010953.GE37714@michelle.cdnetworks.co.kr> <2e77fc10904082334v3fc9676cy97ad97f4e7fe6d0a@mail.gmail.com> In-Reply-To: <2e77fc10904082334v3fc9676cy97ad97f4e7fe6d0a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200904111326.25342.hselasky@c2i.net> Cc: pyunyh@gmail.com, Niki Denev Subject: Re: axe(4) (Belkin F5D5055) problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 11 Apr 2009 11:23:54 -0000 On Thursday 09 April 2009, Niki Denev wrote: > On Thu, Apr 9, 2009 at 4:09 AM, Pyun YongHyeon wrote: > > On Wed, Apr 08, 2009 at 09:45:26AM +0300, Niki Denev wrote: > > >> Also the SiS191 seems to have problems negotiating gigabit link, there > >> are many posts about this > >> when using Linux. > > > > This could be related with PHY handling bug of Linux sis190 driver. > > Because Linux does not have mii(4) it have to poke PHY registers in > > driver layer which =A0in turn would make it hard to support various > > PHY hardwares. > > I've noticed this. The linux drives seems to write some magic numbers to > the hardware at several places... very confusing. > Hi, If the device is connected at the end of more than one HUB, then the follow= ing=20 patch might solve the problem. Else the following patch will have no effect. http://perforce.freebsd.org/chv.cgi?CH=3D160485 =2D-HPS