| To: | Pavel Machek <pavel@xxxxxx> |
|---|---|
| Subject: | Re: ipw2100: firmware problem |
| From: | Zhu Yi <yi.zhu@xxxxxxxxx> |
| Date: | Thu, 09 Jun 2005 11:33:10 +0800 |
| Cc: | James Ketrenos <jketreno@xxxxxxxxxxxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, Netdev list <netdev@xxxxxxxxxxx>, kernel list <linux-kernel@xxxxxxxxxxxxxxx>, "James P. Ketrenos" <ipw2100-admin@xxxxxxxxxxxxxxx> |
| In-reply-to: | <20050608223437.GB2614@xxxxxxxxxx> |
| Organization: | Intel Corp. |
| References: | <20050608142310.GA2339@xxxxxxxxxx> <42A723D3.3060001@xxxxxxxxxxxxxxx> <20050608212707.GA2535@xxxxxxxxxx> <42A76719.2060700@xxxxxxxxxxxxxxx> <20050608223437.GB2614@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 1/1] sysctl configurable icmperror sourceaddress, Lennert Buytenhek |
|---|---|
| Next by Date: | 2.6.12-rc6-mm1 OOPS in tcp_push_one(), Valdis . Kletnieks |
| Previous by Thread: | Re: ipw2100: firmware problem, Pavel Machek |
| Next by Thread: | Re: ipw2100: firmware problem, Pavel Machek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |