From: Johannes Berg <johannes@sipsolutions.net>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] mwl8k: split driver by chipset
Date: Mon, 23 Nov 2009 12:13:09 +0100 [thread overview]
Message-ID: <1258974789.7094.162.camel@johannes.local> (raw)
In-Reply-To: <20091123110211.GS20214@mail.wantstofly.org>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On Mon, 2009-11-23 at 12:02 +0100, Lennert Buytenhek wrote:
> I was wondering if we should really make the support for each chip a
> different kernel module as you did in your patch, but then I figured
> that this might be a good way to let the user choose whether to load
> AP or STA firmware if we have both available, which was still one of
> the unsolved problems. I.e., make mwl8366_ap and mwl8366_sta, and
> then let the user choose which one to load. Or is there a better way
> of doing this?
Try to load both at probe() time (via the async firmware loading
interface that I fixed up recently [1], that patch will be in .33), and
hang on to the firmware images [2]. Register the wiphy with appropriate
bits depending on which firmware files you found (and fail + unbind if
you didn't find any, cf. my ar9170 patch [3]). Then you can upload the
right firmware depending on the type of interface the user is adding.
(Maybe, if needed for EMBEDDED, allow the user to configure which
firmware you load.)
johannes
[1] http://johannes.sipsolutions.net/patches/kernel/all/LATEST/NNN-firmware-class-nowait.patch
[2] that is what my patch allows doing
[3] http://johannes.sipsolutions.net/patches/kernel/all/LATEST/NNN-ar9170-firmware-request-async.patch
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-11-23 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 23:05 [PATCH] mwl8k: split driver by chipset Dan Williams
2009-11-23 5:42 ` Julian Calaby
2009-11-23 11:02 ` Lennert Buytenhek
2009-11-23 11:13 ` Johannes Berg [this message]
2009-11-23 11:29 ` Lennert Buytenhek
2009-11-23 11:34 ` Johannes Berg
2009-11-26 3:25 ` Dan Williams
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=1258974789.7094.162.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=buytenh@wantstofly.org \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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