From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hante Meuleman <meuleman@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@codeaurora.org>,
mailinglist <openwrt-devel@lists.openwrt.org>,
Florian Fainelli <fainelli@broadcom.com>
Subject: Re: [PATCH 10/10] brcmfmac: Add support for multiple PCIE devices in nvram.
Date: Mon, 20 Apr 2015 22:16:29 +0200 [thread overview]
Message-ID: <55355E9D.30209@broadcom.com> (raw)
In-Reply-To: <CACna6ryb_v2Jw1DOudhXvAoQAbjBvdjb_UbdSG_PAC0A=5U9cA@mail.gmail.com>
On 04/20/15 20:49, Rafał Miłecki wrote:
> On 20 April 2015 at 19:12, Arend van Spriel<arend@broadcom.com> wrote:
>> On 04/20/15 13:26, Rafał Miłecki wrote:
>>>
>>> On 17 April 2015 at 10:50, Arend van Spriel<arend@broadcom.com> wrote:
>>>> Another option is to add the parsing stuff in that nvram code and have an
>>>> api to get the appropriate portion based on pcie domain and bus number as
>>>> used in brcmf_fw_get_firmwares_pcie(). However, I would prefer to have
>>>> this
>>>> in the driver and not in arch specific code as there may be other
>>>> platforms
>>>> like our set-top boxes needing this.
>>>
>>>
>>> This is some plan for the future I was lacking from the beginning. It
>>> makes things more clear now, thanks.
>>
>> You're welcome. Do you want to see this clarification in the commit message?
>
> I don't really need that, I'm leaving it up to you :)
>
> The last remaining question from me is if about this NVRAM validation
> function (if it exists).
Ok. I can try to answer that one. The nvram parsing code in firmware.c
intends to do just that. So apart from stripping comments and whitespace
it validates each line and gives off a warning if a wrongly formatted
entry is found.
Regards,
Arend
next prev parent reply other threads:[~2015-04-20 20:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 18:10 [PATCH 00/10] brcmfmac: device support and fixes Arend van Spriel
2015-04-14 18:10 ` [PATCH 01/10] brcmfmac: use static superset of channels for wiphy bands Arend van Spriel
2015-05-09 13:27 ` [01/10] " Kalle Valo
2015-04-14 18:10 ` [PATCH 02/10] brcmfmac: update wiphy band information upon updating regulatory domain Arend van Spriel
2015-04-14 18:10 ` [PATCH 03/10] brcmfmac: add description for feature flags Arend van Spriel
2015-04-14 18:10 ` [PATCH 04/10] brcmfmac: make scheduled scan support conditional Arend van Spriel
2015-04-14 18:10 ` [PATCH 05/10] brcmfmac: add support for BCM4324 rev B5 chipset Arend van Spriel
2015-04-14 18:10 ` [PATCH 06/10] brcmfmac: process interrupt regardless sdiod state Arend van Spriel
2015-04-14 18:10 ` [PATCH 07/10] brcmfmac: fix sdio suspend and resume Arend van Spriel
2015-04-22 7:32 ` Ulf Hansson
2015-04-28 16:14 ` Kalle Valo
2015-04-28 16:50 ` Arend van Spriel
2015-05-04 11:16 ` Ulf Hansson
2015-04-14 18:10 ` [PATCH 08/10] brcmfmac: add support for BCM4358 PCIe device Arend van Spriel
2015-04-14 18:10 ` [PATCH 09/10] brcmfmac: add additional 43602 pcie device id Arend van Spriel
2015-04-14 18:10 ` [PATCH 10/10] brcmfmac: Add support for multiple PCIE devices in nvram Arend van Spriel
2015-04-15 14:52 ` Rafał Miłecki
[not found] ` <F51492713EF10846800D8C0ED37A7DCE019304D6@SJEXCHMB15.corp.ad.broadcom.com>
2015-04-17 7:45 ` Rafał Miłecki
2015-04-17 8:50 ` Arend van Spriel
2015-04-20 11:26 ` Rafał Miłecki
2015-04-20 17:12 ` Arend van Spriel
2015-04-20 18:49 ` Rafał Miłecki
2015-04-20 20:16 ` Arend van Spriel [this message]
2015-04-21 10:16 ` Rafał Miłecki
2015-04-21 10:24 ` Arend van Spriel
2015-04-17 7:55 ` Rafał Miłecki
2015-04-24 8:58 ` Rafał Miłecki
2015-05-09 14:21 ` [PATCH 00/10] brcmfmac: device support and fixes Kalle Valo
2015-05-09 16:29 ` 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=55355E9D.30209@broadcom.com \
--to=arend@broadcom.com \
--cc=fainelli@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=openwrt-devel@lists.openwrt.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).