From: Adrian Chadd <adrian@freebsd.org>
To: David Lang <david@lang.hm>
Cc: bufferbloat-fcc-discuss
<bufferbloat-fcc-discuss@lists.redbarn.org>,
cerowrt-devel@lists.bufferbloat.net,
make-wifi-fast@lists.bufferbloat.net,
Henning Rogge <hrogge@gmail.com>
Subject: Re: [Make-wifi-fast] [bufferbloat-fcc-discuss] arstechnica confirms tp-link router lockdown
Date: Sun, 13 Mar 2016 17:51:13 -0700 [thread overview]
Message-ID: <CAJ-VmoneRhDXKEd5-v4FtRCiS+YmVrwedMhb3OsjzPiZ7L7HuQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1603121701350.23224@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
You do that in hardware. Do the Mac, phy and RF in hardware.
This is what the qca hardware does.
a
On Mar 13, 2016 5:25 PM, "David Lang" <david@lang.hm> wrote:
> On Sat, 12 Mar 2016, Adrian Chadd wrote:
>
> On 12 March 2016 at 11:14, Henning Rogge <hrogge@gmail.com> wrote:
>>
>>> On Sat, Mar 12, 2016 at 3:32 PM, Wayne Workman
>>> <wayne.workman2012@gmail.com> wrote:
>>>
>>>> I understand that Broadcom was paid to develop the Pi, a totally free
>>>> board.
>>>>
>>>> And they already make wireless chipsets.
>>>>
>>>
>>> The question is how easy would it be to build a modern 802.11ac
>>> halfmac chip... the amount of work these chips do (especially with 3*3
>>> or 4*4 MIMO) is not trivial.
>>>
>>
>> It's not that scary - most of the latency sensitive things are:
>>
>> * channel change - eg background scans
>> * calibration related things - but most slow calibration could be done
>> via firmware commands, like the intel chips do!
>> * transmit a-mpdu / retransmit
>> * transmit rate control adaptation
>> * receiving / block-ack things - which is mostly done in hardware anyway
>> * likely some power save transition-y things too
>>
>
> you are ignoring MU-MIMO, the ability to transmit different signals from
> each antenna so that the interference patterns from the different signals
> result in different readable data depending on where the receiver is in
> relation to the access point is not a trivial thing.
>
> But it's one of the most valuable features in the spec.
>
> David Lang
>
[-- Attachment #2: Type: text/html, Size: 2306 bytes --]
next prev parent reply other threads:[~2016-03-14 0:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 18:17 [Make-wifi-fast] " Dave Taht
2016-03-11 18:22 ` [Make-wifi-fast] [Cerowrt-devel] " Luis E. Garcia
2016-03-11 19:07 ` Jonathan Morton
2016-03-11 19:31 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Paul Vixie
2016-03-11 20:26 ` [Make-wifi-fast] " Alan Jenkins
2016-03-11 20:40 ` David Lang
2016-03-12 9:38 ` Jonathan Morton
2016-03-13 0:15 ` David Lang
2016-03-13 15:18 ` Jonathan Morton
2016-03-13 17:40 ` moeller0
2016-03-13 18:17 ` Jonathan Morton
2016-03-13 18:25 ` moeller0
2016-03-13 20:15 ` Jonathan Morton
2016-03-13 21:17 ` moeller0
[not found] ` <CAEfCu-p+87PkRrN-=9=-CA3JpQesRU2RDmxN-yEJt_95Au-yxA@mail.gmail.com>
2016-03-13 17:48 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Dave Taht
2016-03-13 18:23 ` [Make-wifi-fast] [Cerowrt-devel] [bufferbloat-fcc-discuss] " moeller0
2016-03-13 23:22 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] [Cerowrt-devel] " David Lang
[not found] ` <CAEfCu-o7hb+6O0NNc4oUrn7noaVvBhBJK3zNjB8mWtgVtkqpZg@mail.gmail.com>
2016-03-14 1:03 ` David Lang
[not found] ` <CAEfCu-rQN+H7h0OY_3CSrrGcVZ=A4=b0XTAU2h3Pz3_ksh56dw@mail.gmail.com>
2016-03-12 19:14 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Henning Rogge
2016-03-12 20:18 ` Adrian Chadd
[not found] ` <CAEfCu-rmR=p1bAGJjPvaMMBAjKRU1wBeZW4ZQCZVm5eVXCCRQQ@mail.gmail.com>
2016-03-12 22:20 ` Dave Taht
2016-03-13 1:04 ` David Lang
[not found] ` <CAEfCu-r-C3C6P2LpKJduvX733YnbwxBF6nOFAPEMbF28qjRXBg@mail.gmail.com>
2016-03-13 8:06 ` David Lang
2016-03-14 0:51 ` Adrian Chadd [this message]
2016-03-14 1:25 ` David Lang
2016-03-13 18:19 ` Dave Taht
2016-03-13 1:00 ` David Lang
2016-03-13 13:25 Brandon Butterworth
2016-03-13 23:20 ` 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=CAJ-VmoneRhDXKEd5-v4FtRCiS+YmVrwedMhb3OsjzPiZ7L7HuQ@mail.gmail.com \
--to=adrian@freebsd.org \
--cc=bufferbloat-fcc-discuss@lists.redbarn.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=hrogge@gmail.com \
--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