From: Michael Renzmann <madwifi@no...> - 2005-12-15 09:44:17
We have several open tickets that are waiting for confirmation in one or
the other way.
Reports of a problem related to X-Scale cross compilation, where the
compiler complains about a conflict between "-mcpu=xscale" and "-march="
A patch has been provided which solves the problem for the reporter.
Can someone else please try this patch? Are there any unwanted side
effects that might strike us?
Reports about a problem in madwifi-old related to athXraw interfaces. It
mentions a chain of commands which results in an oops.
Can someone else please try to reproduce the problem with madwifi-ng?
In addition, I think the problem might be that ath0raw is not brought
down ("ifconfig ath0raw down") before it is destroyed ("sysctl -w
dev.ath0.rawdev=0"). Can someone please verify if bringing down ath0raw
before destroying it solves the problem?
Describes a race condition in ath_rate_sample and provides a "ugly
work-around". Evaluation of the patch is needed. Is it a proper
solution, or would there be a better way to get rid of the problem? Does
the problem persist for the other rate modules as well? If so, we should
find a general way to solve it.
Reports that background scanning can be the cause for link
instabilities. Anyone able to approve this? Any suggestions on how this
could be fixed?
Get latest updates about Open Source Projects, Conferences and News.