Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754706AbbBFN5K (ORCPT ); Fri, 6 Feb 2015 08:57:10 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:33989 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752535AbbBFN5I (ORCPT ); Fri, 6 Feb 2015 08:57:08 -0500 Date: Fri, 6 Feb 2015 14:57:06 +0100 From: Pavel Machek To: Florian Fainelli Cc: kernel list , netdev@vger.kernel.org Subject: Re: Ethernet: how to disable gigabit support Message-ID: <20150206135706.GB25683@amd> References: <20150205202527.GA7917@amd> <54D3F267.3000908@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54D3F267.3000908@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1178 Lines: 32 On Thu 2015-02-05 14:44:55, Florian Fainelli wrote: > On 05/02/15 12:25, Pavel Machek wrote: > > Hi! > > > > This happened on more than one project: there's gigabit-capable chip, > > but the connector is not designed for gigabit speed. > > > > I'd like to have speed autonegotiation, but not offer gigabit (as it > > will not work). > > > > Is there way to do that without hacking the kernel? Should mii-tool do > > that? > > Since you use the PHY library, you should be able to do something like > this in your PHY driver prior to starting the PHY state machine: > > phydev->supported &= PHY_BASIC_FEATURES (effectively masking Gigabit > capability) Thanks, that did the trick. Pavel (But still it would be nice to have a generic way of doing this, using something like mii-tool.) -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/