From: Erik Stromdahl <erik.stromdahl@gmail.com> To: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Cc: Erik Stromdahl <erik.stromdahl@gmail.com> Subject: [RFC v2 2/3] ath10k: different fw file names for usb Date: Sat, 20 May 2017 22:33:29 +0200 [thread overview] Message-ID: <1495312410-9937-3-git-send-email-erik.stromdahl@gmail.com> (raw) In-Reply-To: <1495312410-9937-1-git-send-email-erik.stromdahl@gmail.com> USB firmware will be named in the same way as SDIO files, i.e, the bus type will be added to the firmware file name. Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com> --- drivers/net/wireless/ath/ath10k/core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c index eea111d..46ce263 100644 --- a/drivers/net/wireless/ath/ath10k/core.c +++ b/drivers/net/wireless/ath/ath10k/core.c @@ -1412,6 +1412,7 @@ static void ath10k_core_get_fw_name(struct ath10k *ar, char *fw_name, { switch (ar->hif.bus) { case ATH10K_BUS_SDIO: + case ATH10K_BUS_USB: scnprintf(fw_name, fw_name_len, "%s-%s-%d.bin", ATH10K_FW_FILE_BASE, ath10k_bus_str(ar->hif.bus), fw_api); -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Erik Stromdahl <erik.stromdahl@gmail.com> To: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Cc: Erik Stromdahl <erik.stromdahl@gmail.com> Subject: [RFC v2 2/3] ath10k: different fw file names for usb Date: Sat, 20 May 2017 22:33:29 +0200 [thread overview] Message-ID: <1495312410-9937-3-git-send-email-erik.stromdahl@gmail.com> (raw) In-Reply-To: <1495312410-9937-1-git-send-email-erik.stromdahl@gmail.com> USB firmware will be named in the same way as SDIO files, i.e, the bus type will be added to the firmware file name. Signed-off-by: Erik Stromdahl <erik.stromdahl@gmail.com> --- drivers/net/wireless/ath/ath10k/core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c index eea111d..46ce263 100644 --- a/drivers/net/wireless/ath/ath10k/core.c +++ b/drivers/net/wireless/ath/ath10k/core.c @@ -1412,6 +1412,7 @@ static void ath10k_core_get_fw_name(struct ath10k *ar, char *fw_name, { switch (ar->hif.bus) { case ATH10K_BUS_SDIO: + case ATH10K_BUS_USB: scnprintf(fw_name, fw_name_len, "%s-%s-%d.bin", ATH10K_FW_FILE_BASE, ath10k_bus_str(ar->hif.bus), fw_api); -- 2.7.4 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-05-20 20:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-20 20:33 [RFC v2 0/3] ath10k usb support Erik Stromdahl 2017-05-20 20:33 ` Erik Stromdahl 2017-05-20 20:33 ` [RFC v2 1/3] ath10k: various usb related definitions Erik Stromdahl 2017-05-20 20:33 ` Erik Stromdahl 2017-05-20 20:33 ` Erik Stromdahl [this message] 2017-05-20 20:33 ` [RFC v2 2/3] ath10k: different fw file names for usb Erik Stromdahl 2017-05-20 20:33 ` [RFC v2 3/3] ath10k: add initial USB support Erik Stromdahl 2017-05-20 20:33 ` Erik Stromdahl 2017-07-06 9:17 ` [RFC v2 0/3] ath10k usb support Kalle Valo 2017-07-06 9:17 ` Kalle Valo
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=1495312410-9937-3-git-send-email-erik.stromdahl@gmail.com \ --to=erik.stromdahl@gmail.com \ --cc=ath10k@lists.infradead.org \ --cc=kvalo@qca.qualcomm.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: linkBe 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.