From: John Talbut <jt@dpets.co.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: Firmware loading with static kernel and initramfs
Date: Mon, 30 Jun 2014 06:09:33 +0100 [thread overview]
Message-ID: <53B0F10D.7030801@dpets.co.uk> (raw)
In-Reply-To: <53B08F07.3000308@lwfinger.net>
On 29/06/14 23:11, Larry Finger wrote:
> On 06/29/2014 02:19 PM, John Talbut wrote:
>> I originally had the problem with a Broadcom BCM43225 wireless. This
>> was with a
>> 3.8 kernel. This was solved by a patch to the kernel brcmsmac driver
>> and this
>> is still working with a 3.14 kernel.
>
> What sort of patch was that? Driver brcmsmac is still using
> request_firmware().
I believe it was this patch:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c?id=25b5632fb35ca61b8ae3eee235edcdc2883f7a5e
>
>> Currently I have the problem with an Intel Centrino Wireless-N 130.
>> The problem
>> was present with a 3.11 kernel and currently with a 3.14 kernel. udev
>> version
>> 204-5linuxmint.
>
> The current Intel drivers all use request_firmware_nowait(), but I'm not
> sure when they were changed.
>
>> A friend seems to have the problem with a Realtek 8129se wireless but
>> we are
>> still checking out that this is the problem.
>
> To my knowledge, there is no Realtek 8129se driver. Do you mean
> rtl8192se? If so, that one has used request_firmware_nowait() for some
> time.
Yes, the rtl8192se driver.
John
next prev parent reply other threads:[~2014-06-30 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 17:15 Firmware loading with static kernel and initramfs John Talbut
2014-06-29 18:31 ` Larry Finger
2014-06-29 19:19 ` John Talbut
2014-06-29 22:11 ` Larry Finger
2014-06-30 5:09 ` John Talbut [this message]
2014-06-30 8:22 ` Arend van Spriel
2014-06-30 9:08 ` John Talbut
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=53B0F10D.7030801@dpets.co.uk \
--to=jt@dpets.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.