From owner-freebsd-current@FreeBSD.ORG Wed Sep 23 20:55:43 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 387EE10656A5 for ; Wed, 23 Sep 2009 20:55:43 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from jacques.telenet-ops.be (jacques.telenet-ops.be [195.130.132.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7C0428FC34 for ; Wed, 23 Sep 2009 20:55:41 +0000 (UTC) Received: from triton.sigsegv.be ([213.119.96.179]) by jacques.telenet-ops.be with bizsmtp id kLvd1c00x3sCccd0JLveJ0; Wed, 23 Sep 2009 22:55:38 +0200 Received: from nereid (nereid.neptune.sigsegv.be [IPv6:2001:470:c8f4:0:200:ff:fe00:8]) by triton.sigsegv.be (Postfix) with SMTP id BEBB71C1E1; Thu, 24 Sep 2009 00:56:43 +0200 (CEST) Received: by nereid (sSMTP sendmail emulation); Wed, 23 Sep 2009 22:55:36 +0200 Date: Wed, 23 Sep 2009 22:55:35 +0200 From: Kristof Provost To: Pyun YongHyeon Message-ID: <20090923205535.GG19069@nereid> References: <20090922211012.GE19069@nereid> <20090922235350.GB1520@michelle.cdnetworks.com> <20090923184149.GF19069@nereid> <20090923202448.GD1099@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090923202448.GD1099@michelle.cdnetworks.com> X-PGP-Fingerprint: 6B6E 5EED 8ECF FAE7 1F61 7458 5046 7D0E 11B0 0EE8 User-Agent: Mutt/1.5.14 (2007-03-31) Cc: current@freebsd.org Subject: Re: mge, mii/e1000phy 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: Wed, 23 Sep 2009 20:55:43 -0000 On 2009-09-23 13:24:48 (-0700), Pyun YongHyeon wrote: > I'm pretty sure the device id for 88E1116 PHY is 0x21. Do you see > printed model number 88E1118 on your hardware? If so I have no idea > why Marvell use the same device id. Do you have access to 88E1118 > HY data sheet? > I've just double checked. The documentation from TS claims it's an 88E1118 and that's what I see on the chip itself as well. I don't have access to the data sheet, that would make this exercise far too easy. > I wanted to know advertised PHY capabilities as mge(4) explicitly > disabled 1000baseT/half-duplex mode in driver layer. But MV88F5182 > data sheet said it supports 1000baseT/half-duplex mode. > I'll try to find out tomorrow. I'm not sure if it'll matter though, as the switch I'm using right now is a 10/100 model. > > > I'm not author of mge(4) so I'm not familiar with mge(4). But it > > > seems that mge(4) lacks link state change handler. Normally NICs > > > are required to reprogram MAC to match resolved speed/duplex/ > > > flow-control of link when it know it established a valid link which > > > is notified from mii(4). > > > > > If that's the case I'd expect the driver not to work on my Sheevaplug > > either. The only difference I see is the PHY. > > > > Could be, but if you manually set media it reinitializes PHY and it > will call mge_ifmedia_upd() which in turn reinitializes the > controller. I guess this is workaround in mge(4). > Do you mean setting the media through an ioctl by 'manually set media'? If so, that doesn't really apply for either the TS-7800 or the Sheevaplug as both need the network to work before userspace can do anything. Kristof