netdev - Re: BCM4313 & brcmsmac & 3.12: only semi-working?

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, 26 Sep 2014 16:42:49 +0200
From:	Arend van Spriel <arend@...adcom.com>
To:	Michael Tokarev <mjt@....msk.ru>
CC:	Seth Forshee <seth.forshee@...onical.com>,
	<brcm80211-dev-list@...adcom.com>,
	<linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: Re: BCM4313 & brcmsmac & 3.12: only semi-working?

On 09/26/14 16:26, Michael Tokarev wrote:
> Okay, so finally, today, without any updates from your side,
> I opened up the laptop again and inserted a newly bought
> Intel 6235ANHMW card instead of this creaky brcm4313.  This
> card works right out of the box - plug it in and set up,
> both wifi and bluetooth (I had numerous probs with bluetooth
> too with brcm card), and it works on both 2.4GHz and 5GHz
> bands.  Connection is very good and stable, I wasn't able
> to trigger a single glitch no matter how hard I tried.

Good for you.

> My only sorry is a lot of wasted time, efforts and money -
> all that have much better value than trying to deal with
> non-working drivers.  And my only wish is so vendors stop
> using non-working parts in their hardware.. But oh well.

Being bold here, but would you be willing to send that non-working part 
of hardware to me. I seem to have 4313 cards over here that just work 
and it would help greatly investigating the issue. I guess you do not 
care that much anymore, but might be others do (myself included).

Regards,
Arend
--
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