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: <CACna6rzv6iFiGP5F2mMs+2wxh0rVpXcXyBjve2Nbn9Ybp8AFsg@mail.gmail.com>
Date:	Thu, 12 Jan 2012 08:08:50 +0100
From:	Rafał Miłecki <zajec5@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Larry Finger <Larry.Finger@...inger.net>,
	Arend van Spriel <arend@...adcom.com>,
	"John W. Linville" <linville@...driver.com>,
	Network Development <netdev@...r.kernel.org>,
	"Franky (Zhenhui) Lin" <frankyl@...adcom.com>
Subject: Re: brcm80211 breakage..

2012/1/12 Linus Torvalds <torvalds@...ux-foundation.org>:
> On Wed, Jan 11, 2012 at 9:20 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>> Maybe your BIOS firmware sets things up, and the Apple Macbook Air
>> doesn't? And the driver used to initialize things sufficiently, and
>> the changes have broken that?
>
> The code in v3.2 also used to support srom rev < 4, the new code
> doesn't seem to do that.

After hacking bcma to read SPROM from the correct location, what did
you get in dmesg? There should be info about version of SPROM.

There are 2 possible reasons for this issue:
1) bcma doesn't fully init your card
2) brcmsmac does sth wrong incorrectly as init

The story with brcmsmac is that it had code duplicated with bcma at
first. Now they partially switched to bcma, which inits bus for them,
and provide access to bus devices. However I'm afraid Broadcom didn't
remove duplicated init code (correct me if i'm wrong!). They may be
re-initializing bus and it's devices which cause some problems...

Linus: is this possible for you to give b43 a chance? It has to be compiled with
B43_BCMA
B43_PHY_N
Unfortunately you have to install firmware manually to get b43 working
:( Howto is located at:
http://wireless.kernel.org/en/users/Drivers/b43
("Install b43-fwcutter" and "If you are using the b43 driver from 3.2
kernel or newer:").

b43 doesn't re-init bus devices, so this test will check if bcma is OK or not.

-- 
Rafał
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ