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: <1197637194.7549.10.camel@odie.local>
Date:	Fri, 14 Dec 2007 13:59:54 +0100
From:	Simon Holm Thøgersen <odie@...aau.dk>
To:	Michael Buesch <mb@...sch.de>
Cc:	Ingo Molnar <mingo@...e.hu>, 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


fre, 14 12 2007 kl. 13:31 +0100, skrev Michael Buesch:
> On Friday 14 December 2007 13:16:17 Ingo Molnar wrote:
> > 
> > * Michael Buesch <mb@...sch.de> wrote:
> > 
> > > > The testers who did nothing but reported that the new driver did not 
> > > > work on their hardware.
> > > 
> > > Which testers?
> > 
> > right in this thread Ray Lee is reporting:
> > 
> > | | Digging a little farther into it, it looks like b43 is barfing 
> > | | partway through init as the firmware file it's looking for has 
> > | | changed names. Perhaps that's the issue. I'll take a longer look at
        ^^^^^^^^^^^^^^
Ray probably has version 3 of the firmware.

> > | | this all tomorrow.
> > 
> > you are really in denial of reality. Just re-read this thread. Upon 
> > re-reading this thread, try to imagine that you are in place of Ray Lee 
> > (might be hard), that you had a working bcm43xx driver and that now you 
> > try to get b43 to work. You are not a kernel hacker who knows this 
> > driver, just an advanced user who'd like to give you some more feedback 
> > about your shiny new code.
> 
> This user did get the following messages in dmesg:
> 
> b43err(dev->wl, "Firmware file \"%s\" not found "
>        "or load failed.\n", path);

So the question seems to be why b43 needs version 4, when b43legacy and
bcm43x uses version 3?


Simon Holm Thøgersen

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