From: Christian Lamparter <chunkeey@googlemail.com>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] wireless: Driver for 60GHz card wil6210
Date: Wed, 31 Oct 2012 18:25:36 +0100 [thread overview]
Message-ID: <201210311825.37192.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAB=NE6WRG9yYV=NLORnEEHSkgfjBSdZr_pycLCmCN2cRUFvQKw@mail.gmail.com>
On Wednesday 31 October 2012 16:14:19 Luis R. Rodriguez wrote:
> On Wed, Oct 31, 2012 at 5:57 AM, Vladimir Kondratiev
> <qca_vkondrat@qca.qualcomm.com> wrote:
> > By the way, Atheros driver carl9170 uses MODULE_VERSION,
> > should we consider killing it?
>
> Well its tied pretty heavily to the firmware which BTW is open and
> GPLv2. Your driver does not need firmware (yet). Why exactly carl9170
> would use MODULE_VERSION though... or need it.. is perhaps Christian
> can clarify on. Christian any reason to have MODULE_VERSION(),
> anything that provide to userspace that cannot be obtained by the
> kernel release it came from instead?
Well, to make the api level of the firmware interface which
is used by the driver accessible through modinfo without
having to load the module. So a script check whenever the
api matches by testing modinfo of the driver and fwinfo
of the fw.
However, this information is also printed out when the
firmware is loaded/parsed.
[ 150.588563] usb 1-10: driver API: 1.9.6 2012-07-07 [1-1]
[ 150.594360] usb 1-10: firmware API: 1.9.6 2012-07-07
So, it's only really useful if you need to know in advance
or in absence of a device. [So, it's not very useful in
most cases]
If you want to make a patch to remove it: here is my
Acked-by: Christian Lamparter <chunkeey@googlemail.com>
[Also, if you remove it, you can kill the ugly #defines
which are used by it too]
Regards,
Chr
next prev parent reply other threads:[~2012-10-31 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 11:58 [PATCH v2 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-10-29 11:58 ` [PATCH v2 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-10-31 1:23 ` Luis R. Rodriguez
2012-10-31 12:57 ` Vladimir Kondratiev
2012-10-31 13:03 ` Luis R. Rodriguez
2012-10-31 14:27 ` Johannes Berg
2012-10-31 15:00 ` Vladimir Kondratiev
2012-10-31 15:04 ` Johannes Berg
2012-10-31 15:14 ` Luis R. Rodriguez
2012-10-31 17:25 ` Christian Lamparter [this message]
2012-10-31 18:53 ` Luis R. Rodriguez
2012-10-31 14:29 ` Gábor Stefanik
2012-10-31 14:52 ` Vladimir Kondratiev
2012-10-29 11:58 ` [PATCH v2 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev
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=201210311825.37192.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.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 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.