[Cerowrt-devel] anyone have real info on the google router?
http://googleblog.blogspot.com/2015/08/meet-onhub-new-router-for-new-way-to-wi.html specifically the issues of firmware and drivers? David Lang ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
[Cerowrt-devel] google wifi
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 https://tinyurl.com/nloy3jm product page https://on.google.com/hub/ -- Matt Taggart m...@lackof.org ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] google wifi
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 > https://tinyurl.com/nloy3jm > > product page > https://on.google.com/hub/ I talked to a friend that worked on it: 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. Openwrt has all the support for the Qualcom chipset but not this board. Openwrt also require fastboot and won't work with Coreboot. Key bits are the Device Tree description of the HW in this directory: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/arch/arm/boot/dts/ qcom-apq8084-mtp.dts qcom-apq8084.dtsi qcom-ipq8064-ap148.dts qcom-ipq8064-arkham.dts qcom-ipq8064-storm.dts qcom-ipq8064-thermal.dtsi qcom-ipq8064-v1.0.dtsi qcom-ipq8064-whirlwind-sp3.dts qcom-ipq8064-whirlwind-sp5.dts qcom-ipq8064.dtsi whirlwind-sp5 is what shipped. (AFAIK) btw, all of this was reviewed on a public chromium.org gerrit server. openwrt does support AP148 and at some point chromeos was booting on AP148 though I don't expect it to work "out of the box" -- Matt Taggart m...@lackof.org ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] google wifi
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 https://tinyurl.com/nloy3jm product page https://on.google.com/hub/ I talked to a friend that worked on it: 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. Openwrt has all the support for the Qualcom chipset but not this board. Openwrt also require fastboot and won't work with Coreboot. Key bits are the Device Tree description of the HW in this directory: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/arch/arm/boot/dts/ qcom-apq8084-mtp.dts qcom-apq8084.dtsi qcom-ipq8064-ap148.dts qcom-ipq8064-arkham.dts qcom-ipq8064-storm.dts qcom-ipq8064-thermal.dtsi qcom-ipq8064-v1.0.dtsi qcom-ipq8064-whirlwind-sp3.dts qcom-ipq8064-whirlwind-sp5.dts qcom-ipq8064.dtsi whirlwind-sp5 is what shipped. (AFAIK) btw, all of this was reviewed on a public chromium.org gerrit server. openwrt does support AP148 and at some point chromeos was booting on AP148 though I don't expect it to work "out of the box" sounds promising. 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? David Lang ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] google wifi
I would like very much for someone from this group to put this box through it's paces with flent on the isp side, and to test the wifi side with the rtt_fair tests, and publish their results. ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] google wifi
David Lang writes: > 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 info.. ath10k ChromeOS uses tools to share/merge config files. The config parts specific to OnHub are here: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/chromeos/config/armel/chromiumos-ipq806x.flavour.config it's using a v3.18 kernel mac80211 code base. (USE="wireless318") -- Matt Taggart m...@lackof.org ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] anyone have real info on the google router?
On Tue, Aug 18, 2015 at 3:31 PM, David Lang wrote: > > http://googleblog.blogspot.com/2015/08/meet-onhub-new-router-for-new-way-to-wi.html > > specifically the issues of firmware and drivers? It runs a very recent kernel (3.18, IIRC). The devel prototype originally ran OpenWrt; should be pretty easy to make OpenWrt run on it again. Has a speaker on it (so you can do proof of actual presence to help bootstrap security stuff). Ath10k wireless. Has a TPM module on board, so you could do a poor man's hsm for storing keys. Android style unlockable bootloader. The intent is it be an open platform. Has a hardware packet assist engine: there will be the usual issues of latency vs. bandwidth; not much use of that this instant. Current software admin is done entirely via Android apps and a google back end: no web gui for it at the moment (Trond isn't comfortable with a web server on the router). Secure upgrade of the firmware. - Jim > > David Lang > ___ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] anyone have real info on the google router?
On Tue, 18 Aug 2015, Jim Gettys wrote: On Tue, Aug 18, 2015 at 3:31 PM, David Lang wrote: http://googleblog.blogspot.com/2015/08/meet-onhub-new-router-for-new-way-to-wi.html specifically the issues of firmware and drivers? It runs a very recent kernel (3.18, IIRC). The devel prototype originally ran OpenWrt; should be pretty easy to make OpenWrt run on it again. Has a speaker on it (so you can do proof of actual presence to help bootstrap security stuff). Ath10k wireless. Has a TPM module on board, so you could do a poor man's hsm for storing keys. IIRC the Ath10k wireless is not very hackable (big binary blob), so that would mean that unless Google has been able to do something new here, it's not very hackable for make-wifi-fast. Am I remembering correctly? otherwise it sounds like a nice device for the price. David Lang Android style unlockable bootloader. The intent is it be an open platform. Has a hardware packet assist engine: there will be the usual issues of latency vs. bandwidth; not much use of that this instant. Current software admin is done entirely via Android apps and a google back end: no web gui for it at the moment (Trond isn't comfortable with a web server on the router). Secure upgrade of the firmware. - Jim David Lang ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
Re: [Cerowrt-devel] anyone have real info on the google router?
On Tue, 18 Aug 2015, David Lang wrote: IIRC the Ath10k wireless is not very hackable (big binary blob), so that would mean that unless Google has been able to do something new here, it's not very hackable for make-wifi-fast. Am I remembering correctly? otherwise it sounds like a nice device for the price. The IPQ8064 from Qualcomm might become more FOSS-friendly over time, Qualcomm seems to be going in the right direction, but right now it's fairly closed down. So no, I don't see this platform as a short term make-wifi-fast development platform, at least not without getting Qualcomm onboard and working closely with the project. If I understand correctly, we have both the packet accelerator (closed source) and the ATH10K wireless (closed source) to contend with. -- Mikael Abrahamssonemail: swm...@swm.pp.se ___ Cerowrt-devel mailing list Cerowrt-devel@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cerowrt-devel
