Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Matt Taggart <matt@lackof.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Intel latency issue
Date: Sun, 04 Dec 2016 00:25:35 -0800	[thread overview]
Message-ID: <20161204082535.35E8C229@taggart.lackof.org> (raw)

http://www.theregister.co.uk/2016/12/03/intel_puma_chipset_firmware_fix/

"Modems powered by Intel's Puma 6 chipset that suffer from bursts of
game-killing latency include the Arris Surfboard SB6190, the Hitron
CGNV4, and the Compal CH7465-LG, and Puma 6-based modems rebadged by
ISPs, such as Virgin Media's Superhub 3 and Comcast's top-end Xfinity
boxes. There are other brands, such as Linksys and Cisco, that use the
system-on-chip that may also be affected."

-- 
Matt Taggart
matt@lackof.org



             reply	other threads:[~2016-12-04  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04  8:25 Matt Taggart [this message]
2016-12-04  8:27 ` Jonathan Morton
2016-12-04 19:41   ` dpreed
2016-12-05 17:10     ` Stephen Hemminger
2016-12-06 11:51       ` Mikael Abrahamsson

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161204082535.35E8C229@taggart.lackof.org \
    --to=matt@lackof.org \
    --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