Linux wireless drivers development
 help / color / mirror / Atom feed
* wpa supplicant interface up delay
@ 2008-10-07 18:16 Johannes Berg
  2008-10-07 18:18 ` Johannes Berg
  2008-10-07 19:44 ` Jouni Malinen
  0 siblings, 2 replies; 4+ messages in thread
From: Johannes Berg @ 2008-10-07 18:16 UTC (permalink / raw)
  To: linux-wireless; +Cc: Jouni Malinen, Dan Williams

[-- Attachment #1: Type: text/plain, Size: 475 bytes --]

                         * Wait some time to allow driver to initialize before
                         * starting configuring the driver. This seems to be  
                         * needed at least some drivers that load firmware etc.
                         * when the interface is set up.

which drivers are those, and why can't we fix the drivers instead? This
seems like a bug in the drivers that they return from their open
callback prematurely.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: wpa supplicant interface up delay
  2008-10-07 18:16 wpa supplicant interface up delay Johannes Berg
@ 2008-10-07 18:18 ` Johannes Berg
  2008-10-07 18:18   ` John W. Linville
  2008-10-07 19:44 ` Jouni Malinen
  1 sibling, 1 reply; 4+ messages in thread
From: Johannes Berg @ 2008-10-07 18:18 UTC (permalink / raw)
  To: linux-wireless; +Cc: Jouni Malinen, Dan Williams

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

On Tue, 2008-10-07 at 20:16 +0200, Johannes Berg wrote:
> * Wait some time to allow driver to initialize before
>                          * starting configuring the driver. This seems to be  
>                          * needed at least some drivers that load firmware etc.
>                          * when the interface is set up.
> 
> which drivers are those, and why can't we fix the drivers instead? This
> seems like a bug in the drivers that they return from their open
> callback prematurely.

In any case, this delay should certainly be removed from the nl80211
driver; when porting drivers to the new APIs we can make sure this is
done correctly.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: wpa supplicant interface up delay
  2008-10-07 18:18 ` Johannes Berg
@ 2008-10-07 18:18   ` John W. Linville
  0 siblings, 0 replies; 4+ messages in thread
From: John W. Linville @ 2008-10-07 18:18 UTC (permalink / raw)
  To: Johannes Berg; +Cc: linux-wireless, Jouni Malinen, Dan Williams

On Tue, Oct 07, 2008 at 08:18:18PM +0200, Johannes Berg wrote:
> On Tue, 2008-10-07 at 20:16 +0200, Johannes Berg wrote:
> > * Wait some time to allow driver to initialize before
> >                          * starting configuring the driver. This seems to be  
> >                          * needed at least some drivers that load firmware etc.
> >                          * when the interface is set up.
> > 
> > which drivers are those, and why can't we fix the drivers instead? This
> > seems like a bug in the drivers that they return from their open
> > callback prematurely.
> 
> In any case, this delay should certainly be removed from the nl80211
> driver; when porting drivers to the new APIs we can make sure this is
> done correctly.

ACK

-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: wpa supplicant interface up delay
  2008-10-07 18:16 wpa supplicant interface up delay Johannes Berg
  2008-10-07 18:18 ` Johannes Berg
@ 2008-10-07 19:44 ` Jouni Malinen
  1 sibling, 0 replies; 4+ messages in thread
From: Jouni Malinen @ 2008-10-07 19:44 UTC (permalink / raw)
  To: Johannes Berg; +Cc: linux-wireless, Dan Williams

On Tue, Oct 07, 2008 at 08:16:01PM +0200, Johannes Berg wrote:
>                          * Wait some time to allow driver to initialize before
>                          * starting configuring the driver. This seems to be  
>                          * needed at least some drivers that load firmware etc.
>                          * when the interface is set up.
> 
> which drivers are those, and why can't we fix the drivers instead? This
> seems like a bug in the drivers that they return from their open
> callback prematurely.

I've observed issues with a driver that (at least at the time) was not
fully open source. I didn't feel like fixing the driver at the time.

Anyway, I'm perfectly fine with removing this from nl80211. As far as
driver_wext.c is concerned, I would like to first verify what the
original issue is and whether the driver could be fixed easily.

-- 
Jouni Malinen                                            PGP id EFC895FA

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-10-07 19:45 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-07 18:16 wpa supplicant interface up delay Johannes Berg
2008-10-07 18:18 ` Johannes Berg
2008-10-07 18:18   ` John W. Linville
2008-10-07 19:44 ` Jouni Malinen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox