From: David Lang <david@lang.hm>
To: John Yates <john@yates-sheets.org>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Google's OnHub?
Date: Thu, 4 Feb 2016 15:21:24 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1602041519390.3665@nftneq.ynat.uz> (raw)
In-Reply-To: <CAJnXXoijj579QSEK+u6C=123hdK8=xVx=9qRW9F_Pkbeze2U0Q@mail.gmail.com>
This was discussed a bit back when this product was first announced. I don't
remember the details, but I recall that the response was that they weren't
pushing for open drivers/firmware to the level that we believe is needed to be
able to address issues.
I agree it's a very interesting bit if kit. but without the ability to go in and
change the drivers, we're pretty stuck
David Lang
On Tue, 2 Feb 2016, John Yates wrote:
> 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
>
prev parent reply other threads:[~2016-02-04 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 2:42 John Yates
2016-02-04 23:21 ` David Lang [this message]
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=alpine.DEB.2.02.1602041519390.3665@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=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