All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: James Ketrenos <jketreno@linux.intel.com>,
	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: Thu, 09 Jun 2005 11:33:10 +0800	[thread overview]
Message-ID: <1118287990.10234.114.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20050608223437.GB2614@elf.ucw.cz>

Hi Pavel,

On Thu, 2005-06-09 at 00:34 +0200, Pavel Machek wrote:
> Actually it would still transmit when user did not want it to. I
> believe that staying "quiet" is right thing, long-term. And it could
> solve firmware-loading problems, short-term...

If ipw2100 is built into kernel, you can disable it by kernel parameter
ipw2100.disable=1. Then you can enable it with:

$ echo 0 > /sys/bus/pci/drivers/ipw2100/*/rf_kill

> How long does association with AP take? Anyway it should be easy to
> tell driver to associate ASAP, just after the insmod...

Are you suggesting by default it is disabled for built into kernel but
enabled as a module?

Thanks,
-yi


  reply	other threads:[~2005-06-09  3:36 UTC|newest]

Thread overview: 62+ 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
2005-06-08 14:56   ` Jirka Bohac
2005-06-08 15:24     ` Tomasz Torcz
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-10 21:18                   ` Alejandro Bonilla
2005-06-13 16:42               ` Jan Rychter
2005-06-11 12:44             ` Denis Vlasenko
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 [this message]
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
2005-06-11 17:06 `  Éric Brunet
2005-06-13 10:05   ` Zhu Yi

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=1118287990.10234.114.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=ipw2100-admin@linux.intel.com \
    --cc=jgarzik@pobox.com \
    --cc=jketreno@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.