> From: devel-requ...@lists.open80211s.org > Subject: Devel Digest, Vol 46, Issue 1 > To: devel@lists.open80211s.org > Date: Wed, 13 Jul 2011 12:00:01 -0400 > > Send Devel mailing list submissions to > devel@lists.open80211s.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://open80211s.com/mailman/listinfo/devel > or, via email, send a message with subject or body 'help' to > devel-requ...@lists.open80211s.org > > You can reach the person managing the list at > devel-ow...@lists.open80211s.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Devel digest..." > > > Today's Topics: > > 1. Re: Problem on Release0.4.0 (V-SHY HO) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Jul 2011 09:22:13 +0000 > From: V-SHY HO <vshy...@hotmail.com> > Subject: Re: Problem on Release0.4.0 > To: <devel@lists.open80211s.org> > Message-ID: <bay155-w5646035245e8db29402501e2...@phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > > Hi Javier, > > Sorry for take long time to try make change at ath9k because still work hard > to study mac80211 source code. > By refer to your patch for ath9k_htc, > after enabled IEEE80211_HW_SUPPORTS_PER_STA_GTK flags and nohwcrypt > parameter at ath9k, > I can have success ping between secured mesh with cards D-Link DWA-547 ( > Atheros AR9280 Rev:2). > > diff -Nurp a/drivers/net/wireless/ath/ath9k/init.c > b/drivers/net/wireless/ath/ath9k/init.c > --- a/drivers/net/wireless/ath/ath9k/init.c 2011-06-15 13:29:59.000000000 > +0800 > +++ b/drivers/net/wireless/ath/ath9k/init.c 2011-07-14 13:52:17.000000000 > +0800 > @@ -685,6 +685,7 @@ void ath9k_set_hw_capab(struct ath_softc > IEEE80211_HW_SUPPORTS_PS | > IEEE80211_HW_PS_NULLFUNC_STACK | > IEEE80211_HW_SPECTRUM_MGMT | > + IEEE80211_HW_SUPPORTS_PER_STA_GTK | > IEEE80211_HW_REPORTS_TX_ACK_STATUS; > > if (sc->sc_ah->caps.hw_caps & ATH9K_HW_CAP_HT) > > cheers, > V-SHY HO > > > > Date: Thu, 16 Jun 2011 12:44:17 -0700 > > From: Javier Cardona <jav...@cozybit.com> > > > > Hi V-SHY, > > > > On Thu, Jun 16, 2011 at 1:03 AM, V-SHY HO <vshy...@hotmail.com> wrote: > > > 1)Refer to > > > http://www.spinics.net/lists/linux-wireless/msg60623.html > > > 05 Dec 2010, Johannes Berg, Re: RSN IBSS and GTK configuration > > > > > > "That seems about right -- NL80211_KEY_TYPE or NL80211_ATTR_KEY_TYPE > > > should be used I guess. Did you change your driver (presumably ath9k) to > > > set WIPHY_FLAG_IBSS_RSN? That's required -- I do expect drivers to have > > > issues with this in many cases, at least until they are changed to not > > > attempt to program multiple GTKs into hardware for IBSS." > > > > > > Recently, you uploaded new patch for ath9k_htc which enables > > > IEEE80211_HW_SUPPORTS_PER_STA_GTK > > > IEEE80211_HW_MFP_CAPABLE > > > WIPHY_FLAG_IBSS_RSN > > > > > > Do we have any hope to enable same parameters to make ath9k have success > > > ping? > > > > Yes. We don't have the right hardware to try it but I would expect > > that the exact changes on ath9k would do the trick. > > Can you try it on your hardware? > > > > > 2) I success determine it with enable napi events on tracing. > > > Now I am learning > > > how to use ftrace to trace function activity and > > > how to make use of trace_printk to have log on new specified function's > > > log > > > message. > > > Can you share some experience to trace mesh related activity? > > > > I'm not sure what activity are you trying to trace. Can you be more > > specific? > > > > > 3) About examining frame with the aid of monitor interface, > > > beside of Wireshark, any others tool make use of monitor interface? > > > What I know about wireshark is , it does not provide frame capture at > > > inner > > > process within PC. > > > May I know your method to examine the frame content which passed from > > > ath9k > > > to mac80211? > > > > The monitor interface should show you just that, the raw 802.11 frame > > before it is processed by mac80211. If you are working on an embedded > > system it's easier to capture the monitor interface traffic with > > tcpdump -w <file> and analyze the file with wireshark on your > > development host. > > > > Cheers, > > > > Javier > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://open80211s.com/pipermail/devel/attachments/20110713/2e4f9d37/attachment-0001.html > > > ------------------------------ > > _______________________________________________ > Devel mailing list > Devel@lists.open80211s.org > http://open80211s.com/mailman/listinfo/devel > > > End of Devel Digest, Vol 46, Issue 1 > ************************************
_______________________________________________ Devel mailing list Devel@lists.open80211s.org http://open80211s.com/mailman/listinfo/devel
