From: Kalle Valo <kvalo@codeaurora.org>
To: amit karwar <amitkarwar@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
Amitkumar Karwar <amit.karwar@redpinesignals.com>
Subject: Re: [v3 10/11] rsi: Add new firmware loading method
Date: Fri, 26 May 2017 18:25:41 +0300 [thread overview]
Message-ID: <87inknprm2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAEhWJFnaG4xC71CL_ayYEyGg0HMNoyHK7aE9gcGAmsako8Q9Tw@mail.gmail.com> (amit karwar's message of "Fri, 26 May 2017 20:40:11 +0530")
amit karwar <amitkarwar@gmail.com> writes:
> On Wed, May 24, 2017 at 1:57 PM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Amitkumar Karwar <amitkarwar@gmail.com> writes:
>>
>>> From: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
>>>
>>> The older firmware loading method has been deprecated and not in use
>>> for any chipets. New method is introduced which works based on soft
>>> boot loader. In this method, complete RAM image and FLASH image are
>>> present in the flash. Before loading the functional firmware, host
>>> issues boot loader commands to verify whether firmware to load is
>>> different from the current functional firmware. If not, firmware
>>> upgrade progresses and boot loader will switch to the new functional
>>> firmware.
>>>
>>> "rs9113_wlan_qspi.rps" is the firmware filename used in this patch.
>>
>> I don't know if you saw the discussion with the wil6210 firmware, but
>> the linux-firmware maintainers prefer to have a subdirectory for
>> firmware files. I'm planning to apply this series now, but you can send
>> a followup patch ASAP which changes the rsi driver to use a subdirectory
>> for the firmware files?
>
> I have just sent a follow up patch.
Thanks, I saw that. Will apply it shortly.
--
Kalle Valo
next prev parent reply other threads:[~2017-05-26 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 10:01 [v3 00/11] Firmware loading changes Amitkumar Karwar
2017-05-16 10:01 ` [v3 01/11] rsi: Rename file rsi_91x_pkt.c to rsi_91x_hal.c Amitkumar Karwar
2017-05-24 13:39 ` [v3,01/11] " Kalle Valo
2017-05-16 10:01 ` [v3 02/11] rsi: Changes to sdio reads and writes Amitkumar Karwar
2017-05-16 10:01 ` [v3 03/11] rsi: define RSI_USB_BUF_SIZE macro Amitkumar Karwar
2017-05-16 10:01 ` [v3 04/11] rsi: Changes in USB read and write operations Amitkumar Karwar
2017-05-16 10:01 ` [v3 05/11] rsi: use macros in USB specific code Amitkumar Karwar
2017-05-16 10:01 ` [v3 06/11] rsi: Handle usb multi-byte write failure case properly Amitkumar Karwar
2017-05-16 10:01 ` [v3 07/11] rsi: Add usb multi-byte read operation Amitkumar Karwar
2017-05-16 10:01 ` [v3 08/11] rsi: Add host interface operations as separate structure Amitkumar Karwar
2017-05-16 10:01 ` [v3 09/11] rsi: Add new host interface operations Amitkumar Karwar
2017-05-16 10:01 ` [v3 10/11] rsi: Add new firmware loading method Amitkumar Karwar
2017-05-24 8:27 ` Kalle Valo
2017-05-26 15:10 ` amit karwar
2017-05-26 15:25 ` Kalle Valo [this message]
2017-05-16 10:01 ` [v3 11/11] rsi: Remove old " Amitkumar Karwar
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=87inknprm2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=amit.karwar@redpinesignals.com \
--cc=amitkarwar@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=prameela.j04cs@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).