From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw) Date: Sun, 24 Sep 2006 16:18:03 +1000 Message-ID: <1159078683.5924.16.camel@localhost.localdomain> References: <1159065798.5924.8.camel@localhost.localdomain> <4515FF5D.4080602@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org Return-path: To: Daniel Drake In-Reply-To: <4515FF5D.4080602-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: bcm43xx-dev-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org Errors-To: bcm43xx-dev-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org List-Id: netdev.vger.kernel.org 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 triggers races in softmac relatively easily, which are > hard to fix properly. At least for me, motivation to work on this stuff > is low given the potentially impending merge of devicescape, and every > time I do spend some time investigating I just get even more frustrated > at how difficult WE is to implement *properly* for "non-hardmac" > drivers. We really have a need for a configuration system designed > around 802.11. > > I agree, the stuff in mainline should be fixed, but at least personally > I am finding it harder and harder to justify working on softmac. 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 ? Cheers, Ben.