netdev
[Top] [All Lists]

Re: ipw2100: firmware problem

To: Jirka Bohac <jbohac@xxxxxxx>
Subject: Re: ipw2100: firmware problem
From: Pavel Machek <pavel@xxxxxxx>
Date: Wed, 8 Jun 2005 18:29:48 +0200
Cc: Denis Vlasenko <vda@xxxxxxxxxxxxx>, Pavel Machek <pavel@xxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, Netdev list <netdev@xxxxxxxxxxx>, kernel list <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20050608145653.GA8844@xxxxxxxxxxxxx>
References: <20050608142310.GA2339@xxxxxxxxxx> <200506081744.20687.vda@xxxxxxxxxxxxx> <20050608145653.GA8844@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.27i
Hi!

> > Do you want to associate to an AP when your kernel boots,
> > _before_ any iwconfig had a chance to configure anything?
> > That's strange.
> > 
> > My position is that wifi drivers must start up in an "OFF" mode.
> > Do not send anything. Do not join APs or start IBSS.
> 
> Agreed.

Me too ;-).

> > Thus, no need to load fw in early boot.
> 
> I don't think this is true. Loading the firmware on the first
> "ifconfig up" is problematic. Often, people want to rename the
> device from ethX/wlanX/... to something stable. This is usually
> based on the adapter's MAC address, which is not visible until
> the firmware is loaded.
> 
> Prism54 does it this way and it really sucks. You need to bring
> the adapter up to load the firmware, then bring it back down,
> rename it, and bring it up again.
> 
> Denis: any plans for this to be fixed?
> 
> I agree that drivers should initialize the adapter in the OFF
> state, but the firmware needs to be loaded earlier than the
> first ifconfig up.
> 
> How about loading the firmware when the first ioctl touches the
> device? This way, it would get loaded just before the MAC address
> is retrieved.

Thats really ugly :-(.

                                Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


<Prev in Thread] Current Thread [Next in Thread>