From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Buesch Subject: Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw) Date: Sun, 24 Sep 2006 10:43:49 +0200 Message-ID: <200609241043.49772.mb@bu3sch.de> References: <1159065798.5924.8.camel@localhost.localdomain> <200609241005.02024.mb@bu3sch.de> <1159085579.5924.25.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, Bcm43xx-dev@lists.berlios.de, Daniel Drake Return-path: Received: from static-ip-62-75-166-246.inaddr.intergenia.de ([62.75.166.246]:25036 "EHLO bu3sch.de") by vger.kernel.org with ESMTP id S1751678AbWIXIn4 (ORCPT ); Sun, 24 Sep 2006 04:43:56 -0400 To: Benjamin Herrenschmidt In-Reply-To: <1159085579.5924.25.camel@localhost.localdomain> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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. > > Ealiest 2.6.20 but likely one or two releases later (me thinks). > > Which means we'll still have nothing near decent wireless for what ... 6 > monthes min ? 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. -- Greetings Michael.