From: GitHub <noreply@github.com>
To: cerowrt-commits@bufferbloat.net
Subject: [dtaht/cerofiles-3.3] bdadb5: mac80211 configuration changed in recent openwrt
Date: Thu, 05 Apr 2012 20:16:47 -0700 [thread overview]
Message-ID: <4f7e601f2b8f6_41ea3f8c7b45eaec802f7@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Branch: refs/heads/cerowrt-3.3.0
Home: https://github.com/dtaht/cerofiles-3.3
Commit: bdadb5304be0fe9a64314f2e4bdd75b094828784
https://github.com/dtaht/cerofiles-3.3/commit/bdadb5304be0fe9a64314f2e4bdd75b094828784
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-03-29 (Thu, 29 Mar 2012)
Changed paths:
M files/lib/wifi/mac80211.sh
Log Message:
-----------
mac80211 configuration changed in recent openwrt
this updates the somewhat special treatment cerowrt gives devices
into the new version of the file.
* Default to ht40+ mode for 5ghz
* survive the device renaming scheme
* Use 5ghz specific ssids to encourage people to use 5ghz
I wish openwrt would adopt 2 of these....
Commit: d481a612ed82179d6f4d1ed0fc00f087572e6830
https://github.com/dtaht/cerofiles-3.3/commit/d481a612ed82179d6f4d1ed0fc00f087572e6830
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-02 (Mon, 02 Apr 2012)
Changed paths:
M files/etc/init.d/boot
Log Message:
-----------
BQL makes tuning down the tx ring no longer needed!
With the tx ring turned down to 4 we'd got back control on big packets.
Finally.
But we compromised ack performance when you could only have 4 packets
outstanding.
With BQL, we get the best of both
worlds, and turning down the tx ring hurts rather than helps.
Let BQL have this job.
Commit: a74b4df58147ab987dbd8f607cae64adf3c0d23f
https://github.com/dtaht/cerofiles-3.3/commit/a74b4df58147ab987dbd8f607cae64adf3c0d23f
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-05 (Thu, 05 Apr 2012)
Changed paths:
M config-wndr3700v2
M files/etc/opkg.conf
Log Message:
-----------
cerowrt-3.3.1-4
Compare: https://github.com/dtaht/cerofiles-3.3/compare/ea8932e...a74b4df
next reply other threads:[~2012-04-06 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 3:16 GitHub [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-06 3:02 GitHub
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f7e601f2b8f6_41ea3f8c7b45eaec802f7@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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