From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw) Date: Mon, 25 Sep 2006 11:02:39 +0200 Message-ID: <1159174960.4509.13.camel@ux156> References: <1159065798.5924.8.camel@localhost.localdomain> <4515FF5D.4080602@gentoo.org> <1159078683.5924.16.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Daniel Drake , Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: To: Benjamin Herrenschmidt In-Reply-To: <1159078683.5924.16.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@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 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, there are next to no useful locks in it and most data structures are not protected at all. johannes