From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] cerowrt-next and cerofiles-next trees established on github using kernel 3.6.9
Date: Thu, 6 Dec 2012 11:49:52 +0100 [thread overview]
Message-ID: <CAA93jw6jKoDC5QD805TvFq7Fq88wkd7+GL8eNnaJaUnR1HyJkw@mail.gmail.com> (raw)
The new repos are at:
https://github.com/dtaht/cerowrt-next/
https://github.com/dtaht/cerofiles-next/
While I have a mostly working build now of nearly all of cerowrt on
Linux 3.6.9, there is still work to be done on getting wifi to work
again, in particular. I doubt I will get it sorted today.
In the meantime...
There is an enormous and growing overall tasks list. and some draft
release notes here:
https://github.com/dtaht/cerowrt-next/blob/master/tasks.org
If you see anything on that you want to leap in and do (or add!) -
just do it - or discuss it on this list. :)
My thanks to stephen walker for knocking out a whole lot of package
upgrades and related patches.
As well as to Robert Bradley for the ipv6 unaligned hacks (which
worked FIRST TIME)
And to ketan for looking into TCP fast open...
Paolo Valente for QFQ+ and BFQ support
And the whole openwrt team for pushing ahead so fast on openwrt
"Barrier breaker", now that AA is stable.
I'm totally aware there are dlna and upnp fixes in the pipeline, but
before that, is getting the darn thing to boot right... and finding
some way to test those two protocols....
There are no doubt going to be tons of new bugs introduced by this 2+
month interval between releases, and the 3 kernel version leap
forward, so DO NOT EVEN THINK about installing the upcoming first
3.6.9 build on your default gw....
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2012-12-06 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6jKoDC5QD805TvFq7Fq88wkd7+GL8eNnaJaUnR1HyJkw@mail.gmail.com \
--to=dave.taht@gmail.com \
--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