public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Line of Nodes
Date: Wed, 12 Mar 2014 15:25:07 +0100	[thread overview]
Message-ID: <20140312142507.GO1629@pengutronix.de> (raw)
In-Reply-To: <201403121451.09760.sw@simonwunderlich.de>

Hi Simon,

On Wed, Mar 12, 2014 at 02:51:09PM +0100, Simon Wunderlich wrote:
> Mhm, I'd generally recommend the Matthew Gast books on 802.11, these
> are very good.

Thanks, sounds good! Is "802.11 Wireless Networks: The Definitive Guide"
recent enough? Seems to be from 2005.

> The throughput limitation I'm talking about is a mesh-network specific problem 
> when you use single radios only: as a wifi radio can only transmit or receive 
> at the same time, the throughput will be cut to 50% with the first hop, and 
> will decrease furhter with more hops. I don't know if there are books about 
> such effects, but there are certainly papers ...

Will search.

Would having a 2nd transmitter help?

> > Can you give me a hint which feature I need to search for in the kernel
> > drivers?
> 
> ath9k supports that for example. you can set the txpower using "iw wlan0 set 
> txpower 1500" for example to set to 15dBm output pwoer

Thanks, txpower is a good hint.

> > As the stations will be built from scratch (SoC+RAM+Flash+Wifi-Chipset),
> > we can chose the right chipsets, as long as it's possible to buy them
> > somewhere.
> > 
> 
> I'd definitely recommend to buy WiFi modules (e.g. pci-e) or off-the-shelf 
> boards with WiFi SoCs on it. If you don't have experience in building WiFi 
> routers, you might have a lot of fun otherwise. :)

The issue is that the stations need to be very low power, so I'd like to
leave everything out which draws power but isn't absolutely needed. The
HF part should be solvable, that's something the hardware developers
have experience with. I'm aiming for a low power ARM cpu, which
basically rules out anything that needs PCIe and leaves us with SDIO or
USB for the connection of the transmitters.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2014-03-12 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 21:25 [B.A.T.M.A.N.] Line of Nodes Robert Schwebel
2014-03-12 10:36 ` Simon Wunderlich
2014-03-12 12:53   ` Robert Schwebel
2014-03-12 13:51     ` Simon Wunderlich
2014-03-12 14:25       ` Robert Schwebel [this message]
2014-03-12 14:54         ` Andrew Lunn
2014-03-12 18:20           ` Robert Schwebel
2014-03-31 11:06             ` Bruno Antunes
2014-03-31 18:14               ` Robert Schwebel

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=20140312142507.GO1629@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sw@simonwunderlich.de \
    /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