From: Denis Vlasenko <vda@ilport.com.ua>
To: Pavel Machek <pavel@ucw.cz>, Jeff Garzik <jgarzik@pobox.com>,
Netdev list <netdev@oss.sgi.com>,
kernel list <linux-kernel@vger.kernel.org>,
"James P. Ketrenos" <ipw2100-admin@linux.intel.com>
Subject: Re: ipw2100: firmware problem
Date: Wed, 8 Jun 2005 17:44:20 +0300 [thread overview]
Message-ID: <200506081744.20687.vda@ilport.com.ua> (raw)
In-Reply-To: <20050608142310.GA2339@elf.ucw.cz>
On Wednesday 08 June 2005 17:23, Pavel Machek wrote:
> Hi!
>
> I'm fighting with firmware problem: if ipw2100 is compiled into
> kernel, it is loaded while kernel boots and firmware loader is not yet
> available. That leads to uninitialized (=> useless) adapter.
>
> What's the prefered way to solve this one? Only load firmware when
> user does ifconfig eth1 up? [It is wifi, it looks like it would be
> better to start firmware sooner so that it can associate to the
> AP...].
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.
Thus, no need to load fw in early boot.
Driver may load firmware and start actively doing something
only when iwconfig gets executed and thus driver is
instructed what to do.
Some drivers currently do not act this way, and thus
less advanced users may unknowingly run a wireless STA
(or worse, an AP!) on their notebook for years, interfering
with neighbors and/or violating local regulations (there are
countrles where 802.11 use needs licensing).
--
vda
next prev parent reply other threads:[~2005-06-08 14:44 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 14:23 ipw2100: firmware problem Pavel Machek
2005-06-08 14:44 ` Denis Vlasenko [this message]
2005-06-08 14:56 ` Jirka Bohac
2005-06-08 16:29 ` Pavel Machek
2005-06-21 7:42 ` Simon Kelley
2005-06-21 8:29 ` Feyd
2005-06-21 8:46 ` Simon Kelley
2005-06-08 15:05 ` Alejandro Bonilla
2005-06-08 15:23 ` Jiri Benc
2005-06-09 6:09 ` Denis Vlasenko
2005-06-09 6:16 ` David S. Miller
2005-06-09 6:25 ` Denis Vlasenko
2005-06-09 6:28 ` David S. Miller
2005-06-09 6:37 ` Denis Vlasenko
2005-06-09 8:36 ` Wichert Akkerman
2005-06-09 10:42 ` Pavel Machek
2005-06-09 19:53 ` David S. Miller
2005-06-09 21:01 ` James Ketrenos
2005-06-09 21:11 ` Pavel Machek
2005-06-09 21:15 ` Arjan van de Ven
2005-06-09 22:11 ` David S. Miller
2005-06-10 2:13 ` Jeff Garzik
2005-06-10 2:46 ` Alejandro Bonilla
2005-06-10 9:00 ` Pavel Machek
2005-06-10 13:00 ` John Stoffel
2005-06-10 13:33 ` Alejandro Bonilla
2005-06-09 14:31 ` Alejandro Bonilla
2005-06-10 6:56 ` Denis Vlasenko
2005-06-10 13:23 ` Alejandro Bonilla
2005-06-10 20:26 ` Lee Revell
2005-06-10 21:00 ` Alejandro Bonilla
2005-06-10 21:07 ` Lee Revell
2005-06-13 16:42 ` Jan Rychter
2005-06-11 12:44 ` Denis Vlasenko
2005-06-08 17:10 ` James Ketrenos
2005-06-08 19:43 ` David S. Miller
2005-06-08 19:49 ` Dave Jones
2005-06-08 19:54 ` David S. Miller
2005-06-09 6:03 ` Denis Vlasenko
2005-06-09 6:10 ` David S. Miller
2005-06-09 6:17 ` Denis Vlasenko
2005-06-09 6:20 ` David S. Miller
2005-06-09 6:30 ` Denis Vlasenko
2005-06-09 6:35 ` David S. Miller
2005-06-10 3:51 ` Jim Crilly
2005-06-09 6:06 ` Jeff Garzik
2005-06-09 6:13 ` David S. Miller
2005-06-09 6:29 ` Jeff Garzik
2005-06-08 16:58 ` James Ketrenos
2005-06-08 21:27 ` Pavel Machek
2005-06-08 21:46 ` James Ketrenos
2005-06-08 22:34 ` Pavel Machek
2005-06-09 3:33 ` Zhu Yi
2005-06-09 10:56 ` Pavel Machek
2005-06-09 13:56 ` Andi Kleen
2005-06-09 21:12 ` Olivier Galibert
2005-06-09 23:13 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506081744.20687.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=ipw2100-admin@linux.intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).