public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
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:34:41 +0100	[thread overview]
Message-ID: <1258976081.7094.164.camel@johannes.local> (raw)
In-Reply-To: <20091123112916.GT20214@mail.wantstofly.org>

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

On Mon, 2009-11-23 at 12:29 +0100, Lennert Buytenhek wrote:

> This has the problem that e.g. if someone creates a STA interface first,
> and we load the STA firmware image in response to that, and then creates
> an additional AP interface, we'd have reload the chip while there's
> still an active interface (the original STA one), which seems somewhat
> involved.  Just rejecting the second add_interface() seems undesirable,
> as then the outcome of two add_interface() calls will depend on their
> order.
> 
> (AP firmware supports both AP and STA interfaces, but e.g. it doesn't
> do STA power save and such.)
> 
> It'll also have some consequences if there are monitor interfaces, as
> e.g. STA firmware allows fine-grained control over the receive filter,
> while the AP firmware does not.

Hah well in that case it won't really work because you really shouldn't
change capabilities on the fly. I have no useful idea then, sorry.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-11-23 11:34 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
2009-11-23 11:29     ` Lennert Buytenhek
2009-11-23 11:34       ` Johannes Berg [this message]
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=1258976081.7094.164.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