Ok thanks for the tip. So I will wait until the wireless-testing 2.6.27-rc1 :-)
2008/7/9 Pavel Roskin <[EMAIL PROTECTED]>: > On Tue, 2008-07-08 at 16:13 +0200, Frédéric Weisbecker wrote: > > Ok thank you for your answer. > > In the purpose to compare ath5k traces with madwifi traces, I'm > > writing a personal patch based on Debugfs to log the IO on the card > > since MmIoTrace doesn't work for 2.6.26. > > If someone is interested I will share it. > > The new mmiotrace is scheduled for Linux 2.6.27. It's already present > in several kernel trees, including linux-next. It will use debugfs. I > suggest that you look at the new mmiotrace code. It will allow > debugging madwifi or any driver without changes, this making a separate > madwifi-trace branch unnecessary. I suggest that you look at it. > > I'm afraid extracting the new mmiotrace from linux-next would be too > much work, but it shouldn't take long before mmiotrace comes to the > wireless-testing branch. I think we are 1 week from 2.6.26, 3 weeks > from 2.6.27-rc1 and 4 weeks from wireless-testing based on 2.6.27-rc1. > > -- > Regards, > Pavel Roskin >
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
