From owner-freebsd-net@FreeBSD.ORG Sun Dec 11 00:07:06 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AFAB1065672; Sun, 11 Dec 2011 00:07:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id A589C8FC0C; Sun, 11 Dec 2011 00:07:05 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so5314229vcb.13 for ; Sat, 10 Dec 2011 16:07:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qcuEi3xzFwhaFjoYwns4TlJE7f3KfN5O/A85nwUxOLk=; b=Fd2le0feGlXkgZBggm/C335/QDP0RFztLHGhk5jB0PUnwTXr/cGCGb4rxbhy03al6Z SytLjobe+dwMcBeU9vsWmu8z7Tr4C4rJKjVZkzB3P31G7JNlqP79FqGT4kg8qRsBMSSq xfrGkpwC2LZEIFBfzKXA+budkuSvPClXbakQE= MIME-Version: 1.0 Received: by 10.52.90.80 with SMTP id bu16mr7255782vdb.113.1323562024934; Sat, 10 Dec 2011 16:07:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.26.50 with HTTP; Sat, 10 Dec 2011 16:07:04 -0800 (PST) In-Reply-To: <20111210140540.6301dfa9.ray@freebsd.org> References: <20111210140540.6301dfa9.ray@freebsd.org> Date: Sun, 11 Dec 2011 11:07:04 +1100 X-Google-Sender-Auth: 3MCWttULyope3e8Ue5rzGjesEwo Message-ID: From: Adrian Chadd To: Aleksandr Rybalko Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: "float PHYs", communication between indirect attached devices 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: Sun, 11 Dec 2011 00:07:06 -0000 On 10 December 2011 23:05, Aleksandr Rybalko wrote: > Hi net@ subscribers, > > Simple explanation of problem: > real situation, device with two NICs (arge0 and arge1) > arge0 attached to PHY w/o direct access to it. > arge1 attached to switch MII port (and have access to MDIO bus). > > switch have child MDIO bus for all Physical ports. > One of this ports (or his PHY) must be controlled by arge0. Must be controlled how/why? Please explain this a little more first. I have a feeling that you want to magically make it able to configure the PHY it's glued to, so changing speed/duplex/clock and such are kept in sync. We can likely just ignore that and just allow the user to configure both the arge{0,1} interface and the PHY it's glued to. Then it's just up to documenting that particular ugly requirement for now. Read: This shouldn't be a blocker for further development. :) Adrian