From owner-freebsd-embedded@FreeBSD.ORG Mon Dec 12 10:28:31 2011 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22411106566B for ; Mon, 12 Dec 2011 10:28:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C8AF28FC13 for ; Mon, 12 Dec 2011 10:28:30 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so6219356vbb.13 for ; Mon, 12 Dec 2011 02:28:30 -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 :content-transfer-encoding; bh=qfmI6Ft6azIHu9ee9BLf7abaYQuaLxP78RTUkuvorlY=; b=O+99CbkvUT7wIydy2YGskVbYd3JJvioOfbkiucGFCfMFD7WX2jMG1xvI3N3lxKH9Yq F6z2WWo/7NHPmNHo+hppzZn41Qnmb8wTIALqrzCqMVgqHM20S/RzsyXZZIcz/D0zKU/X dzmkPX4bduoIY6jqLvjHvdjEPfEssICK/AGnY= MIME-Version: 1.0 Received: by 10.52.90.80 with SMTP id bu16mr9284777vdb.113.1323685710014; Mon, 12 Dec 2011 02:28:30 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.26.50 with HTTP; Mon, 12 Dec 2011 02:28:29 -0800 (PST) In-Reply-To: References: <68ABED76-CB1F-405A-8036-EC254F7511FA@lassitu.de> <3B3DB17D-BF87-40EE-B1C1-445F178E8844@lassitu.de> <86030CEE-6839-4B96-ACDC-2BA9AC1E4AE4@lassitu.de> <2D625CC9-A0E3-47AA-A504-CE8FB2F90245@lassitu.de> <203BF1C8-D528-40C9-8611-9C7AC7E43BAB@lassitu.de> <3C0E9CA3-E130-4E9A-ABCC-1782E28999D1@lassitu.de> <6387ABA5-AC55-49DD-9058-E45CC0A3E0A0@lassitu.de> <74E4AF57-3D22-415E-B913-176753B09B16@lassitu.de> <710E2C7A-E9AC-4103-8C61-0EDC4A3AF9DE@lassitu.de> Date: Mon, 12 Dec 2011 02:28:29 -0800 X-Google-Sender-Auth: 8YzR6wWeXgrnEWPUuKgnfP9Fydk Message-ID: From: Adrian Chadd To: Stefan Bethke Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-embedded@freebsd.org Subject: Re: TL-WR1043: switch X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2011 10:28:31 -0000 (bah, being in the wrong timezone sucks.) On 11 December 2011 12:54, Stefan Bethke wrote: > Am 11.12.2011 um 21:28 schrieb Adrian Chadd: > >> Hm, so - how does this expose the CPU facing port(s), if any? >> >> ray@ is trying to figure out how to expose the arge0/arge1 interface >> (as he's got at least one board where the switch PHY hangs off of >> arge1, not arge0) so things are probed/attached "right". >> >> That discussion may be worth having here. :) > > The RTL8366 family of switches has a GMII interface to hook up an etherne= t controller. =A0MDC/MDIO are not connected to the ethernet controller, ins= tead register access is through this I2C-like interface, which on the TL-WR= 1043ND is through two GPIOs. Right. So all the PHY access/glue has to come out of this i2c style bus. > The RTL8306SD (which is used for example in the Linksys WRT160NL) has two= MII ports. One is always used to connect a CPU, while the second one can b= e configured to either communicate with the switch or with one specific PHY= . > I believe the WRT160NL uses the latter mode, using the first ethernet por= t of the CPU to talk to the switch ("LAN"), and the second one to the PHY (= "WAN"). It exposes both the five PHYs via MDC/MDIO, as well as switch confi= guration. =A0Unfortunately, the configuration registers are spread out over= all the PHYs, so you can't cleanly isolate the PHYs from the switch portio= n. =A0Since the switch has only one set of MDC/MDIO, both ethernet controll= ers share the same minibus (and both driver instances need to work on just = the one instance). =A0For arge1, using the appropriate phymask should be su= fficient. Right. This I think is one of those places where it gets ugly. > We already have PHY support for the similar RTL8305 in the tree (sys/dev/= mii/rlswitch.c), which does configure the switch. =A0I haven't looked at ho= w it handles the multiple exposed PHYs. > > BTW, would it make sense to put all this info up on a wiki page somewhere= ? =A0I'm optimistic that we can flesh the code out in the next couple of we= eks, but it would be sad to bury all the additional information just in the= mailing list archives. I'm happy for you to do this. Create a wiki.freebsd.org account and tell me what your username is; I'll then throw your account into the right group to let you modify things. >> Whats RTL8366RB_SGCR_EN_VLAN_4KTB do? > > The switch also supports a mode where theres a configuration per VID, so = it can support all possible VIDs (1-4094). =A0I cna add the code, but I don= 't think it really adds that many real-world functionality. Well, as a network engineer of sorts, I'd like to be able to glue these devices into the full VLAN space. I have a habit at home of using VLANs in ranges, so I tend to use VLANs right up to 4000. :) How difficult does it look? Does it change how the VLANs are actually configured? Adrian