From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Jonathan Morton" <chromatix99@gmail.com>
Cc: "Mikael Abrahamsson" <swmike@swm.pp.se>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how far behind is the embedded router world, still?
Date: Thu, 26 Jul 2018 12:48:38 -0400 (EDT) [thread overview]
Message-ID: <1532623718.389715294@apps.rackspace.com> (raw)
In-Reply-To: <F6AC84BA-3447-4229-9E91-6408146C1822@gmail.com>
How would one get Linux Foundation to raise money to sponsor a router software initiative?
I can see that all the current network product OEMs might mass up to kill it or make it fail. Kind of like coreboot vs. UEFI.
But maybe Facebook or Amazon or Google - dedicated white-box fan companies - might do it. Or maybe there's a Chinese funding source.
-----Original Message-----
From: "Jonathan Morton" <chromatix99@gmail.com>
Sent: Thursday, July 26, 2018 10:13am
To: "Mikael Abrahamsson" <swmike@swm.pp.se>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how fHow wouar behind is the embedded router world, still?
> On 26 Jul, 2018, at 11:53 am, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> 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.
This in itself sounds like a colossal waste of developer man-hours. Which really just serves to underline how clueless CPE vendors are - about their core business, no less.
They obviously have a lot more resources than we do. What could *we* do with that level of funding and organisation? Take six months, and put out a router that *doesn't* suck for a change!
- Jonathan Morton
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2018-07-26 16:48 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
2018-07-26 14:13 ` Jonathan Morton
2018-07-26 16:48 ` dpreed [this message]
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=1532623718.389715294@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=swmike@swm.pp.se \
/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