From: John Talbut <jt@dpets.co.uk>
To: Arend van Spriel <arend@broadcom.com>
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: Thu, 28 Mar 2013 10:03:03 +0000 [thread overview]
Message-ID: <51541557.5050207@dpets.co.uk> (raw)
In-Reply-To: <51531B18.7060909@broadcom.com>
On 27/03/13 16:15, Arend van Spriel wrote:
>> 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.
>
With dependency based booting it would seem to me that it should be
possible to make the creation of this driver dependent on the root
filesystem being mounted. Alternatively the firmware could be included
in the initramfs.
Or the firmware could be incorporated into the driver.
Anyway, thanks for your help, and Rafał and Hauke. I have put the
information at http://wiki.debian.org/brcm80211.
Regards
John
next prev parent reply other threads:[~2013-03-28 10:03 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
2013-03-28 10:03 ` John Talbut [this message]
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=51541557.5050207@dpets.co.uk \
--to=jt@dpets.co.uk \
--cc=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--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).