From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4CDE03B2C4; Sun, 13 Mar 2016 20:51:15 -0400 (EDT) Received: by mail-ig0-x234.google.com with SMTP id mh10so3104083igb.0; Sun, 13 Mar 2016 17:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=GhIObk95h3ho9oGbjOiy5nga9tBkPP7BafO5iDu2tOs=; b=zBAxJkxvjVsFL2io7r/h/OhrV3+FgaZHlxi+6ZNhlYVsZx4szdpm6QCP95eSbmzsRB VEhsXEyZ8soaUGWf6P20j1uBTScEBUoggFsoPSpD1p0QU4ccENHnHzOfy1gJDL0pFJ4I 3w6PRrUDw6nzyJkBgGiOFlqrUErsOSm91irYWXgr2q34WmfQ6Tc2hIHjFGfKSIJ+nIhp xMbm1QLLgsI0fm4xcvk9T8dppP9wSTyN43vRePXGbfOPg69c36/ReCbXNOMzVaDJuwSS 5Ulop68JsPRE54+VoUDPFF+SxPEQ8Msl9NSluWZhFe//Hv1+Loc9m7T7+4GEADZCfaQh jj3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=GhIObk95h3ho9oGbjOiy5nga9tBkPP7BafO5iDu2tOs=; b=dLJEBHVyXOv/6ikWOnoGrIKuflasN7a5rOWFlazip25oRrAX1yrDKv41KigQeMv8Ef q9xpwcjJ/RpactitxuRrUk26nyZ8oTi3T5aCg0VKq7Kg8Y5GWoDqf0LEfahKDa/zau5I 6r4jhIcPx6zCBEbmXIxiu6v/p60n2h6py2YP3+hpHeK/YH+70AffcTLQiiKt1/xHZjjw nWVuGO5yMPUjnMAfv/J+WMNTPyP53AZXz4A5UObbs1sMrnUNQzcwem3TDtekXGSdgdG/ XMRgzTl3ZRKoCtOSmZLelnpvhqXgppi+GZ58IUtoTP8tl88IMoroaZMevDD5BAjV8eSM TRCA== X-Gm-Message-State: AD7BkJIWe19jL9+Qb0nvFcLPcXDOdb616IOhruTbo+M56G3cBCTC+0Vdv4PeCOo0qVq9s1VkCUeTzsCcD2d9lQ== MIME-Version: 1.0 X-Received: by 10.50.36.105 with SMTP id p9mr14091298igj.22.1457916674737; Sun, 13 Mar 2016 17:51:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.14.19 with HTTP; Sun, 13 Mar 2016 17:51:13 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Sun, 13 Mar 2016 17:51:13 -0700 (PDT) In-Reply-To: References: Date: Sun, 13 Mar 2016 17:51:13 -0700 X-Google-Sender-Auth: ykFhrMjHkhk3TrLFPMBWVoSLiGw Message-ID: From: Adrian Chadd To: David Lang Cc: bufferbloat-fcc-discuss , cerowrt-devel@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net, Henning Rogge Content-Type: multipart/alternative; boundary=089e01176343828dba052df7ada1 X-Mailman-Approved-At: Wed, 16 Mar 2016 11:41:57 -0400 Subject: Re: [Make-wifi-fast] [bufferbloat-fcc-discuss] arstechnica confirms tp-link router lockdown X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 00:51:15 -0000 --089e01176343828dba052df7ada1 Content-Type: text/plain; charset=UTF-8 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" wrote: > On Sat, 12 Mar 2016, Adrian Chadd wrote: > > On 12 March 2016 at 11:14, Henning Rogge wrote: >> >>> On Sat, Mar 12, 2016 at 3:32 PM, Wayne Workman >>> 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 > --089e01176343828dba052df7ada1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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 ea= ch antenna so that the interference patterns from the different signals res= ult in different readable data depending on where the receiver is in relati= on to the access point is not a trivial thing.

But it's one of the most valuable features in the spec.

David Lang
--089e01176343828dba052df7ada1--