From owner-freebsd-mips@FreeBSD.ORG  Tue May 21 14:39:21 2013
Return-Path: <owner-freebsd-mips@FreeBSD.ORG>
Delivered-To: freebsd-mips@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id DED1B34A;
 Tue, 21 May 2013 14:39:21 +0000 (UTC)
 (envelope-from lists@rewt.org.uk)
Received: from hosted.mx.as41113.net (hosted.mx.as41113.net [91.208.177.22])
 by mx1.freebsd.org (Postfix) with ESMTP id A27646E4;
 Tue, 21 May 2013 14:39:21 +0000 (UTC)
Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 (Authenticated sender: lists@rewt.org.uk)
 by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bFKNz6NNvz1Tr;
 Tue, 21 May 2013 15:39:15 +0100 (BST)
Message-ID: <519B8706.1090409@rewt.org.uk>
Date: Tue, 21 May 2013 15:39:02 +0100
From: Joe Holden <lists@rewt.org.uk>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT.
References: <CACVs6=_UHMvo6DSyXzvXxJ0eCcSsC+k3yZ42ia5TGzgHduT2zA@mail.gmail.com>	<20130516111059.38543d57@wind.dino.sk>	<20130516131642.adfae355aa3bf7767e9b56e5@ddteam.net>	<20130516124248.33ae4e05@wind.dino.sk>	<51952112.9010607@rewt.org.uk>	<20130517192206.5db0533f@zeta.dino.sk>	<51966CB6.2040701@rewt.org.uk>	<CACVs6=-0URQ2f7UqVxRdpuGpf103KOW9CTF6FFCGaGhvg3jOMw@mail.gmail.com>	<20130520110659.1d1d2165@zeta.dino.sk>	<D1F45DEB-3C3C-42D1-8EDE-94B18AB32152@bsdimp.com>	<20130520164001.5f7d99b8@zeta.dino.sk>	<C48F8AE6-316B-4C4A-AD2B-739C698B0AAC@bsdimp.com>	<20130520172508.087daf7b@zeta.dino.sk>	<CACVs6=8_y5Rqo9UHnQwbEancfZOqrqEAhcu=EXGGSGLjvayKVg@mail.gmail.com>	<20130520173934.099ea541@zeta.dino.sk>	<519A605D.8020304@rewt.org.uk>
 <CAJ-Vmom82-oOfCgRtUgwXeoARa4aAWB-FjtbV451aLbCZj6Fxw@mail.gmail.com>
In-Reply-To: <CAJ-Vmom82-oOfCgRtUgwXeoARa4aAWB-FjtbV451aLbCZj6Fxw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Aleksandr Rybalko <ray@ddteam.net>,
 "freebsd-mips@FreeBSD.org" <freebsd-mips@freebsd.org>
X-BeenThere: freebsd-mips@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-mips>,
 <mailto:freebsd-mips-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mips>
List-Post: <mailto:freebsd-mips@freebsd.org>
List-Help: <mailto:freebsd-mips-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
 <mailto:freebsd-mips-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 14:39:21 -0000

Adrian Chadd wrote:
> On 20 May 2013 10:41, Joe Holden <lists@rewt.org.uk> wrote:
> 
>> Hm, I do recall seeing something in a document somewhere that suggested it
>> used gpio/i2c to talk to the PHYs due to the design they've used, is there
>> any way of dumping accesses/messages across gpio pins (without soldering) ?
> 
> CAn you dig that up?
> 
> Is it something where they've glued a PHY to a GPIO that needs to be
> bit banged in software, or is this something automatic where they put
> the GPIO pins into a "I'm a PHY!" mode, and the ethernet controller
> speaks to it?
> 
> 
> 
> Adrian
hm, can't find it in the doc I thought it was in (hardware reference) - 
may have been in relation to RGMII rather than specifically the erl.

If they're using those gpio pins for RGMII signalling then tickling them 
may well cause link negotiation problems I'd have thought