I didn't use git because I wanted to use the version that openwrt trunk was using, and the git at kernel.org is still down.
Yes I do have HT20 mode set, which was the default for openwrt config, so I left it at default. I also tried it in HT40 mode with same results. Its possible that the HT code may have been in the version of compat-wireless that openwrt trunk is using, and thus got patched into the o11s version during my procedure below. I can check that later when I get home, as I was building that in the evening yesterday. Regards, David Fulgham On Fri, Oct 14, 2011 at 10:30 AM, Javier Cardona <jav...@cozybit.com> wrote: > Hi David, > > > On Thu, Oct 13, 2011 at 10:22 PM, David Fulgham > <david.a.fulg...@gmail.com> wrote: > > Ok, so did some research,etc. was having a heck of a time trying to get > the r28079 and o11s patch to work. So I wanted to use the latest openwrt > trunk, however the compat-wireless-o11s... has too many differences and > won't compile as is with the latest trunk. So I wanted to upgrade the o11s > version to the latest openwrt changes. > > let me know if my procedure is the way this should be done. > > 1) I extracted the compat-wireless-o11s.... to a folder A > > 2) downloaded and extracted the compat-wireless-2011-10-11 that is > currently being compiled as part of the openwrt trunk. and extracted to > Folder B > > 3) used diff on the Folders A and B to create a patch file. > > 4) applied the patch file to the o11s folder A > > That's one way to do it but it's probably better to work from git > trees instead of tarballs. This is somewhat documented here: > > http://www.o11s.org/trac/wiki/CompatWirelessBuilding > > > 5) re-tar-bzip2'd Folder A after changing the folder name to match what > is expected by openwrt and copied it into the /trunk/dl folder for openwrt > MAKE to use. > > 6) make V=99 ... and fixed up a couple of openwrt's patches that where > already applied in the o11s-patched version. > > 7) repeat 6 until it finally compiled (didn't take much to get it to go) > > Right. > > > I uploaded the firmware to a device and everything seems to be working > ok... Except I'm getting the following in my dmesg: > > ------------[ cut here ]------------ > > WARNING: at > /home/user/openwrt/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2011-10-05/drivers/net/wireless/ath/ath9k/xmit.c:1928 > 0x81aeb464() > > Modules linked in: ohci_hcd nf_nat_irc nf_conntrack_irc nf_nat_ftp > nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_conntrack xt_NOTRACK > iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd > pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac > xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables > ppp_async ppp_generic slhc ath9k ath9k_common ath9k_hw ath mac80211 usbcore > nls_base crc_ccitt cfg80211 compat arc4 aes_generic crypto_algapi leds_gpio > button_hotplug gpio_keys_polled input_polldev input_core > > Congratulations! We have encountered the same problem :) > We're working on this problem right now. > BTW, we were only seeing this when HT is enabled. Is that your case? > > > > The line in xmit.c relates to the following if statement: > > if ((sc->sc_flags & SC_OP_TXAGGR) && txctl->an && > > ieee80211_is_data_qos(hdr->frame_control)) { > > tid = ath_get_tid(txctl->an, skb); > > WARN_ON(tid->ac->txq != txq); > > } > > Yep, and that is only accessible when aggregation is enabled. > > > Everything is stable, but I don't seem to be getting HT modes. > > Does the version of compat-wireless on the wiki have the HT and > Aggregation patches? > > I thought it did not, but your warning should not happen if it didn't. > > We'll make a new release as soon as we complete HT support. Cross > fingers that we can solve this soon. > > Cheers, > > Javier > > >
_______________________________________________ Devel mailing list Devel@lists.open80211s.org http://open80211s.com/mailman/listinfo/devel
