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]

Date:	Fri, 14 Dec 2007 14:08:59 +0100
From:	Michael Buesch <mb@...sch.de>
To:	Ingo Molnar <mingo@...e.hu>
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, John Linville <linville@...driver.com>
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex

On Friday 14 December 2007 13:53:27 Ingo Molnar wrote:
> 
> * Michael Buesch <mb@...sch.de> wrote:
> 
> > This user did get the following messages in dmesg:
> > 
> > b43err(dev->wl, "Firmware file \"%s\" not found "
> >        "or load failed.\n", path);
> > b43err(wl, "You must go to "
> >        "http://linuxwireless.org/en/users/Drivers/b43#devicefirmware "
> >        "and download the correct firmware (version 4).\n");
> > 
> > I'm not sure how I can improve that even more. There is a full URL 
> > describing how to get the device workin in _full_ detail.
> 
> well i dont have this hardware, but the following description in this 
> thread seems to contradict that:
> 
> || Well, doing an `rmmod bcm43xx ; modprobe ssb b43` gives me nothing in 
> || dmesg other than lines related to the bcm43xx driver. 
> || iwconfig/ifconfig do not see the interface either.

Let's quote another of Ray's statements:
"And ifconfig -a does indeed show it, sorry about that."

So if he did then try to initialize that device, that clearly
_did_ show up in a standard place where network devices are
expected to show up, he did see the message I quoted.
Well, what if he did not try to initialize the device by doing
an "ifconfig wlanX up"? That can hardly be my fault, right?

-- 
Greetings Michael.
--
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/