Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net, gregkh@linuxfoundation.org,
	 Alistair Woodman <awoodman@isc.org>
Subject: [Cerowrt-devel] closer ties to ltsi?
Date: Fri, 2 Mar 2012 02:33:25 -0800	[thread overview]
Message-ID: <CAA93jw7Hm+KNRUEAinod2Djs2upwN_yhWCDk7wiGF3HH-qCVhA@mail.gmail.com> (raw)

Dear Greg:

What ltsi is up to:

http://ltsi.linuxfoundation.org/what-is-ltsi

is orthogonal to what we are up to, in that they are trying to produce
a usable, stable tree that can be used in a lot of CE devices, and we
are trying to push the bleeding edge in finding, fixing, and testing
things that would be good to have deployed in a lot of CE devices at
least on the bufferbloat, security, and network - especially ipv6 -
fronts.

How to faster get stuff from "R&D" to deployment is always on my mind.
I'm very happy to be successfully tracking the 3.3 process 'live' at
the moment with cerowrt. I imagine the next 'stable'
kernel chosen will be 3.3 or 3.4 based.

How to  make bloatlab #1 more effective and useful is currently on my
mind, as I'm plan to rebuild it when I get back to california next
week. While there's a great deal of gear under test, we could do
better, and certainly having some automation and a good test suite is
something I wanted to have in operation by now, and don't, as BQL +
SFQRED etc really need some serious exercising.

ltsi seems to have a lot of hw vendor support, we have a growing
amount of ISP interest...

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

             reply	other threads:[~2012-03-02 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 10:33 Dave Taht [this message]
2012-03-02 15:43 ` Greg KH
2012-03-02 16:13   ` Jim Gettys

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=CAA93jw7Hm+KNRUEAinod2Djs2upwN_yhWCDk7wiGF3HH-qCVhA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=awoodman@isc.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=gregkh@linuxfoundation.org \
    /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