Brad Langhorst schrieb:
> with the release version of ndiswrapper i'm able to insert ndiswrapper
> and set the essid of the interface .
> if i also specify the channel iwconfig reports the correct mac address
> for the AP
> i've also tried with cvs and debugging enabled... (see the attached log)
> what can i do to help resolv this?
> i've been lurking a while but haven't seen anything about this
> serialized driver issue. nothing explanitory in the archive or the faq
> either. What is the problem with "serialized" drivers - and what does
> "serialized" mean in this context?
I'm also trying to get the internal Atheros-based a/b/g card of my R30
work. A few weeks ago I developed a patch to fix the problem with the
timers you described. It works, but then the driver chrashes as soon as
you try to send some data. And you can still not switch it to ad-hoc
mode (that's my personal requirement).
My patch is currently under examination by the maintainers. One of them
have access to similar hardware now, and I'm also trying to look at this
issue again. So we may see a solution soon - hopefully :)