Date: Fri, 14 Dec 2007 11:56:24 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Michael Buesch <mb@bu3sch.de>
Cc: Ray Lee <ray-lk@madrabbit.org>, bcm43xx-dev@lists.berlios.de,
       Daniel Walker <dwalker@mvista.com>, akpm@linux-foundation.org,
       linux-kernel@vger.kernel.org, linux@bohmer.net, jonathan@jonmasters.org,
       matthias.kaehlcke@gmail.com, kjwinchester@gmail.com, mbuesch@freenet.de,
       John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore
	to mutex
Message-ID: <20071214105624.GC23964@elte.hu>
References: <20071213003028.676998182@mvista.com> <200712131445.39770.mb@bu3sch.de> <2c0942db0712131604m41c34da9hf3122b0603f3af96@mail.gmail.com> <200712140143.16451.mb@bu3sch.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200712140143.16451.mb@bu3sch.de>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1020
Lines: 29


* Michael Buesch <mb@bu3sch.de> wrote:

> > (eth0 is ethernet, eth1 doesn't exist -- usually it's the wireless.)
> > 
> > `ifconfig` doesn't see eth1 or wlan0_rename.
> > 
> > What else might I be doing wrong?
> 
> I don't know. Try ifconfig -a Or tell udev to not crap up your device 
> names.
> 
> > Regardless, perhaps scheduling bcm43xx for removal in 2.6.26 is a 
> > bit premature.
> 
> Oh come on. b43 is more than a year old now. How long should we wait? 
> Two or three? Forever?

possibly forever, if you dont get obvious regressions like "my wlan does 
not work" (reported in this very thread), resolved. Pushing the blame to 
udev (in a rather unfriendly way) wont give users a working system and 
wont get you many new testers for the new driver either.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/