From: John Yates <john@yates-sheets.org>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] Google's OnHub?
Date: Tue, 2 Feb 2016 21:42:38 -0500 [thread overview]
Message-ID: <CAJnXXoijj579QSEK+u6C=123hdK8=xVx=9qRW9F_Pkbeze2U0Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
Google seems to have taken an interest in WiFi routers:
https://on.google.com/hub/
The OnHub sports an impressive complement of antennae:
- 6 x 2.4GHz
- 6 x 5GHz
- 1 congestion sensing (?)
From this arstechnica review
<http://arstechnica.com/gadgets/2015/08/google-onhub-review-googles-smart-home-trojan-horse-is-a-200-leap-of-faith/>
:
We do know that this little router is packing a ton of processing
horsepower. The OnHub is powered by a Qualcomm IPQ8064—a close cousin of
the Snapdragon 600 (APQ8064). It's a dual core 1.4GHz SoC using the Krait
300 CPU architecture. The difference between the "AP" SoCs that usually
ship in smartphones and the "IP" SoC here is the removal of
smartphone-specific features like support for a display, camera, and
cellular modem. Together with 1GB of RAM and 4GB of storage, the OnHub has
stratospherically-high specs for a router.
Nmap’s OS detection guessed the OnHub to be running "Linux 3.2 - 3.19." OnHub's
license page <https://support.google.com/onhub/answer/6257015> makes
several mentions of Gentoo and Chrome OS. According to *The Financial Times
<http://www.ft.com/intl/cms/s/0/4502b18e-4538-11e5-af2f-4d6e0e5eda22.html#ixzz3jBWn2RF9>*,
OnHub was a project from the Chrome and Google Fiber teams, so it makes
sense that they would use parts of Chrome OS.
And from this subsequent tear-down
<http://arstechnica.com/gadgets/2015/09/google-onhub-gets-torn-asunder-reveals-big-speaker-many-antennas/>
there
are other fun radio components:
There's also a Silicon Labs EM3581
<http://www.silabs.com/products/wireless/zigbee/Pages/zigbee-chips-em35x.aspx>
SOC
network co-processor for ZigBee and Skyworks 66109
<http://www.skyworksinc.com/Product/1718/SKY66109-11> 2.4 GHz ZigBee/Smart
Energy front-end module, which are also dormant. Both will be used, not for
Zigbee compatible devices, but for Google's "Thread" protocol. Zigbee and
Thread are both based on 802.15.4 and are hardware compatible, with a
software update able to turn Zigbee devices into Thread devices. There's
also an Atheros 3012-BL3D
<http://www.qca.qualcomm.com/wp-content/uploads/2013/11/AR3012.pdf> Bluetooth
radio, another component that isn't turned on yet.
If we could enlist them in the make-wifi-fast effort mightn't they have the
clout to get us access to the innards of a product that they are sponsoring?
/john
[-- Attachment #2: Type: text/html, Size: 3797 bytes --]
next reply other threads:[~2016-02-03 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 2:42 John Yates [this message]
2016-02-04 23:21 ` David Lang
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJnXXoijj579QSEK+u6C=123hdK8=xVx=9qRW9F_Pkbeze2U0Q@mail.gmail.com' \
--to=john@yates-sheets.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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