All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: ath9k-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] ath9k_htc: introduce support for different fw versions
Date: Sun, 06 Sep 2015 16:16:31 +0300	[thread overview]
Message-ID: <87bndfhemo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <55EC1D0B.6090707@rempel-privat.de> (Oleksij Rempel's message of "Sun, 06 Sep 2015 13:01:31 +0200")

Oleksij Rempel <linux@rempel-privat.de> writes:

>>> At same time this patch will add new module option which should allow
>>> user to play with development fw version without replacing stable one.
>>> If user will set “ath9k_htc use_dev_fw=1” module will try to find
>>> firmware/ath9k_htc/htc_[9271|7010]-1.dev.0.fw first and if it fails,
>>> use stable version: for example...1.4.0.fw.
>> 
>> I'm not really sure if this module parameter makes sense and I haven't
>> noticed any other wifi driver having a similar parameter. If user wants
>> to test a developemnt firmware he can override a stable firmware version
>> with a simple cp operation. So why is the module parameter needed?
>
> Sure, iwl module has CONFIG for this case, so you should recompile it.

Yeah, that's even worse.

> The use case which i was thinking is the ability to provide a package
> for dev FW, which will not conflict with main FW package.
>
> The package just should provide 3 files, /etc/modules/ath9k_htc_params
> and /lib/firmware/bla.fw
> If dev package introduces some regressions i still can ask user to
> reload module with other parameter.

I think this should be doable even without a module parameter, but I
guess the module parameter is ok then.

-- 
Kalle Valo

      reply	other threads:[~2015-09-06 13:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 16:12 [PATCH] ath9k_htc: introduce support for different fw versions Oleksij Rempel
2015-06-14 23:27 ` Julian Calaby
2015-06-15 18:55   ` Oleksij Rempel
2015-06-15 18:57   ` Oleksij Rempel
2015-06-15 18:58   ` [PATCH v2] " Oleksij Rempel
2015-07-03  4:07     ` Oleksij Rempel
2015-07-03 10:53       ` Kalle Valo
2015-07-03 17:43         ` Oleksij Rempel
2015-07-12 12:17     ` Kalle Valo
2015-07-12 17:42       ` [PATCH v3] " Oleksij Rempel
2015-08-14  5:12       ` Oleksij Rempel
2015-09-06 10:55         ` Kalle Valo
2015-09-06 11:01           ` Oleksij Rempel
2015-09-06 13:16             ` Kalle Valo [this message]

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=87bndfhemo.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    /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.