From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: leetminiwheat <LeetMiniWheat@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
cake@lists.bufferbloat.net
Subject: Re: [Cake] Current status and recommendations for APU2C*/ArcherC7 and ath10k platforms?
Date: Thu, 30 Mar 2017 10:11:20 +0200 [thread overview]
Message-ID: <87r31fyyjb.fsf@alrua-karlstad> (raw)
In-Reply-To: <CAGHZhqHfVsQGgqT7sEsqesf4j7mo5MUoDN_L1MY-Aat0QNWuxA@mail.gmail.com> (leetminiwheat's message of "Thu, 30 Mar 2017 00:08:59 -0400")
leetminiwheat <LeetMiniWheat@gmail.com> writes:
> Apologies I haven't had time to follow recent developments but are there
> any recent bufferbloat/CAKE related news/recommendations for the APU2
> platform? Specifically the APU2C (previous was marvell I believe)
>
> Hardware:
> APU2C4 (AMD x86_64 | 4GB | 3x i210-AT)
> WLE600VX (ath10k)
> 64GB mSATA
>
> Also have an Archer C7 V2 (ath10k) and a old WDR3800 (ath9k) still
> chugging along.
>
> Looking for an optimal Archer C7 build or recommendations if anyone
> has any experience on it.
The 17.01 LEDE release is great for both the C7 and the WNDR3800, and
has all the WiFi-related fixes (bufferbloat fixes and airtime fairness)
included. You'll probably need something beefier for a main gateway at
those speeds, though. Not sure about the APU2; think it is supported in
LEDE as well?
-Toke
prev parent reply other threads:[~2017-03-30 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 4:08 leetminiwheat
2017-03-30 8:11 ` Toke Høiland-Jørgensen [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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r31fyyjb.fsf@alrua-karlstad \
--to=toke@toke.dk \
--cc=LeetMiniWheat@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@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