[OpenWrt-Devel] [PATCH] brcm47xx: move wrt610n_v2 and e3000_v1 to mips74k subtarget

Nathan Hintz nlhintz at hotmail.com
Sun Oct 19 03:19:19 EDT 2014

Hi Rafał:

> Date: Sun, 19 Oct 2014 07:48:04 +0200
> Subject: Re: [PATCH] brcm47xx: move wrt610n_v2 and e3000_v1 to mips74k subtarget
> From: zajec5 at gmail.com
> To: nlhintz at hotmail.com
> CC: openwrt-devel at lists.openwrt.org; hauke at hauke-m.de
> On 19 October 2014 00:19, Nathan Hintz <nlhintz at hotmail.com> wrote:
> >> > Neither are "SSB Wifi"
> >>
> >> They are.
> >>
> >> https://wikidevi.com/wiki/Linksys_WRT610N_v2
> >> BCM4322 which is SSB based
> >>
> >> https://wikidevi.com/wiki/Linksys_E3000
> >> BCM4322 which is SSB based
> >>
> >
> > I see your point; however, the E3000 and WRT610Nv2 are mips74k, and would
> > get the same
> > benefit from using the mips74k subtarget (mips32r2) as all of the others.
> > The only difference
> > that I can see is that the E3000 and WRT610nV2 are required to use the
> > proprietary
> > Broadcom wl driver (which is one of the supported profiles under the mips74k
> > subtarget) in
> > order to utilize the 5GHz radio; whereas, with at least some of the others,
> > using the proprietary
> > Broadcom wl driver is optional.  I could modify the patch description to
> > include this info and to
> > keep the "SSB Wifi" comment if you think it is necessary.
> There are few devices we don't have perfect solution for. I'm aware
> that these 2 devices are MIPS 74K, but we're still bound to two
> solutions:
> 1) Use "generic" subtarget for E3000/WRT610Nv2 and make them suffer
> from less optimized code. That's what we do now.
> 2) Use "mips74k" subtarget for them, add "ssb" support to the
> "mips74k", and make firmware bigger for dozens of other devices.

There are no additional "ssb" bits that need to be added to the mips74k subtarget.
The existing mips74k trx works out of the box on E3000 (and should work on
WRT610nV2 as well).  As you mentioned earlier, wl.ko doesn't require any of the
in-kernel SSB parts, as it handles everything it needs internally.  Simply build the
mips74k target as it exists today; include the proprietary driver (or load it separately),
and it all just works.  The patch I've provided should be the only change that is needed
(to build the device specific .bin files).

> In such situation we decided it's better option to make 2 devices
> "suffer" than dozens of other. We can't really afford running buildbot
> with dozens of subtargets.
> And no, forcing E3000/WRT610Nv2 to use closed source drivers, because
> we don't include ssb in a firmware is not an option. We are not DD-WRT
> :P Close source driver could be an *alternative*.
> Btw. b43 recently gained 5 GHz support for N-PHY cards (BCM4322), I'm
> not sure if it's available in BB stable, but should be in CC
> (shapshots) for sure.
> -- 
> Rafał

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20141019/36c2c6d9/attachment.htm>
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list