Re: iwn not working since 4.99.73

[Brett Lymn <blymn%baesystems.com.au@localhost>]

On Thu, Nov 06, 2008 at 12:18:18AM +0700, Robert Elz wrote:
> 
> The second half ...
> 

That will teach me for bundling unrelated changes..

> * Make sure the ESSID is cleared.
> 
> is simply wrong, at least where you have it, iwn_init() is called in too
> many places to be sticking what is essentially one off init code there.
> As you have it, it is impossible to select an ssid to connect to, as
> when the link is ordered up (or when a media choice is made, and probably
> other times) the selected ssid is zapped by your new code.  If it is needed
> at all, it probably belongs in the attach routine, or somewhere like that.
> I just removed it (for me, the ssid always gets set as part of config,
> so I don't care what the driver thinks it should be before that).
> 

OK - I will shift it.  I did this because I had a report of the driver
"finding" AP's after the SSID had been set to "" using ifconfig but
not before.  I chose the wrong spot.

-- 
Brett Lymn
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email
in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."