linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Franky Lin" <frankyl@broadcom.com>
To: "Thomas Langås" <thomas.langas@fxitech.com>
Cc: "Arend Van Spriel" <arend@broadcom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Howard Harte" <hharte@broadcom.com>
Subject: Re: brcm80211 (with bcm4329-chip)
Date: Mon, 21 Nov 2011 13:58:51 -0800	[thread overview]
Message-ID: <4ECAC99B.8090507@broadcom.com> (raw)
In-Reply-To: <CADrAYB=wDwrzCFEi4-PFepLiLMbPLAGxoaNGtXBaPZPR1onokA@mail.gmail.com>

On 11/21/2011 01:34 PM, Thomas Langås wrote:
> On Mon, Nov 21, 2011 at 10:13 PM, Thomas Langås
> <thomas.langas@fxitech.com>  wrote:
>> Hmm, doing that, and loading this as a module instead of compiling it into the
>> kernel seemed to work.
>>
>> Is there a reason for this not working when being compiled into the kernel? Is
>> it possible that I need to change the order of  some of the units
>> being initialized
>> in my machine-description / init?\

Usually we compile it as module instead of built-in. But I just tried it 
with built-in and it can intialize and scan. Some issue did happen 
during joining  an AP. So I would suggest use module for your 
development for now.

>
> Ok, so I get the device listed as a wlan0-device, and I see the driver
> being able to communicate
> with the chip, sort of (it can read registers at least), but then I
> start seeing errors like this (from
> the previously attached log):

It's possible that the firmware carshed. Are you using the 
firmware/nvram from Linux repository? You should use the nvram that fits 
your platform.

Franky


  reply	other threads:[~2011-11-21 21:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADrAYBnwWEaigcgQYYk6V3VEuEYyrmzJQXegKVk6TgOTPh5N8A@mail.gmail.com>
2011-11-21 17:23 ` brcm80211 (with bcm4329-chip) Arend van Spriel
2011-11-21 18:30   ` Franky Lin
2011-11-21 18:45     ` Thomas Langås
2011-11-21 19:58       ` Franky Lin
2011-11-21 21:13         ` Thomas Langås
2011-11-21 21:34           ` Thomas Langås
2011-11-21 21:58             ` Franky Lin [this message]
2011-11-21 22:26               ` Thomas Langås
2011-11-21 22:48                 ` Franky Lin
2011-11-21 23:40                   ` Thomas Langås
2011-11-21 23:42                     ` Howard Harte
2011-11-21 23:50                       ` Thomas Langås
2011-11-21 23:56                         ` Franky Lin
2011-11-22  0:00                           ` Thomas Langås
2011-11-22  0:13                             ` Franky Lin
2011-11-22  0:22                               ` Thomas Langås
2011-11-21 18:47   ` Thomas Langås

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=4ECAC99B.8090507@broadcom.com \
    --to=frankyl@broadcom.com \
    --cc=arend@broadcom.com \
    --cc=hharte@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=thomas.langas@fxitech.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).