From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Problem with BCM943224
Date: Thu, 10 Mar 2011 12:35:29 -0600 [thread overview]
Message-ID: <4D7919F1.3070106@lwfinger.net> (raw)
In-Reply-To: <AANLkTikb8z-NqGdgWz9Ua+8pWm3Vts2uT9sh7ez6OYVB@mail.gmail.com>
On 03/10/2011 11:40 AM, Rafał Miłecki wrote:
>
> I guess you do not need that anymore, but I said to check, so... That
> notebook that was shipped with BCM4313 is HP G62-A10sw.
>
> I've taken BCM4313 from that notebook and put it in my cheap adapter.
> It didn't work (again, all reads 1). It seems that my adapter does not
> like any AI based card. It accepts SSB based cards only. At least now
> I know it is not my BCM943223 that is faulty, but adapter. I'm sure
> BCM4313 is fine, because it works OK in that HP notebook.
>
> Bad news: that dumb, dumb, dumb HP has 14e4:4727 (BCM4313)
> whitelisted, but 14e4:4353 (BCM43224) is blacklisted. Who the hell
> designed that :|
The lawyers. HP's argument is that it cannot allow any combination that has not
been tested for regulatory compliance. It carries about as much validity as
Broadcom's lawyers not allowing redistribution of firmware for regulatory
reasons. I've gotten quite good at hot plugging the PCIe card while at the GRUB
prompt. Someday, I'll get mad enough to rewrite that part of the BIOS.
Other than these screwy BIOS problems, I like HP laptops, but I don't think I'll
get another of theirs due to this whitelisting problem. I think Dell does not
have this difficulty. Unfortunately, they seem to offer very few setups with AMD
processors - my choice.
Larry
next prev parent reply other threads:[~2011-03-10 18:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 10:59 Problem with BCM943224 Rafał Miłecki
2011-03-09 15:44 ` Larry Finger
2011-03-09 16:26 ` Rafał Miłecki
2011-03-09 16:38 ` Larry Finger
2011-03-09 16:50 ` Rafał Miłecki
2011-03-09 16:53 ` Gábor Stefanik
2011-03-09 17:11 ` Larry Finger
2011-03-09 18:04 ` Rafał Miłecki
2011-03-09 18:44 ` Larry Finger
2011-03-10 9:27 ` Stanislaw Gruszka
2011-03-17 15:34 ` Stanislaw Gruszka
2011-03-10 17:40 ` Rafał Miłecki
2011-03-10 18:35 ` Larry Finger [this message]
2011-03-10 10:28 ` Arend van Spriel
2011-03-10 10:56 ` Rafał Miłecki
2011-03-10 11:15 ` Arend van Spriel
2011-03-10 12:59 ` Rafał Miłecki
2011-03-11 14:18 ` Rafał Miłecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7919F1.3070106@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).