When we remove the active interface, there's no need to continue
sending beacons; doing so would cause a null pointer deref in
ieee80211_beacon_get(). Disable the interrupt in remove_interface
and add a WARN_ON(!vif) in case there are other instances lurking.
Signed-off-by: Bob Copeland
---
dri
On Tue, Jun 2, 2009 at 4:10 PM, Mark Hindley wrote:
> I have an initial patch which gives me working leds on my DWL-G630.
>
> It will need cleaning up a bit. In particular, I am not sure if using it
> whenever SOFTLED is not activated is OK. I don't have any other
> hardware, so I can't test.
>
>
On Tue, Jun 02, 2009 at 04:13:33PM -0400, Bob Copeland wrote:
> On Tue, Jun 2, 2009 at 4:10 PM, Mark Hindley wrote:
> > I have an initial patch which gives me working leds on my DWL-G630.
> >
> > It will need cleaning up a bit. In particular, I am not sure if using it
> > whenever SOFTLED is not a
I have an initial patch which gives me working leds on my DWL-G630.
It will need cleaning up a bit. In particular, I am not sure if using it
whenever SOFTLED is not activated is OK. I don't have any other
hardware, so I can't test.
Comments please
Mark
diff --git a/drivers/net/wireless/ath5k/b
I can confirm 1 & 2, i have the same problems on my aspire one.
Also wrt: 1
The reported signal strength is much lower than running say madwifi on
the same hardware/os.
On 1 Jun 2009, at 21:43, Maxim Levitsky wrote:
> Hi,
>
> Just like ath9k thread, here is the list of bugs, I have seen on my
On Tue, Jun 2, 2009 at 2:11 AM, omniprese...@wired® wrote:
> I want to send some way to reproduce or some system logs. Other than
> "dmesg" given it doesn't survive the crash. I want to help!
Try netconsole or a serial console.
--
Bob Copeland %% www.bobcopeland.com
___
