Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] anyone have real info on the google router?
Date: Wed, 19 Aug 2015 08:02:24 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1508190759220.13227@uplift.swm.pp.se> (raw)
In-Reply-To: <alpine.DEB.2.02.1508182114400.23683@nftneq.ynat.uz>

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 Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2015-08-19  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 19:31 David Lang
2015-08-19  1:57 ` Jim Gettys
2015-08-19  4:16   ` David Lang
2015-08-19  6:02     ` Mikael Abrahamsson [this message]
2015-08-19  9:47   ` Steven Barth
2015-08-19 17:55     ` David Lang
2015-08-19 18:10       ` Mikael Abrahamsson
2015-08-19 18:49       ` Steven Barth

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.1508190759220.13227@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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