From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"Stanislaw Gruszka" <sgruszka@redhat.com>,
"Gábor Stefanik" <netrolller.3d@gmail.com>
Subject: Re: Problem with BCM943224
Date: Wed, 09 Mar 2011 12:44:08 -0600 [thread overview]
Message-ID: <4D77CA78.3080401@lwfinger.net> (raw)
In-Reply-To: <AANLkTinEC5b6-vP_zc2RE2Juc8YFx8nkEK7isvQw+UVX@mail.gmail.com>
On 03/09/2011 12:04 PM, Rafał Miłecki wrote:
>
> 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. Do
> you think such a boards would be compatible with Broadcom's cards?
I have a system with an Atom processor and one with an AMD 450 MHz CPU. I do not
try to build kernels on either of them. I have their sources on a 2.4 GHz
dual-core machine in an NFS-exported volume. I cross-build for i386 as the host
is 64 bits and only do the "make modules_install install" on the target
machines. It works quite well.
Larry
next prev parent reply other threads:[~2011-03-09 18:50 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 [this message]
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
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=4D77CA78.3080401@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=sgruszka@redhat.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).