From owner-freebsd-mips@FreeBSD.ORG Mon Sep 12 23:17:46 2011 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A87111065702 for ; Mon, 12 Sep 2011 23:17:46 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 448CD8FC0A for ; Mon, 12 Sep 2011 23:17:46 +0000 (UTC) Received: by wwe3 with SMTP id 3so2777678wwe.31 for ; Mon, 12 Sep 2011 16:17:45 -0700 (PDT) Received: by 10.227.59.83 with SMTP id k19mr620637wbh.67.1315869465185; Mon, 12 Sep 2011 16:17:45 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.227.117.8 with HTTP; Mon, 12 Sep 2011 16:17:25 -0700 (PDT) In-Reply-To: <130096A5-D938-4140-9B59-0CDDE1C8029A@bsdimp.com> References: <130096A5-D938-4140-9B59-0CDDE1C8029A@bsdimp.com> From: Juli Mallett Date: Mon, 12 Sep 2011 16:17:25 -0700 X-Google-Sender-Auth: jkW0wq77dBhKECeRtwDvnPmJ2PM Message-ID: To: Warner Losh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "mips@freebsd.org" Subject: Re: Things to tackle in the MIPS space? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 23:17:46 -0000 On Mon, Sep 12, 2011 at 14:36, Warner Losh wrote: > > On Sep 12, 2011, at 2:55 PM, Juli Mallett wrote: >>> 2) Ehternet support. Also apparently broken, although I know little abo= ut ENET and PHYs and such. We do =C2=A0have people here who do though. >> >> Um, what happened to Ethernet support? =C2=A0It worked and worked quite >> well the last time I touched it. =C2=A0Performance could be better, but >> improving performance of the Ethernet driver would probably be a >> pretty nasty way to learn about how Ethernet drivers work. =C2=A0(Namely >> because it's easy to make the performance much better for a single >> case and a lot worse for every other one.) =C2=A0You shouldn't need to k= now >> anything much about how the PHYs work, though. > > My experience has been mixed. =C2=A0Some boards work great w/o any tweaki= ng at all. =C2=A0Others don't work at all. =C2=A0Sadly, I've sent back the = board I have that worked and just have one that doesn't work. For the sake of not sewing unnecessary confusion on the list, I just want to add that this is almost certainly because of deficiencies in board support code in the Simple Executive, which I'm happy to help fix for boards that have patches against any version of the Cavium SDK/Linux, than because the driver doesn't work, as was intimated earlier.