Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-25 Thread Johannes Berg
On Mon, 2006-09-25 at 19:58 +1000, Benjamin Herrenschmidt wrote: > Doh ! Scary... locking is hard ... if the stuff was written without > locking in mind in the first place, it might end up being a nightmare... Yeah, I've actually suggested "rewriting" it from its own pieces :) But Jiri says he un

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-25 Thread Benjamin Herrenschmidt
> yes. Many locking issues in d80211 to still sort out. Basically, there > are next to no useful locks in it and most data structures are not > protected at all. Doh ! Scary... locking is hard ... if the stuff was written without locking in mind in the first place, it might end up being a nightma

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-25 Thread Johannes Berg
On Sun, 2006-09-24 at 16:18 +1000, Benjamin Herrenschmidt wrote: > So what are the chances of getting this dscape stack merged, let's > say... for 2.6.19 ? 0 > Or we'll get yet another full release with barely > working wireless ? yes. Many locking issues in d80211 to still sort out. Basically

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Michael Buesch
On Sunday 24 September 2006 17:34, Daniel Drake wrote: > Michael Buesch wrote: > > Well. Works For Me (tm). > > If there is some bug for you in current mainline, it needs to > > be fixed. But I can't fix something I am not able to reproduce and > > don't know what happens. > > Take a look at the l

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Dan Williams
On Sun, 2006-09-24 at 16:13 +1000, Benjamin Herrenschmidt wrote: > > prism54 fullmac, right? > > Yes. > > > Try using -Dwext; the prism54 wpa_supplicant driver is a dead-end and I > > added WE-19 commands to it a bit ago anyway. Oddly enough, I couldn't > > seem to get the driver to work reliabl

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Daniel Drake
Michael Buesch wrote: Well. Works For Me (tm). If there is some bug for you in current mainline, it needs to be fixed. But I can't fix something I am not able to reproduce and don't know what happens. Take a look at the logs in Ben's original mail. I've seen this a lot myself and am fairly sur

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Benjamin Herrenschmidt
On Sun, 2006-09-24 at 10:43 +0200, Michael Buesch wrote: > On Sunday 24 September 2006 10:12, Benjamin Herrenschmidt wrote: > > > > So what are the chances of getting this dscape stack merged, let's > > > > say... for 2.6.19 ? Or we'll get yet another full release with barely > > > > working wirele

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Michael Buesch
On Sunday 24 September 2006 10:12, Benjamin Herrenschmidt wrote: > > > So what are the chances of getting this dscape stack merged, let's > > > say... for 2.6.19 ? Or we'll get yet another full release with barely > > > working wireless ? > > > > I don't think it's possible to happen for 2.6.19. >

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Benjamin Herrenschmidt
> > So what are the chances of getting this dscape stack merged, let's > > say... for 2.6.19 ? Or we'll get yet another full release with barely > > working wireless ? > > I don't think it's possible to happen for 2.6.19. > Ealiest 2.6.20 but likely one or two releases later (me thinks). Which me

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-24 Thread Michael Buesch
On Sunday 24 September 2006 08:18, Benjamin Herrenschmidt wrote: > On Sat, 2006-09-23 at 23:45 -0400, Daniel Drake wrote: > > Benjamin Herrenschmidt wrote: > > > Oh and I don't care about "it works in dscape stack" sort of crap I > > > regulary get. I want something that > > > works with upstream

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-23 Thread Benjamin Herrenschmidt
On Sat, 2006-09-23 at 23:45 -0400, Daniel Drake wrote: > Benjamin Herrenschmidt wrote: > > Oh and I don't care about "it works in dscape stack" sort of crap I > > regulary get. I want something that > > works with upstream kernels. That isn't that much to ask... or is it ? > > wpa_supplicant trig

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-23 Thread Benjamin Herrenschmidt
> prism54 fullmac, right? Yes. > Try using -Dwext; the prism54 wpa_supplicant driver is a dead-end and I > added WE-19 commands to it a bit ago anyway. Oddly enough, I couldn't > seem to get the driver to work reliably for me using straight WEP > either, let alone WPA. It's pretty unmaintained

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-23 Thread Dan Williams
On Sun, 2006-09-24 at 12:43 +1000, Benjamin Herrenschmidt wrote: > Hi folks ! > > So this is 2.6.18 + Larry "fix" (though I've seen this problem before, > it seems using WPA just make it happen more often). > > This is also a 4318, so the link is pretty weak due to the Tx Power > problem and I su

Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-23 Thread Daniel Drake
Benjamin Herrenschmidt wrote: Oh and I don't care about "it works in dscape stack" sort of crap I regulary get. I want something that works with upstream kernels. That isn't that much to ask... or is it ? wpa_supplicant triggers races in softmac relatively easily, which are hard to fix proper

bcm43xx driver unstable behaviour (and linux wireless is junk btw)

2006-09-23 Thread Benjamin Herrenschmidt
Hi folks ! So this is 2.6.18 + Larry "fix" (though I've seen this problem before, it seems using WPA just make it happen more often). This is also a 4318, so the link is pretty weak due to the Tx Power problem and I suspects it makes the driver problems more visible... So basically, I "lose" the