From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Gábor Stefanik" <netrolller.3d@gmail.com>
Subject: Re: Problem with BCM943224
Date: Thu, 10 Mar 2011 10:27:54 +0100 [thread overview]
Message-ID: <20110310092753.GA2323@redhat.com> (raw)
In-Reply-To: <AANLkTinEC5b6-vP_zc2RE2Juc8YFx8nkEK7isvQw+UVX@mail.gmail.com>
On Wed, Mar 09, 2011 at 07:04:01PM +0100, Rafał Miłecki wrote:
> Do you think buying some more expensive adapter could help? The newest
> offered by hwtools seems to be:
> http://www.hwtools.net/Adapter/MP2H.html
> (ver 2.2). It is not so expensive at all, $15 without shipping.
>
> I've already written to them with question about BCM943224
> compatibility (they don't have that chipset on their list).
>
> Stanisław: I remember you telling that you have such a adapter. Do you
> maybe have access to some BCM943224/BCM94313 card? Could you test that
> combo for me, please?
I have new laptop at home with some bcm device, don't know exacly what
version, but most likely is somehting that you listed or similar. I'll
test and let you now next week. I planned to replace wireless adapter
on that laptop anyway.
> The only other solution I can see is to buy motherboard with mini PCIe
> slot. There are some *D410P* (BLKD410PT, BOXD410PT, BLKD410PTL,
> D410PT) and D510MO having such a slow (and Atom CPU.... :/). Kernel
> compilation would be disaster but I think I could live with that.
If you configure out all unnedded drivers/features, compilation time
should not be so bad.
> Do
> you think such a boards would be compatible with Broadcom's cards?
I think any miniPCIe host should be compatibile with any miniPCIe device.
Cheers
Stanislaw
next prev parent reply other threads:[~2011-03-10 9:29 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 [this message]
2011-03-17 15:34 ` Stanislaw Gruszka
2011-03-10 17:40 ` Rafał Miłecki
2011-03-10 18:35 ` Larry Finger
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=20110310092753.GA2323@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--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).