Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Bob McMahon <bob.mcmahon@broadcom.com>
Cc: Pete Heist <peteheist@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Flent test hardware
Date: Sun, 5 Nov 2017 14:13:35 +0200	[thread overview]
Message-ID: <CAJq5cE0RrjFcw6rXd1YojPAEsKU2NK=AsyMU62HcsuT1Vn2Ktw@mail.gmail.com> (raw)
In-Reply-To: <CAHb6Lvo_nr4bXMVOvFBT8P4Dx0spmBmQvM_fJ3bdeVc8==eXnw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

I'm currently using an AMD APU system on an AsRock mini-ITX board as my
primary computer.  That happened to come with Atheros network hardware,
both wired and wireless.

With a little effort, it could be squeezed into a very small case indeed,
and the major components can probably be found on clearance since the Ryzen
release.  APUs' CPU cores are hardly state of the art, but quick enough for
this sort of job and sometimes very cheap indeed.

The m/board model I have is FM2A88X-ITX+.  Note that the later "/ac" model
goes back to a Realtek wired chipset.  If you can stand a larger form
factor, the FM2A88M Extreme4+ R2.0 is another option to compare on price,
though it doesn't come with a wifi card.

In the current AsRock lineup for the AM4 socket, it appears that some
models in their Fatal1ty line use Intel NICs.  Pair one of those with a
Bristol Ridge APU for now, and you'll be able to upgrade to Zen based Raven
Ridge APUs, expected to be easily twice as fast, when they become available.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 1146 bytes --]

  reply	other threads:[~2017-11-05 12:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 13:33 Pete Heist
2017-11-04 15:06 ` Sebastian Moeller
2017-11-04 16:33   ` Pete Heist
2017-11-04 17:25     ` Sebastian Moeller
2017-11-04 18:45       ` Pete Heist
2017-11-05  1:42 ` Bob McMahon
2017-11-05 12:13   ` Jonathan Morton [this message]
2017-11-05 14:23     ` Pete Heist
     [not found]       ` <CAJq5cE0nkn+iDP9NuU2aoSk_G+2cxkZYShj9PfK5u=Fr7fTrLA@mail.gmail.com>
     [not found]         ` <CAJq5cE13M=fmyh2oQ5UxFCOcoPhZ2nOPEkqRWcT-UdGT60=ezA@mail.gmail.com>
     [not found]           ` <CAJq5cE1KQ+K9x7k+bnuFvqyNhjsg6mSn_CU4b0h8S1bwo5SXOg@mail.gmail.com>
     [not found]             ` <CAJq5cE2Tk_TAHES+7O28MjryG-nYHRNJ5OB9WjsCXGSfEgORog@mail.gmail.com>
     [not found]               ` <CAJq5cE0xkhbXYZ4c1+-9FmKOv1_DFFMJh8hqa-W8jEx+K_xTFg@mail.gmail.com>
2017-11-05 16:24                 ` Jonathan Morton
2017-11-05 17:39                   ` Pete Heist
2017-11-05 18:08                     ` Jonathan Morton
2017-11-05 18:42                       ` Pete Heist
2017-11-05 20:15                         ` Jonathan Morton
2017-11-07  0:32                           ` Pete Heist
2017-11-05 13:57   ` Pete Heist
2017-11-05 19:42     ` Bob McMahon
2017-11-05 21:41       ` Pete Heist
2017-11-06 20:15     ` Isaac Konikoff
2017-11-06 21:29       ` Bob McMahon
2017-11-07  0:39 ` Dave Taht
2017-11-07  1:37   ` Pete Heist
2017-11-07 10:21     ` Pete Heist
2017-11-08  4:46       ` Bob McMahon

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='CAJq5cE0RrjFcw6rXd1YojPAEsKU2NK=AsyMU62HcsuT1Vn2Ktw@mail.gmail.com' \
    --to=chromatix99@gmail.com \
    --cc=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=peteheist@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