| To: | pavel@xxxxxx |
|---|---|
| Subject: | Re: ipw2100: firmware problem |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Thu, 09 Jun 2005 12:53:24 -0700 (PDT) |
| Cc: | vda@xxxxxxxxxxxxx, abonilla@xxxxxxxxxxxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, ipw2100-admin@xxxxxxxxxxxxxxx |
| In-reply-to: | <20050609104205.GD3169@xxxxxxxxxx> |
| References: | <200506090909.55889.vda@xxxxxxxxxxxxx> <20050608.231657.59660080.davem@xxxxxxxxxxxxx> <20050609104205.GD3169@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Pavel Machek <pavel@xxxxxx> Date: Thu, 9 Jun 2005 12:42:05 +0200 > I'm not saying it should not work automagically. But it is wrong to > start transmitting on wireless as soon as kernel boots. It should stay > quiet in the radio until it is either told to talk or until interface > is upped. I agree. There is a similar problem in the Acenic driver, it brings the link up and receives broadcast packets as soon as the driver is loaded. Mostly this is because the driver inits the chip and registers the IRQ handler at probe time, whereas nearly every other driver does this at ->open() time. |
| Previous by Date: | Re: 2.4.30-hf1 do_IRQ stack overflows, Marcelo Tosatti |
|---|---|
| Next by Date: | [patch] 8548 support for eTSEC, Andy Fleming |
| Previous by Thread: | Re: ipw2100: firmware problem, Pavel Machek |
| Next by Thread: | Re: ipw2100: firmware problem, James Ketrenos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |