All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Holger Schurig <holgerschurig@googlemail.com>,
	Jan Kiszka <jan.kiszka@web.de>,
	linux-wireless@vger.kernel.org
Subject: Re: ar9170 in AP mode
Date: Mon, 9 Nov 2009 09:14:59 -0500	[thread overview]
Message-ID: <20091109141458.GA2805@tuxdriver.com> (raw)
In-Reply-To: <87ocncdrfz.fsf@purkki.valot.fi>

On Mon, Nov 09, 2009 at 10:37:36AM +0200, Kalle Valo wrote:
> Holger Schurig <holgerschurig@googlemail.com> writes:

> > So, I personally prefer to have "Do an AP right" or "Don't do it at
> > all". But please no general enablement.
> >
> > But, for example, having some CONFIG_AR9K_AP_MODE depending on
> > CONFIG_EXPERIMENTAL and a bit fat warning would do for me. Hopefully
> > this would scara away distros, so that they don't turn this on for
> > there standard kernel :-)
> 
> I think EXPERIMENTAL is not enough, I would prefer that the user needs
> to patch the driver to enable it. Or if that's not good enough, then
> maybe depend on BROKEN.

Here we go again... :-)

So I definitely agree that it should be off by default.  I also agree
that it should be difficult to turn it on accidentally.  We don't
need any extra wierd bug reports.

OTOH, I think we can all acknowledge that many people have reasonable
use cases with their fleet of equipment.  I wonder if a sysctl would
be enough of a deterrent?  They are fairly simple to turn-on, but
you do have to know about them to do so...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-11-09 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 13:29 ar9170 in AP mode Jan Kiszka
2009-11-08 13:38 ` Kalle Valo
2009-11-08 13:47   ` Jan Kiszka
2009-11-08 14:01     ` Johannes Berg
2009-11-08 14:40       ` Jan Kiszka
2009-11-08 14:56         ` Johannes Berg
2009-11-09  8:16     ` Holger Schurig
2009-11-09  8:37       ` Kalle Valo
2009-11-09 14:14         ` John W. Linville [this message]
2009-11-09 21:09           ` Jan Kiszka
2009-11-10 10:39             ` Johannes Berg
2009-11-09 18:52         ` Jeffrey Baker
2009-11-09 19:49           ` Luis R. Rodriguez

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=20091109141458.GA2805@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=holgerschurig@googlemail.com \
    --cc=jan.kiszka@web.de \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    /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.