On Tue, Apr 7, 2009 at 5:08 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Tue, Apr 07, 2009 at 12:49:30AM -0700, Hin-Tak Leung wrote: >> On Tue, Apr 7, 2009 at 6:34 AM, Luis R. Rodriguez >> <lrodriguez@xxxxxxxxxxx> wrote: >> >> > Not sure, I wanted to get this out to help those who are interested in >> > porting changes over (if any) to zd1211rw. If you find nothing useful >> > from it please simply disregard it. >> >> It is vaguely relevant in that (1) there are new and old features >> which are not in the rw driver yet - e.g. the AP mode, and >> 3.0 introduces newly antenna diversity, (2) to port changes - either >> new-hardware related, or bug-fixes/improvements, they need to be >> proven to work-better ... e.g. blindly copying could just copy >> mistakes/regressions... > > Right, that is the idea. It has been 6 weeks - I re-visited the code and found a mistake of mine, and managed to get it to compile against 2.6.29.3-159.fc11.x86_64 and 2.6.28.8 vanila 32-bit . It definitely does *not* work correctly on x86_64 linux - I get a rather wierd problem where register-read of the last 16-bit of the mac address from firmware _apparently_ fails, but it is fed to the next register-read and the result of the next register-read is received by the next-next-read, etc. (i.e. the result of a read is received by the next read). For 32-bit, it seems to work alright, except for one oop in AP mode when a client connects so far (out of a few connects). This is just a head-up that I have a series of diffs to port the vendor driver forward to current kernels, if anybody wants to have a look, for side-by-side scavenging to the rw driver. (I probably will post them to the sourceforge zd1211-dev list after a little look at that oops) BTW, anybody has any idea what else is needed for the rw driver to support AP mode? -- 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
