Date: Sat, 11 Apr 2009 13:26:24 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: pyunyh@gmail.com, Niki Denev <ndenev@gmail.com> Subject: Re: axe(4) (Belkin F5D5055) problems Message-ID: <200904111326.25342.hselasky@c2i.net> In-Reply-To: <2e77fc10904082334v3fc9676cy97ad97f4e7fe6d0a@mail.gmail.com> References: <2e77fc10903280259s5a761cacs398b88649a2367fe@mail.gmail.com> <20090409010953.GE37714@michelle.cdnetworks.co.kr> <2e77fc10904082334v3fc9676cy97ad97f4e7fe6d0a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 09 April 2009, Niki Denev wrote: > On Thu, Apr 9, 2009 at 4:09 AM, Pyun YongHyeon <pyunyh@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904111326.25342.hselasky>