On 12/14/2016 02:46 PM, Valo, Kalle wrote: > Erik Stromdahl <erik.stromdahl@xxxxxxxxx> writes: > >> I have made a few updates since I submitted the original RFC and created >> a repo on github: >> >> https://github.com/erstrom/linux-ath >> >> I have a bunch of branches that are all based on the tags on the ath master. >> >> As of this moment the latest version is: >> >> ath-201612131156-ath10k-sdio >> >> This branch contains the original RFC patches plus some addons/fixes. > > Good, this makes it easier to follow the development. So what's the > current status with this branch? What works and what doesn't? > Well, everything in there has been tested (limited though, as you yourself experienced), but it is not complete. I still have some other patches that need some more refurbishing before I can push them. I will push those patches that I consider "good enough" for publish to this repo. Most likely I will rewrite/squash etc. some of it before submitting a new RFC series. So, there are still some additional stuff that needs to be added. In my case I have a series of patches related to OCB (Outside the Context of a BSS) mode of operation (since the chipset I am using is intended for this purpose). These patches are still not complete. Other SDIO 11ac chipsets might just need an item in the struct ath10k_hw_params array together with some firmware files. > Especially I'm interested about the state of the HTT high latency > support. How much work is to add that? It would also make it easier to > add USB support to ath10k. > I actually have some patches regarding this, but they have not been tested at all since I have not yet managed to fully configure my SDIO chip properly so far. I must finish the OCB code I mentioned earlier and fix another really annoying issue with a missing HTT version response (sometimes target won't respond to the HTT version request). Then, hopefully, I can make some TX and RX tests. I think the HTT TX part is fairly straight forward. But the RX part is a little bit more tricky since I am not really sure about how to interface mac80211 in the RX path. My work flow goes like this: As soon as there is a new tag on the ath.git master, I rebase my stuff on top of it and push a new branch to my repo. I will continuously push updates to the latest branch (the branch based on the latest ath tag). Older branches will not be maintained. /Erik
