[Cerowrt-devel] google wifi
david at lang.hm
Tue Aug 18 16:44:10 EDT 2015
On Tue, 18 Aug 2015, Matt Taggart wrote:
> Matt Taggart writes:
>> Google is working with TP-LINK (and soon ASUS) on wifi (is there a
>> make-wifi-fast list this should have gone to?)
>> Google Blog: Meet OnHub: a new router for a new way to Wi-Fi
>> product page
> I talked to a friend that worked on it:
> <ggg> the kernel for the Onhub router is under "whirlwind" project
> name in the chromium.org source tree. The firmware is coreboot and is
> also public.
> <ggg> Openwrt has all the support for the Qualcom chipset but not
> this board.
> <ggg> Openwrt also require fastboot and won't work with Coreboot.
> <ggg> Key bits are the Device Tree description of the HW in this directory:
> <ggg> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/arch/arm/boot/dts/
> <ggg> qcom-apq8084-mtp.dts
> <ggg> qcom-apq8084.dtsi
> <ggg> qcom-ipq8064-ap148.dts
> <ggg> qcom-ipq8064-arkham.dts
> <ggg> qcom-ipq8064-storm.dts
> <ggg> qcom-ipq8064-thermal.dtsi
> <ggg> qcom-ipq8064-v1.0.dtsi
> <ggg> qcom-ipq8064-whirlwind-sp3.dts
> <ggg> qcom-ipq8064-whirlwind-sp5.dts
> <ggg> qcom-ipq8064.dtsi
> <ggg> whirlwind-sp5 is what shipped. (AFAIK)
> <ggg> btw, all of this was reviewed on a public chromium.org gerrit
> <ggg> openwrt does support AP148
> <ggg> and at some point chromeos was booting on AP148 though I don't
> expect it to work "out of the box"
how open is the wifi driver? Is it something that we can dive into and modify
for make-wifi-fast? or is it a typical vendor blob?
More information about the Cerowrt-devel