Re: [zd1211-devs] zd1211 vendor driver on 2.6.35.10
Status: Beta
Brought to you by:
mayne
From: Hin-Tak L. <hin...@ya...> - 2011-05-12 07:58:44
|
Nerijus Baliunas wrote: > On Wed, 16 Feb 2011 01:28:19 +0000 (GMT) Hin-Tak Leung > <ht...@us...> wrote: > >> I use it mainly for the AP mode, on an old machine that has just been >> resurrected after over a year, so the last it worked was on 2.6.31.x . >> There are a couple of old and new quirks: a dozen of 'We are trapped in >> zd_SigProcess, Going to release all,id=3,block=1' is new to 2.6.35.x, but >> the driver has always needed if down/up and or iwlist scan before a client >> station can connect, and that's still the case; and under extended use (a >> few days, and/or a few GB traffic) it can still bring the AP machine down. >> >> I see some great person has just had a whole bunch of patches committed to >> wireless-testing in the last few months for enabling AP mode for the >> in-kernel zd1211rw driver... so 2.6.39(?) or thereabout it would be >> generally available...so the use of the vendor driver for AP mode would >> soon not be needed any more. I'd probably give the compat-wireless a try >> soon enough. > > There is a patch at http://ankalagon.ru/notes/patch-na-zd1211rw which adds AP > mode in a very simple way, and it actually works! I had to modify the first > hunk slightly for kernel 2.6.38, modified patch below: It looks like a non-standard(ugly?) hack though, and not likely to work with standard linux AP-setup instruction... in any case, the "official" change has already happened - once something is in the wireless-testing branch of the kernel, it is just a matter of time before it reaches Linus himself. The process usually takes a few months between a change appearing in wireless testing to it appearing in the official release. |