From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by huchra.bufferbloat.net (Postfix) with ESMTPS id CC20D21F77D
	for <cerowrt-devel@lists.bufferbloat.net>;
	Tue, 18 Aug 2015 13:44:16 -0700 (PDT)
Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100])
	by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id
	t7IKiA26017403; Tue, 18 Aug 2015 13:44:10 -0700
Date: Tue, 18 Aug 2015 13:44:10 -0700 (PDT)
From: David Lang <david@lang.hm>
X-X-Sender: dlang@asgard.lang.hm
To: Matt Taggart <matt@lackof.org>
In-Reply-To: <20150818203315.DF3861EF@taggart.lackof.org>
Message-ID: <alpine.DEB.2.02.1508181342230.27696@nftneq.ynat.uz>
References: <20150818200840.31F771EF@taggart.lackof.org>
	<20150818203315.DF3861EF@taggart.lackof.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] google wifi
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2015 20:44:39 -0000

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:
>
> <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
> server.
> <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"

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