Thanks Bob for your support. The following lines from https://github.com/cozybit/open80211s/wiki/HOWTO made to think of H/W independent.
open80211s <http://open80211s.org/>, is an open-source implementation of the ratified IEEE 802.11s wireless mesh standard. The goal for the open80211s project is to run on any commodity hardware supported by the Linux kernel. More specifically, open80211s was born to fulfill the following goals: - To create the first open implementation of 802.11s - To let the world use, understand, and contribute to 802.11s and open80211s - To consolidate the numerous non-interoperable mesh protocols into one that is based on a standard specification Cozybit has used open80211s on multiple devices, ranging from personal laptops, embedded linux hardware to Android based devices. I Will check with TI for the same. Regards, Rudresh On 11 January 2015 at 20:03, Bob Copeland <[email protected]> wrote: > On Sat, Jan 10, 2015 at 09:16:55PM +0530, Rudresh NB via Devel wrote: > > Hi Marco. > > Thanks for the answer. I agree that listed #3 patch is for > > ath9k specific. For wl1271 I need to see the datasheet and make > > corresponding change in the driver for powersave. But for basic mesh > > support you say that some patch is required? with the default kernel that > > support Mesh is not enough? > > Hi Rudresh, > > Mobile chipsets like TI wl12xx typically implement some of the MAC in > firmware for powersave reasons (increasingly, this is true of desktop > chipsets as well). Thus, it's not a forgone conclusion that mesh will > work with some specific mac80211 device even though 11s is implemented > in the MAC. > > A mac80211 driver needs to do at least the following: > > - include mesh IEs in beacons > - turn off bssid filtering (FIF_OTHER_BSS) > - somehow report TX status or link quality back to the kernel > - report neighbor beacons back to the kernel > - for encrypted mesh: handle a large number of keys > (at least 2 per STA plus one more) > - for synchronization: adjust TSF, put timestamps on RXed beacons > - for power saving: update TIM elements on every beacon, and have > hardware timers to wake up for neighbor beacons > - for Mesh AP (on one device): support simultaneous AP and Mesh vifs > > Some devices may not support some or all of the above due to firmware > limitations. > > Today, none of the TI chips support mesh upstream as far as I can tell. > I believe Thomas Pedersen worked on it once upon a time but I do not > know the outcome of that attempt. > > -- > Bob Copeland %% http://bobcopeland.com/ >
_______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
