On 11/16/2010 10:55 AM, James Womack wrote: > On 16/11/10 15:00, Larry Finger wrote: >> On 11/16/2010 08:46 AM, James Womack wrote: >> >>> This should be sufficient, hopefully! >> >> Perfect. >> >> Larry > > Good. Thanks for fixing this issue. Do you have any idea when we could > expect to see this fix incorporated into a mainstream kernel? The fix to change the panic into a simple warning has been pushed upstream. If GregKH, the staging maintainer, thinks it can go into 2.6.37, then the backporting to stable will happen fairly quickly. If he decides it is too invasive (not likely), then the patch will wait for ~2 months for 2.6.38. Once in mainline, there will be some delay as the patch for 2.6.37 does not apply to your kernel (2.6.32 as I recall), thus I will have to supply a revised version. Once it is in 2.6.32.Y, then your disto will have to pick up the changes and create an updated kernel. The wheels of change turn slowly - kernel stability is extremely important. My estimate would be 6 weeks at a minimum. Note that I still do not have a real fix for the warning. That could take a long time to find, particularly as I cannot duplicate the condition on my box. Long-range debugging is a very slow process. One other thing to note. I have a mac80211 version of the rtl8187se driver that almost works. It is able to receive and transmit short packets. When a packet longer than about 64 bytes is sent, the firmware locks up. I sent my source to Realtek to see if they could see what I'm doing wrong. Their report is that the driver is now working, but not stable. Once that driver is finished, it wil;l; be submitted to mainline, and the version in staging will be dropped. Larry -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
