From: Dave Taht <dave.taht@gmail.com>
To: Richard Smith <richard@laptop.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] fiddling with wireless, batman-adv, etc
Date: Mon, 13 May 2013 17:57:28 -0700 [thread overview]
Message-ID: <CAA93jw7nig6oQYna8c1EgMQ3EYLo9AO5WhL3RKFXLC5Y9o8cmw@mail.gmail.com> (raw)
In-Reply-To: <CA+vq8rcb4bgnnmShN3hG+RQ5MPexQHtV-M1vYFvot=82baEhfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On Mon, May 13, 2013 at 5:47 PM, Richard Smith <richard@laptop.org> wrote:
> > I believe these results (which was from about that many machines and
> there
> > were some good data being presented and crunched) were using multiple
> > channels and diversity routing, which in the b.a.t.m.a.n world
> > is called "interface alternating"
> >
> > http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize
>
> Ok. I'll have to ask about it on the batman-adv list.
>
> > As I recall OLPC now has two radios?
>
> Yes. We added a Marvell 8787 option to the XO-4. The 8787 can do
> either 2.4Ghz or 5Ghz just not simultaneous.
Sorry man, I tend to view the dense mesh problem as unsolvable without
diversity routing and 2 or more channels available.
There's some upcoming work on power management that is seeking funding I
can send you a brief on, which will probably help the single channel case,
but....
> In theory you could use
> the 8787 card with an XO-1.75 but the mwifiex driver would need to be
> backported on to the 1.75 kernel or OLPC 1.75 specific patches ported
> to a newer kernel with mwifiex support. Both involve a good bit of
> effort.
>
> --
> Richard A. Smith
> One Laptop per Child
>
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 2100 bytes --]
next prev parent reply other threads:[~2013-05-14 0:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 18:55 Dave Taht
2013-05-14 0:15 ` Richard Smith
2013-05-14 0:29 ` Dave Taht
2013-05-14 0:47 ` Richard Smith
2013-05-14 0:57 ` Dave Taht [this message]
2013-05-14 1:03 ` Richard Smith
2013-05-14 7:12 ` Dave Taht
2013-05-14 16:39 ` Richard Smith
2013-05-14 0:54 ` Outback Dingo
2013-05-14 1:06 ` Richard Smith
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=CAA93jw7nig6oQYna8c1EgMQ3EYLo9AO5WhL3RKFXLC5Y9o8cmw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richard@laptop.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