From owner-freebsd-arch@FreeBSD.ORG Thu Jan 26 16:30:52 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F21C106566C for ; Thu, 26 Jan 2012 16:30:52 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 5833F8FC1D for ; Thu, 26 Jan 2012 16:30:52 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 8FB0EF0AD; Thu, 26 Jan 2012 16:30:51 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Stefan Bethke In-Reply-To: <20120125221753.GA17821@alchemy.franken.de> Date: Thu, 26 Jan 2012 17:30:51 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <47ABA638-7E08-4350-A03C-3D4A23BF2D7E@lassitu.de> <1763C3FF-1EA0-4DC0-891D-63816EBF4A04@lassitu.de> <20120106182756.GA88161@alchemy.franken.de> <95372FB3-406F-46C2-8684-4FDB672D9FCF@lassitu.de> <20120106214741.GB88161@alchemy.franken.de> <20120108130039.GG88161@alchemy.franken.de> <23477898-8D85-498C-8E30-192810BD68A8@lassitu.de> <20120111193738.GB44286@alchemy.franken.de> <66DDA0A2-F878-43FF-8824-54868F493B18@lassitu.de> <20120125221753.GA17821@alchemy.franken.de> To: Marius Strobl X-Mailer: Apple Mail (2.1084) Cc: FreeBSD-arch Subject: Re: Extending sys/dev/mii X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 16:30:52 -0000 Am 25.01.2012 um 23:17 schrieb Marius Strobl: > Yes, it assumes IEEE 802.3-compliant devices and usecases. If you > throw out all the things like auto-probing via ID registers, out- > detection of media via the BMSR and so and which makes miibus(4) > the generic PHY handling framework that it is or work around them, > I hardly can think of much that would be left that justifies using > miibus(4) in the first place though. Can't we just build another > framework which handles all the other stuff that also just happens > to have an MDIO interface and attach it instead? The problem with that is that for f.e. the RTL8306, the switch and the = PHYs coexist on the same MDIO bus, so some form of interoperation is = required. Don't get me wrong, my post was not meant to suggest that the current = miibus code must be scratched or even significantly changed, I just = wanted to document the limitations I discovered. What I would like to do is make my new mdio bus driver into a = full-fledged bus, and then maybe see if miibus can be extended to work = with it more naturally than through the miiproxy adapter driver. Stefan --=20 Stefan Bethke Fon +49 151 14070811