commit f04b3787bbce4567e28069a9ec97dcd804626ac7 introduced
a regression for the ofdmtable writing.
It incorrectly removed the writing of the high 16bits for
a 32bit table write and initialized the direction identifier
too late.
This patch does also some cleanups to make the code much more
readabl
> It would be great if you have some time to further continue development
> on the driver. We always need new developers who know what they do. :)
Not sure I do qualify w/r to the "who know what they do" part but I'm
willing to try :)
Best,
Michael
--
Michael Gerdau email: [EMAIL PROTECTE
On Sunday 09 December 2007 12:37:27 John H. wrote:
> i dont know what other ones i would have used. bcm43xx never worked
> right, really, and had bandwidth limitations.
>
> Right now I am downloading over a wireless lan and getting 1mb/s.
> Why? That just makes no sense.
Because it's broken?
On Sunday 09 December 2007 12:31:40 Michael Gerdau wrote:
> > Can you send me the code you have? I am going to buy various N devices.
> > So I want to avoid duplicating work.
>
> Yes, sure.
> I'll do a bit of cleaning up and mail it to you (either tonight or
> tomorrow).
>
> I also have a few are
> Can you send me the code you have? I am going to buy various N devices.
> So I want to avoid duplicating work.
Yes, sure.
I'll do a bit of cleaning up and mail it to you (either tonight or
tomorrow).
I also have a few areas where I feel I'm stuck (this being my very first
kernel/driver project
On Sunday 09 December 2007 09:01:26 John H. wrote:
> no, i stopped using ndiswrapper a while back because I wanted to use
> b43, but I did not have this issue then.
But ndiswrapper doesn't use mac80211, right?
Do you see this issue with other _mac80211_ drivers?
> On Dec 8, 2007 2:35 PM, Michael
