2010/5/8 Felix Fietkau <[email protected]>:
> I think what we're doing now is working well enough. The reason why I picked
> the bleeding edge snapshot of compat-wireless for the stable branch of
> OpenWrt is that it fixes a large number of critical bugs. However, none of
> the bugs that I was working on fixing in ath9k were regressions.
> I think ath9k (and the linux wireless subsystem in general) has had very few
> regressions over time, even in the wireless-testing tree, so I see no point
> in adding more stable branching to the mix.

Good point, they are not often regressions.

> The compat-wireless snapshot that is in OpenWrt right now has been tested on
> quite a few APs in production use, and while it's not perfect, it's in
> better shape than anything we had before.
> Client connections are no longer dropping all the time, the Rx and Tx path
> seems to no longer get stuck, descriptor corruption seems to be gone
> completely - these were all issues that were present in ath9k from the
> beginning, but were fixed recently.

Agree. I definitely don't want to belittle the progress that is being
made. I see some really good patches going in, quite a few of them
signed off by you. Thanx for that.

> The reason these were not fixed earlier is that other bugs were in the way,
> but that does not imply that the development process is ineffective for
> stabilization.

I guess you are right here too: my problem is not really with the
regressions, and branching won't fix the preexisting bugs. I think
it's mostly psychology. When I'm about to update to a bleeding edge
snapshot that is only a few days old I get nervous. I have hundreds of
people using those APs and they have every chipset imaginable on their
side. It feels like a recipe for disaster to update from a patched
development snapshot a few months old to another one that is only days
old.

Any guess when I will be able to run ath9k "as is" from a mainline
kernel along with a stable hostapd release?

/Björn
_______________________________________________
ath9k-devel mailing list
[email protected]
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to