Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Matt Taggart <matt@lackof.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] google wifi
Date: Tue, 18 Aug 2015 13:44:10 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1508181342230.27696@nftneq.ynat.uz> (raw)
In-Reply-To: <20150818203315.DF3861EF@taggart.lackof.org>

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

  reply	other threads:[~2015-08-18 20:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 20:08 Matt Taggart
2015-08-18 20:33 ` Matt Taggart
2015-08-18 20:44   ` David Lang [this message]
2015-08-18 20:56     ` Dave Taht
2015-08-19 17:38       ` Isaac Konikoff
2015-08-19 18:09         ` Mikael Abrahamsson
2015-08-19 18:16           ` Jonathan Morton
2015-09-22 22:08       ` Isaac Konikoff
2015-10-01 18:48         ` Isaac Konikoff
2015-08-18 21:18     ` Matt Taggart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1508181342230.27696@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=matt@lackof.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox