linux-kernel - Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 Dec 2007 11:56:24 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Michael Buesch <mb@...sch.de>
Cc:	Ray Lee <ray-lk@...rabbit.org>, bcm43xx-dev@...ts.berlios.de,
	Daniel Walker <dwalker@...sta.com>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux@...mer.net,
	jonathan@...masters.org, matthias.kaehlcke@...il.com,
	kjwinchester@...il.com, mbuesch@...enet.de,
	John Linville <linville@...driver.com>
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore
	to mutex


* Michael Buesch <mb@...sch.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/