Date: Mon, 12 Sep 2011 16:36:50 -0500 From: Warner Losh <imp@bsdimp.com> To: Juli Mallett <jmallett@FreeBSD.org> Cc: "mips@freebsd.org" <mips@FreeBSD.org> Subject: Re: Things to tackle in the MIPS space? Message-ID: <130096A5-D938-4140-9B59-0CDDE1C8029A@bsdimp.com> In-Reply-To: <CACVs6=_VFYs6sgjaBP4Ec2dX5k4=MSd=bJmyrWKEOznXxPmUzw@mail.gmail.com> References: <AC6674AB7BC78549BB231821ABF7A9AEB74D600064@EMBX01-WF.jnpr.net> <CACVs6=_VFYs6sgjaBP4Ec2dX5k4=MSd=bJmyrWKEOznXxPmUzw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 12, 2011, at 2:55 PM, Juli Mallett wrote: >> 2) Ehternet support. Also apparently broken, although I know little = about ENET and PHYs and such. We do have people here who do though. >=20 > Um, what happened to Ethernet support? It worked and worked quite > well the last time I touched it. Performance could be better, but > improving performance of the Ethernet driver would probably be a > pretty nasty way to learn about how Ethernet drivers work. (Namely > because it's easy to make the performance much better for a single > case and a lot worse for every other one.) You shouldn't need to know > anything much about how the PHYs work, though. My experience has been mixed. Some boards work great w/o any tweaking = at all. Others don't work at all. Sadly, I've sent back the board I = have that worked and just have one that doesn't work. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?130096A5-D938-4140-9B59-0CDDE1C8029A>