> > > Do they represent change of directions during the development of rc.c > code? > > I don't think I understand your question. > > I mean, you develop the basic stuff to implement an algorithm and then end up not using those parameters.
> Well I stay away from it because IMHO its pretty convoluted. But I should > note > that it was designed to be simple but more importantly to run really well > on low end MIPS APs. It is convoluted primarily because it contains all these lines of code corresponding to RSSI measurement that are not being used. Also, these parts of code would be causing unnecessary slowing of the MIPS APs that you have in mind. But all these arguments are futile if someone can point out that it is crucial stuff and may be used for future development. I must mention that I am using compat-wireless-2.31-rc4 code, maybe there has been more development on this stuff after that? > Another reason I stay away is I believe minstrel can > eventually be made MCS aware and it may work better. But someone has to > work on that first. > > I can potentially hack minstrel and tailor it for ath9k but I really need to be sure if that would be useful to the project that I am working on right now, i.e. my Masters thesis. :)
_______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
