From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] More sanely debloating wifi aggregates
Date: Thu, 13 Dec 2012 11:42:57 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1212131140360.25390@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw4DQnufZ24sbWWUV9BQESGTZZfv5K15LB_M6PkO==DRkA@mail.gmail.com>
On Wed, 12 Dec 2012, Dave Taht wrote:
> It is my intent to start working harder on wifi issues next year.
>
> Regardless of how much I care about fixing APs, the biggest user of
> linux based wifi is android, so it makes sense to be hacking on that,
> rather than the crappy iwl chip in most of my machines. (I have ath9k
> cards, tho)
>
> I'm getting an android tablet for christmas (any recommendations?
> Obviously Cyanogenmod is going to have to be supported... What wifi
> chipsets are in use?)
Very few android manufacturers really support hacking the devices, the Nexus
line direct from Google is both among the best price/performance and with device
hacking supported. I haven't looked into the chipsets (I just recieved my Nexus
10)
David Lang
prev parent reply other threads:[~2012-12-13 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 9:08 Dave Taht
2012-12-13 19:42 ` 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
* 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.1212131140360.25390@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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