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: Windows password security audit tool. GUI, reports in PDF.

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

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

"John W. Linville" <linville@...driver.com> wrote:

> On Fri, Dec 14, 2007 at 11:56:24AM +0100, Ingo Molnar wrote:
>>
>> * Michael Buesch <mb@...sch.de> wrote:
>
>> > 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.
>
> It is true that Michael can be a little unpleasant at times.
> The colloquialism that comes to mind is that he "does not suffer fools
> lightly".  Hopefully he will take your counseling to heart and learn
> to be a bit more moderate in his tone.  FWIW, he is still young. :-)

No way. He's just inhuman. :P

> That said, it is also true that the b43[legacy] driver[s] do a more
> than adequate job of replacing the old bcm43xx driver provided that
> one (re-)installs the proper firmware.  And I know of no other driver
> that goes to more trouble to tell you how to get the proper firmware
> installed than this one.
>
> The bcm43xx driver will be added to the feature removal schedule
> in 2.6.25.  Proper judgment will be used in deciding the actual date
> of its removal.  In the meantime hopefully every distribution will
> have or obtain a working udev configuration.  If things don't work
> out as planned then we will re-evaluate.
>
> Let's stop this now please.

Agreed. As a b43legacy maintainer, I'd be happy to know if Ingo  
suggests other ways to smooth out the transition. I haven't read  
proposals yet.


--
Ciao
Stefano



--
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/