From: Nick Feamster <feamster@cc.gatech.edu>
To: d@taht.net (Dave Täht)
Cc: bismark-users <bismark-users@lists.bufferbloat.net>
Subject: Re: [Bismark-users] Status update
Date: Tue, 15 Mar 2011 13:28:33 -0400 [thread overview]
Message-ID: <1547DA4E-BAF3-498A-B0E4-60DB6B7ABEC6@cc.gatech.edu> (raw)
In-Reply-To: <87wrk0jnyn.fsf@cruithne.co.teklibre.org>
Hi Dave,
One more thing on your action items:
I plan to post the job posting to the bloat list later today.
-Nick
On Mar 15, 2011, at 1:25 PM, Dave Täht wrote:
>
> I put a more complete build (more packages) up at www.co.teklibre.org/openwrt/
>
> Regrettably unless our topmost git commit is in sync it won't work.
>
> commit a42e50cceaf2cc8997cfb6870ae1ab70f3f1abe1 is my top.
>
> So we will need to get on the same page sometime soon.
>
> There are some useful patches worth cherry picking for this device from
> the debloat-testing tree, notably the ath9k one (I think I can safely
> revert half of it though, at this point) and eBDP.
>
> One nice thing about git head of openwrt, it has support for txqueuelen
> in /etc/config/network
>
> Now, if you need help getting the router working, I seem to remember
> that the version I had did not load the ath9k drivers by default, so you
> needed to install those via opkg.
>
> "Poole, Brian" <bpoole@cc.gatech.edu> writes:
>
>> Hey Dave,
>>
>> I'm helping out on the project as well and can provide a bit of a
>> status update. I've pulled down the build tree on a shared GT server
>> and completed a test build (not adding everything we want yet, just
>> verifying it works.) That has completed successfully but we haven't
>> actually tried loading it up yet.
>>
>> I purchased a wndr3700 locally and hope to try loading it up later
>> today. I know Srikanth already had one and was just waiting for the
>> build to be completed to try it out (Srikanth, its in
>> ~bismark/openwrt/wndr3700/bin/ar71xx :-)
>>
>> Brian
>> ________________________________________
>> From: bismark-users-bounces@lists.bufferbloat.net [bismark-users-bounces@lists.bufferbloat.net] on behalf of Dave Täht [d@taht.net]
>> Sent: Tuesday, March 15, 2011 12:20 PM
>> To: bismark-users
>> Subject: [Bismark-users] Status update
>>
>> I'm busy getting the new server up this afternoon. I intend first to get
>> builds going for various OSes - ubuntu 10.10, and whatever else is
>> needed, then migrate the shipka (web) server over after the box proves
>> stable.
>>
>> Open questions:
>>
>> 1) To what extent do you want this project to be public, or invitation
>> only?
>>
>> 2) Get a wndr3700 yet?
>>
>> 3) Get a build done?
>>
>> --
>> Dave Taht
>> http://nex-6.taht.net
>> _______________________________________________
>> Bismark-users mailing list
>> Bismark-users@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bismark-users
>
> --
> Dave Taht
> http://nex-6.taht.net
> _______________________________________________
> Bismark-users mailing list
> Bismark-users@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-users
next prev parent reply other threads:[~2011-03-15 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:20 Dave Täht
2011-03-15 17:00 ` Poole, Brian
2011-03-15 17:25 ` Dave Täht
2011-03-15 17:28 ` Nick Feamster [this message]
2011-03-15 17:30 ` Dave Täht
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=1547DA4E-BAF3-498A-B0E4-60DB6B7ABEC6@cc.gatech.edu \
--to=feamster@cc.gatech.edu \
--cc=bismark-users@lists.bufferbloat.net \
--cc=d@taht.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