From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Hubert Wiedeke <info@stackinside.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Request for brcmfmac4366c-pcie.bin
Date: Wed, 4 Apr 2018 09:38:32 +0200 [thread overview]
Message-ID: <5AC480F8.7060001@broadcom.com> (raw)
In-Reply-To: <20180404051229.f31c6913c9d4d26ae4fb0c1e@stackinside.com>
On 4/4/2018 4:12 AM, Hubert Wiedeke wrote:
> On Mon, 19 Feb 2018 12:51:07 +0100
> Arend van Spriel <arend.vanspriel@broadcom.com> wrote:
>
>> On 2/17/2018 9:19 AM, Hubert Wiedeke wrote:
>>> Hi,
>>>
>>> I'd like to ask about the current status of 4366c firmware preparation for linux-firmware.git . Is it close to finish? What about DFS? Nothing critical, just a question.
>>
>> I have prepared some firmware changes for 4366, but did not manage to
>> get any test-cycles for it.
>>
>> Regards,
>> Arend
>>
>
> Could you please estimate any possible dates for the tested FW to be released?
Not really. Linux open-source work is getting rather low prio when it
comes to claiming test lab resources. Best I can say is somewhere this year.
Regards,
Arend
next prev parent reply other threads:[~2018-04-04 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 8:19 Request for brcmfmac4366c-pcie.bin Hubert Wiedeke
2018-02-19 11:51 ` Arend van Spriel
2018-04-04 2:12 ` Hubert Wiedeke
2018-04-04 7:38 ` Arend van Spriel [this message]
2018-12-07 1:10 ` Hubert Wiedeke
-- strict thread matches above, loose matches on Subject: below --
2018-10-24 13:35 Sebastien Floury
2016-09-12 5:22 Rafał Miłecki
2017-02-23 20:53 ` Rafał Miłecki
2017-02-24 9:07 ` 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=5AC480F8.7060001@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=info@stackinside.com \
--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 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).