Re: [Wirelessdriver-support] can't transmit 85% of the time..

[Rob M. <ro...@ma...>]

If somebody wants to patch this in the current version, they're welcome 
to.

The new code that will be out very shortly has everything gated and has 
been tested to work on dual processor boxes as well.

-Rob

On Monday, December 2, 2002, at 03:08 PM, Matthew T. Russotto wrote:

>
> On Sunday, December 1, 2002, at 05:47  PM, Andrew Gallatin wrote:
>
>> If this is not a common problem caused by pilot error on my part, then
>> my #1 suspicion is that there is a race condition somewhere which gets
>> worse with a faster CPU.  (ie, this box is brand new, and probably
>> faster than the box the driver was developed on). Perhaps a missing
>> IODelay() that was never noticed on older machines?
>
> I've found at least one race condition -- if you call setNetworkName 
> (which is not gated), the network name variable is set, then the card 
> is reconfigured with the new network name.  If a timer interrupt 
> occurs between those points, the network name variable could get reset 
> before it takes effect.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T 
> handheld. Power & Color in a compact size! 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> Wirelessdriver-support mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support
>
--
"Quidquid latine dictum sit, altum viditur."