| To: | vda@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: ipw2100: firmware problem |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Wed, 08 Jun 2005 23:10:45 -0700 (PDT) |
| Cc: | jketreno@xxxxxxxxxxxxxxx, pavel@xxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, ipw2100-admin@xxxxxxxxxxxxxxx |
| In-reply-to: | <200506090903.49295.vda@ilport.com.ua> |
| References: | <42A7268D.9020402@linux.intel.com> <20050608.124332.85408883.davem@davemloft.net> <200506090903.49295.vda@ilport.com.ua> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Denis Vlasenko <vda@xxxxxxxxxxxxx> Date: Thu, 9 Jun 2005 09:03:49 +0300 > You practically cannot avoid having initrd because you are very likely > to need to do some wifi config (at least ESSID and mode). I need neither at home. It comes up by default just fine with ifconfig. Your points are valid, but they do not detract from the fact that pieced up drivers, half in the kernel half somewhere else, is total madness. It is a lose for the user. |
| Previous by Date: | Re: ipw2100: firmware problem, Denis Vlasenko |
|---|---|
| Next by Date: | [PATCH] iseries_veth: Supress spurious WARN_ON() at module unload, Michael Ellerman |
| Previous by Thread: | Re: ipw2100: firmware problem, Denis Vlasenko |
| Next by Thread: | Re: ipw2100: firmware problem, Denis Vlasenko |
| Indexes: | [Date] [Thread] [Top] [All Lists] |