Date: Sat, 25 May 2013 00:59:09 +0100 From: Joe Holden <lists@rewt.org.uk> To: Juli Mallett <jmallett@FreeBSD.org> Cc: Aleksandr Rybalko <ray@ddteam.net>, "freebsd-mips@FreeBSD.org" <freebsd-mips@freebsd.org> Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT. Message-ID: <519FFECD.8060905@rewt.org.uk> In-Reply-To: <CACVs6=9VGjgrg%2B3B7x_QQ8=VU0-Z5y_5_swD7GnZCk%2B_gapA1A@mail.gmail.com> References: <CACVs6=_UHMvo6DSyXzvXxJ0eCcSsC%2Bk3yZ42ia5TGzgHduT2zA@mail.gmail.com> <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> <20130523070225.4d9a3a59@zeta.dino.sk> <519DA801.2090205@rewt.org.uk> <20130523075537.37e4bcba@zeta.dino.sk> <CACVs6=-hWxgmUS8fN4_68-di=iZiB-pOeNfh-RfjFRiaOASNTQ@mail.gmail.com> <20130523134206.69ea6994@zeta.dino.sk> <07C411D8-C5D3-4CD4-896B-844F6514C3DF@bsdimp.com> <CACVs6=8FhTND_WtFm%2BmdL2e=DoNXqMsCXg_X8XTNcD9Om6SB7Q@mail.gmail.com> <519E5CFD.7060008@rewt.org.uk> <CACVs6=9a=Bw8GBMdjGXM4OaD0eARdMF2cKYZHwThas_e4ku2Nw@mail.gmail.com> <519F9377.60904@rewt.org.uk> <CACVs6=9VGjgrg%2B3B7x_QQ8=VU0-Z5y_5_swD7GnZCk%2B_gapA1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Juli Mallett wrote: > On Fri, May 24, 2013 at 9:21 AM, Joe Holden <lists@rewt.org.uk> wrote: >> Looks like theres a couple of modifications and seemingly a bunch of missing >> cavium specific bits which presumably is their licensed sdk rather than the >> public one. > > I don't believe so. The cavm-executive* file in the GPL tarball > contains most Cavium-specific code. Then ubnt-platform* contains > support for IPSec offload. And so on. (I decided to just download > another copy and dig through it a little.) > >> Can't see if they do anything different in the available files, but you'll >> probably be able to spot it straight away :) > > You had mentioned you saw something related to the Atheros PHYs, but I > don't see it — am I missing it? > there is a kernel message on boot that alludes to a custom phy driver, but it isn't present in the gpl source. >> http://91.208.177.20/~jwh/ubnt/kernel/arch/mips/cavium-octeon/octeon_info.c >> http://91.208.177.20/~jwh/ubnt/kernel/drivers/net/octeon/ethernet.c >> http://91.208.177.20/~jwh/ubnt/kernel/net/core/dev.c > > I think you're probably listing those files because they contain > 'ubnt', but alas they just contain some stuff related to device > naming. > Like most vendors I suspect they distribute code minus the private stuff >> I'm pretty sure their stock firmware also boots up with something along the >> lines of ath_ubnt_phy driver, will have to double check.. I think I have one >> left with stock firmware > > If you get any more information, that sounds like something that would > be useful. > I'll have a gander but the same string in their binary-only firmware isn't present in the GPL code. > Thanks, > Juli. If you have any tips on what I can experiment with, I'm happy to do that, I have a few ERLs Thanks, Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?519FFECD.8060905>