Return-path: Received: from static-72-92-88-10.phlapa.fios.verizon.net ([72.92.88.10]:35251 "EHLO smtp.roinet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753743AbZKQVxJ (ORCPT ); Tue, 17 Nov 2009 16:53:09 -0500 Message-ID: <4B031B48.1090105@roinet.com> Date: Tue, 17 Nov 2009 16:53:12 -0500 From: David Acker MIME-Version: 1.0 To: "Luis R. Rodriguez" CC: Andrey Yurovsky , Michael Renzmann , madwifi-devel@lists.sourceforge.net, madwifi-users@lists.sourceforge.net, linux-wireless Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why? References: <2205.95.222.251.107.1258282369.squirrel@webmail.otaku42.de> <43e72e890911161701p61d0db5ag25a1459f900b3ab7@mail.gmail.com> <4B02DFF4.1060509@roinet.com> <45e8e6c40911171257m7c687380k6e6e2677fd11f851@mail.gmail.com> <43e72e890911171337p4b0d97fcp844266137bb51b56@mail.gmail.com> <4B03193E.2080304@roinet.com> <43e72e890911171345q2dc59d66g6ac2a9eec04c577c@mail.gmail.com> In-Reply-To: <43e72e890911171345q2dc59d66g6ac2a9eec04c577c@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: Luis R. Rodriguez wrote: > On Tue, Nov 17, 2009 at 1:44 PM, David Acker wrote: >> It is a non-802.11s protocol that predates 802.11s development by quite >> awhile. It runs over WDS links. In theory it could run over anything that >> supports dynamic creation and destruction of WDS links. > > So its a some sort of MadWifi-only hack? Not at all. The algorithm runs in user space and has run over other radio/driver combinations and even in networks of mixed radio types. I don't see a problem with running it over ath5k. Basic functionality should work fine. The problem with switching to ath5k would be the loss of performance related features (compression, fast frames, turbo), and some required features (half/quarter rates are required for some channels on some radios). Also, I don't know if ath5k will work on products based on Atheros WiSOCs like Ubiquiti's PicoStation and Bullet. A lesser issue (more of a pain for me than an ath5k issue) is that I have some platforms that use an older kernel and moving up to a newer kernel will have to be done without hardware vendor support. -ack