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: <200712180018.57272.mb@bu3sch.de>
Date:	Tue, 18 Dec 2007 00:18:56 +0100
From:	Michael Buesch <mb@...sch.de>
To:	mvtodevnull@...il.com
Cc:	"Larry Finger" <larry.finger@...inger.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"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 Tuesday 18 December 2007 00:12:30 mvtodevnull@...il.com wrote:
> On Dec 17, 2007 5:45 PM, Michael Buesch <mb@...sch.de> wrote:
> >
> > Ehm, excuse me.
> > What are you doing exactly? In this thread you told me you have
> > a device which requires b43:
> >
> 
> Well, I'm not sure what you mean by "requires" b43, but I did say that
> the device uses the b43 driver.

Requires means requires.

> Sorry, I should have been more specific. I figured since the device
> could use bcm43xx, it could also use b43legacy, so I copied the
> entries in b43_ssb_tbl[] to b43legacy_ssb_tbl[] and rebuilt the
> b43legacy driver. I removed the b43 and ssb modules, and inserted the
> b43legacy module. Afterwards, I noticed b43 had still been autoloaded,
> so I removed it (I checked dmesg and only b43legacy had initialized
> anyway) , and proceeded to use the b43legacy driver with the version 3
> firmware. And like I said, it works exactly like the b43 driver with
> the version 4 firmware.

I'm not sure what you are trying to show with this hack.
It's been said several times in this thread that the firmware has
nothing to do with the device radio.
So it won't affect the transmit rate or something like that.

Note that the difference between b43 and b43legacy is NOT that the
driver is "legacy". It is called legacy because it does _only_ support
legacy _devices_. So if you hack it to drive a new card it will only
work by luck (luck as in there might be some code left over which
is able to initialize the device somehow.). My point being, we removed
code for new devices from b43legacy and are probably going to remove
even more stuff in the future. So there is simply no point in testing
any new device with b43legacy.

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