From: Jouni Malinen (jkmaline_at_cc.hut.fi)
Date: 2002-08-13 15:06:47 UTC
On Fri, Aug 09, 2002 at 05:27:39PM +0900, ���￭ wrote:
> when I try to load driver using prism 2.0 card it looks like work correctly and client can access the AP
> but, when I try with prism 2.5 or 3.0 card the driver can't get any information from the card from hfa384x_get_rid()
That's quite odd.. There shouldn't really be that kind of differences between Prism2 and Prism2.5/3..
> --------------------- with prism 2.0 card
> prism2_hw_config: initialized in -440674 iterations
Something wrapping around here?
> prism2_hw_init() == local->is_symbol = 2364
> +++++++++++++++++++++ with prism 2.5 card
> prism2_hw_init() == local->is_symbol = 1600
This was the only difference I noticed here.. Apparently the driver tried to use smaller TX fid with this card. This should work, but maybe you should test with the same TX buffer size also with this card.
Have you tested latest CVS snapshot? It has removed the bogus is_symbol verification and first tries to allocate large buffer and only if that fails, it will try to get a smaller buffer (as a workaround for problems with Symbol cards).
-- Jouni Malinen PGP id EFC895FA