From owner-freebsd-net@FreeBSD.ORG Mon May 12 12:07:53 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58BD9106564A for ; Mon, 12 May 2008 12:07:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2EB4B8FC1C for ; Mon, 12 May 2008 12:07:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id CABD9108372; Mon, 12 May 2008 08:07:52 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 12 May 2008 08:07:52 -0400 X-Sasl-enc: uJVrlmLmigE7uBV7IAIoSvieU25H8cBpywE+WevWG5sa 1210594072 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id CF84ED379; Mon, 12 May 2008 08:07:51 -0400 (EDT) Message-ID: <48283316.2080100@FreeBSD.org> Date: Mon, 12 May 2008 13:07:50 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080511) MIME-Version: 1.0 To: Volker References: <48281D8F.2090501@vwsoft.com> <20080512111958.GA95632@alchemy.franken.de> <48283036.8060602@vwsoft.com> In-Reply-To: <48283036.8060602@vwsoft.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org, Marius Strobl Subject: Re: how to identify a PHY? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 12:07:53 -0000 Volker wrote: > ... > In short my original question better reads as "how do I know the kind of > phy if no driver has been attached". Can one retrieve that information > out of a verbose boot dmesg (from probing messages)? > You can't determine which PHY is in use unless a driver is attached, because it's necessary to attach a driver in order to access the card's MII registers. Same with any other OS. If no PHY driver attached, but a NIC driver attached, you should see this message: device_printf(dev, "MII without any PHY!\n"); It sounds like someone needs to instrument the code path mii_phy_probe() to print useful information in the situation you describe. cheers BMS