Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Joel Wirāmu Pauling" <joel@aenertia.net>
Cc: "Dave Taht" <dave.taht@gmail.com>,
	"Jonathan Morton" <chromatix99@gmail.com>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how far behind is the embedded router world, still?
Date: Fri, 27 Jul 2018 08:18:08 -0400 (EDT)	[thread overview]
Message-ID: <1532693888.89877811@apps.rackspace.com> (raw)

In some ways, the quickness is good, beats the old days of ATT monopoly never innovating except over 10 year incremental cycles.

But Linux isn't capable of quick innovation. It's too overcomplicated. Too many parts barely fit together, or don't. Huge config files encoding same info in inconsistent ways. Poor cross compilation architecture, if there is one at all. Days long build cycles.

Then throw in UEFI which has to be built on Windows to get it right.

Not a system that can chase innovation of the small kind. Hardware is now like software in how varied it can be. But software is no longer about flexibility of abstraction. Every Linux is a Time Sharing System.


-----Original Message-----
From: "Joel Wirāmu Pauling" <joel@aenertia.net>
Sent: Thu, Jul 26, 2018 at 4:34 pm
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Dave Taht" <dave.taht@gmail.com>, "Jonathan Morton" <chromatix99@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how far behind is the embedded router world, still?

Just a note - a lot of this mess is due to China's rapid dev cycles and
race to the bottom on cost vs supply.

Generally a fab house who is in turn contracted by an OEM in China will
have 1 maybe 2 engineers who will do the initial low level C bits required
for a product/board. They get it working on whatever build environment they
have at hand and chuck it over the fence to product unit who ship it. Then
moving onto the next contract never to be seen from again.


-Joel


On 27 July 2018 at 08:15, Dave Taht  wrote:

> On Thu, Jul 26, 2018 at 9:48 AM dpreed@deepplum.com 
> wrote:
> >
> > How would one get Linux Foundation to raise money to sponsor a router
> software initiative?
>
> We tried. Personally, having bled out mentally and financially more
> than once, I am not up to trying again. They don't return our calls
> anymore.
>
> > 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.
>
> Well, try to sort through
> https://www.forbes.com/sites/forbesnycouncil/2018/07/26/
> why-you-should-start-looking-at-googles-flutter-and-
> fuchsia-now/#795943a6a309
>
> As for china, sure, that would be great. Europe, sure. I think china
> has a huge incentive to get into making better firmware in
> collaboration with europe. As for america...
>
>
> > -----Original Message-----
> > From: "Jonathan Morton" 
> > Sent: Thursday, July 26, 2018 10:13am
> > To: "Mikael Abrahamsson" 
> > 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 
> 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
> >
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



             reply	other threads:[~2018-07-27 12:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 12:18 dpreed [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-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
2018-07-26 20:15       ` Dave Taht
2018-07-26 20:34         ` Joel Wirāmu Pauling
2018-07-27  9:31       ` 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=1532693888.89877811@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=joel@aenertia.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