Routers and FCC requirements - one approach to keeping dev open

[sfx2000]

Side note - this article is a bit of a PR, but the principles are similar to what various OEM's are doing to keep things open for 3rd party development

http://hackerboards.com/mips-vm-tech-lets-routers-stay-open-despite-new-fcc-rules/

Interesting read and approach though...

 

[RMerlin]

Running the wifi separately from the rest of the firmware. Where have I seen something like that? Oh right, Quantenna...

Broadcom's current DHD architecture could probably do just the same, by loading the CLM data into the SoC's dedicated CPU. It's in fact what Asus started doing with their current generation of BCM routers.

 

[sfx2000]

Running the wifi separately from the rest of the firmware. Where have I seen something like that? Oh right, Quantenna...

Broadcom's current DHD architecture could probably do just the same, by loading the CLM data into the SoC's dedicated CPU. It's in fact what Asus started doing with their current generation of BCM routers.

Broadcom has run their own private RTOS inside their chips for quite some time... the STA drive only shows how one can interact with the RTOS. QCA, Marvell, and others are similar.

The MIPS article is interesting as this is a nice view inside something that is typically hidden - aka QTN and others.