From: "John W. Linville" <linville@tuxdriver.com>
To: Jouni Malinen <j@w1.fi>
Cc: "Kalle Valo" <kalle.valo@iki.fi>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Hin-Tak Leung" <hintak.leung@gmail.com>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
"Stefan Steuerwald" <salsasepp@googlemail.com>,
linux-wireless@vger.kernel.org
Subject: Re: Testing AP mode with WLAN-USB-Stick: How to obtain?
Date: Wed, 10 Jun 2009 15:58:57 -0400 [thread overview]
Message-ID: <20090610195857.GF3892@tuxdriver.com> (raw)
In-Reply-To: <20090610192825.GA23353@jm.kir.nu>
On Wed, Jun 10, 2009 at 10:28:25PM +0300, Jouni Malinen wrote:
> I don't like the idea of making hostapd warn the user somehow, but could
> probably live with something like AP mode being implemented in the
> driver, but disabled by default. Only if the user were to use a module
> parameter, say, broken_ap_mode=1, would the support for AP mode be
> registered. As long as distros do not start adding this parameter by
> default, this would force the user to become at least somehow informed
> about the issues and make a conscious choice in enabling the mode.
I would probably lean the other way -- let the driver expose the fact
that his AP mode is dysfunctional, and require hostap to say it is OK
to use it. Then again, it is the kind of thing that a user will say
"OK" and then go on to file bug reports about the problems created
by broken AP mode drivers...
Like I said, "on the fence"... :-)
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-06-10 20:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f76a32050906081007q19e9361w8c1fad6fc73c47e7@mail.gmail.com>
2009-06-08 17:11 ` Testing AP mode with WLAN-USB-Stick: How to obtain? Stefan Steuerwald
2009-06-08 20:19 ` Chi-Thanh Christopher Nguyen
2009-06-08 23:59 ` Hin-Tak Leung
2009-06-09 11:26 ` Gábor Stefanik
2009-06-10 3:18 ` Hin-Tak Leung
2009-06-10 7:30 ` Johannes Berg
2009-06-10 11:31 ` John W. Linville
2009-06-10 19:19 ` Kalle Valo
2009-06-10 19:28 ` Jouni Malinen
2009-06-10 19:36 ` Kalle Valo
2009-06-10 19:40 ` Gábor Stefanik
2009-06-10 19:58 ` John W. Linville [this message]
2009-06-10 19:55 ` John W. Linville
2009-06-10 13:39 ` Hin-Tak Leung
2009-06-10 15:22 ` Gábor Stefanik
2009-06-10 15:49 ` Johannes Berg
2009-06-10 15:51 ` Johannes Berg
2009-06-10 19:28 ` Kalle Valo
2009-06-11 3:08 ` Hin-Tak Leung
2009-06-11 3:51 ` Luis R. Rodriguez
2009-06-11 9:59 ` Johannes Berg
2009-06-11 14:42 ` Gábor Stefanik
2009-06-09 8:19 ` Jon Fairbairn
2009-06-09 9:16 ` Alexandre Becholey - s h o c k f i s h /
2009-06-11 14:58 Joerg Pommnitz
2009-06-11 15:06 ` Gábor Stefanik
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=20090610195857.GF3892@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hintak.leung@gmail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=salsasepp@googlemail.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;
as well as URLs for NNTP newsgroup(s).