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]
Date:	Fri, 14 Dec 2007 20:59:25 -0500
From:	mvtodevnull@...il.com
To:	"Larry Finger" <larry.finger@...inger.net>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, "Michael Buesch" <mb@...sch.de>,
	"Daniel Walker" <dwalker@...sta.com>,
	"Ray Lee" <ray-lk@...rabbit.org>,
	"Simon Holm Thøgersen" <odie@...aau.dk>,
	matthias.kaehlcke@...il.com, linux-kernel@...r.kernel.org,
	linux@...mer.net, "Ingo Molnar" <mingo@...e.hu>,
	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

On Dec 14, 2007 7:58 PM, Larry Finger <larry.finger@...inger.net> wrote:
> Rafael J. Wysocki wrote:
> >
> > Actually, can you explain why, from the technical point of view, the version 4
> > firware is better than version 3, please?
>
> I will be very interested in Michael's answer to this question; however, my experience is that it
> doesn't make much difference if your device is supported by both V3 and V4 firmware. This impression
> was obtained by comparing BCM4318 and BCM4311/1 devices with b43 and b43legacy.
>
> Note that 802.11b and early BCM4306 devices are not supported by V4 firmware.

Could this be the reason my BCM94311MCG rev 1 receives such terrible
performance with b43 but works well with bcm43xx? The device is
802.11b/g but my router is 802.11b. I filed a report on this issue
here: https://bugzilla.redhat.com/show_bug.cgi?id=413291

I was told by Michael that I would have to fix it myself, and I am
trying, but the learning curve is a little steep. If this is relevant,
I might at least have some direction to go in.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ