linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "John Talbut" <jt@dpets.co.uk>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Hauke Mehrtens" <hauke@hauke-m.de>,
	linux-wireless@vger.kernel.org
Subject: Re: brcmsmac in kernel driver on a Samsung NC110
Date: Wed, 27 Mar 2013 17:15:20 +0100	[thread overview]
Message-ID: <51531B18.7060909@broadcom.com> (raw)
In-Reply-To: <5152E45F.9050003@dpets.co.uk>

On 03/27/2013 01:21 PM, John Talbut wrote:
> 
> 
> On 27/03/13 12:06, Arend van Spriel wrote:
>> On 03/27/2013 12:22 PM, Arend van Spriel wrote:
>>> On 03/27/2013 11:45 AM, John Talbut wrote:
>>>>
>>>>
>>>> On 27/03/13 10:33, Rafał Miłecki wrote:
>>>>> 2013/3/27 John Talbut <jt@dpets.co.uk>:
>>>>>> On 27/03/13 07:46, Rafał Miłecki wrote:
>>>>>>> 2013/3/26 Arend van Spriel <arend@broadcom.com>:
>>>>>>>> On 03/26/2013 08:48 PM, John Talbut wrote:
>>>>>>>>> echo "14e4 4357" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
>>>>>>>>> bash: /sys/bus/pci/drivers/bcma-pci-bridge/new_id: No such file or directory
>>>>>>>>
>>>>>>>> This could mean you do not have CONFIG_BCMA_HOST_PCI=y in your .config
>>>>>>>
>>>>>>> Exactly. Make sure you have CONFIG_BCMA_HOST_PCI=y and that your
>>>>>>> host_pci.c is not modified/hacked/whatever.
>>>>>>>
>>>>>>> You can compare it with
>>>>>>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/bcma/host_pci.c
>>>>>>> bcma_pci_bridge_tbl.
>>>>>>>
>>>>>> OK, thanks, I have recompiled the kernel with CONFIG_BCMA_HOST_PCI=y and
>>>>>> we have some progress.
>>>>>>
>>>>>> ls /sys/bus/bcma/devices
>>>>>> bcma0:0
>>>>>>
>>>>>> lspci -d 14e4: -v
>>>>>> now has a line:
>>>>>> Kernel driver in use: bcma-pci-bridge
>>>>>>
>>>>>> host_pci.c is the same as torvalds.
>>>>>>
>>>>>> However, kernel log includes:
>>>>>> brcmsmac bcma0:0: firmware: agent aborted loading brcm/bcm43xx-0.fw (not
>>>>>> found?)
>>>>>> ieee80211 phy0: brcmsmac: Failed to find firmware usually in
>>>>>> /lib/firmware/brcm
>>>>>> brcmsmac: brcms_bcma_probe: brcms_attach failed!
>>>>>
>>>>> "Failed to find firmware". You didn't tell us if you have firmware installed.
>>>>> ls /lib/firmware/brcm/
>>>>> http://wireless.kernel.org/en/users/Drivers/brcm80211#Firmware_installation
>>>>>
>>>> Sorry, meant to do that:
>>>> ls /lib/firmware/brcm/
>>>> bcm43xx-0.fw bcm43xx_hdr-0.fw
>>>>
>>
>> To confirm my suspicion could you try following (as root):
>>
>> /sys/bus/bcma/drivers/brcmsmac # echo bcma0:0 > bind
>>
>> This should retrigger brcmsmac to get firmware and use the device.
>>
>> Regards,
>> Arend
> 
> Yes.
> cd /sys/bus/bcma/drivers/brcmsmac
> echo bcma0:0 > bind
> 
> And I now have wlan0.
> 
> So, how to get the firmware loaded after the root filesystem is mounted?

You just did. I admit this is a bit tricky way to do it. The driver
would need to be reworked to defer firmware loading, but there is not
clear API. I believe the general recommendation is to attempt firmware
loading upon IFFUP, because you can assume the actual root filesystem is
mounted upon receiving that notification. Let me try to come up with a
patch.

Regards,
Arend


  reply	other threads:[~2013-03-27 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51514F1B.1080207@dpets.co.uk>
     [not found] ` <5151639F.4010700@broadcom.com>
     [not found]   ` <51516BC2.5010004@dpets.co.uk>
     [not found]     ` <515173A4.7030607@broadcom.com>
     [not found]       ` <515179C5.50406@dpets.co.uk>
     [not found]         ` <51517E28.5000303@broadcom.com>
     [not found]           ` <515182C6.5030305@dpets.co.uk>
     [not found]             ` <51518682.7060503@broadcom.com>
     [not found]               ` <515189C6.7070003@dpets.co.uk>
2013-03-26 12:01                 ` brcmsmac in kernel driver on a Samsung NC110 Arend van Spriel
2013-03-26 14:30                   ` John Talbut
2013-03-26 17:01                     ` Rafał Miłecki
2013-03-26 16:59                   ` Rafał Miłecki
2013-03-26 18:43                     ` John Talbut
2013-03-26 19:01                       ` Hauke Mehrtens
2013-03-26 19:48                         ` John Talbut
2013-03-26 22:00                           ` Arend van Spriel
2013-03-27  7:46                             ` Rafał Miłecki
2013-03-27 10:24                               ` John Talbut
2013-03-27 10:33                                 ` Rafał Miłecki
2013-03-27 10:45                                   ` John Talbut
2013-03-27 11:22                                     ` Arend van Spriel
2013-03-27 12:00                                       ` John Talbut
2013-03-27 12:06                                       ` Arend van Spriel
2013-03-27 12:21                                         ` John Talbut
2013-03-27 16:15                                           ` Arend van Spriel [this message]
2013-03-28 10:03                                             ` John Talbut
2013-03-28 11:23                                               ` Arend van Spriel

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=51531B18.7060909@broadcom.com \
    --to=arend@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=jt@dpets.co.uk \
    --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).