Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how far behind is the embedded router world, still?
Date: Thu, 26 Jul 2018 10:53:27 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1807261047560.14354@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw6TetZ9JSfw0ZFDMm5nxixV4Y6pycCqMKYa2uNseegSzg@mail.gmail.com>

On Wed, 25 Jul 2018, Dave Taht wrote:

> There are still a few companies alive in this space (openrg being one 
> that I know nothing about), but...

There is no single answer to this. Lots of the home routing SoC space is 
now converging on 4.4, but BCM decided to go for 4.1. They came from 3.2, 
3.4 and perhaps 3.10. When I talk to staff at SoC vendors, they seem to 
live in a world where you take a linux kernel that's announced as LTS (in 
the best of worlds), work on that for 1-2 years during which you release 
an SDK, which then the device manufacturers will take and start putting 
their solutions on, which takes another 1-2 years before it reaches 
customers. So already there is significant latency.

This doesn't mean there are not devices out there today, newly installed, 
that have really ancient kernels (as you have discovered). This is 
especially true for cheaper and simpler devices that are very cost 
optimized.

There is movement in the right direction, but revving kernels on older 
platforms is still hard, as in all of IoT space, due to lack of revenue 
from older platforms. Main model is still to sell a device and then there 
is no further income, so no money to continously develop the device.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  parent reply	other threads:[~2018-07-26  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 18:50 Dave Taht
2018-07-25 19:14 ` valdis.kletnieks
2018-07-25 19:49   ` dpreed
2018-07-25 20:00     ` Dave Taht
2018-07-25 20:17 ` Jim Gettys
2018-07-26  8:53 ` Mikael Abrahamsson [this message]
2018-07-26 14:13   ` Jonathan Morton
2018-07-26 16:48     ` dpreed
2018-07-26 20:15       ` Dave Taht
2018-07-26 20:34         ` Joel Wirāmu Pauling
2018-07-27  9:31       ` Mikael Abrahamsson
2018-07-26 13:13 [Cerowrt-devel] So how far behind is the embedded router world,still? dpreed
2018-07-26 13:56 ` [Cerowrt-devel] So how far behind is the embedded router world, still? Mikael Abrahamsson
2018-07-26 16:45 ` valdis.kletnieks
2018-07-27 12:18 dpreed

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=alpine.DEB.2.20.1807261047560.14354@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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