All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Rami Rosen <ramirose@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kune@deine-taler.de" <kune@deine-taler.de>,
	Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH ] zd1211rw: enable master mode. (wireless-testing)
Date: Thu, 20 Nov 2008 16:33:59 +0100	[thread overview]
Message-ID: <200811201633.59986.mb@bu3sch.de> (raw)
In-Reply-To: <20081119211600.GE5900@tesla>

On Wednesday 19 November 2008 22:16:00 Luis R. Rodriguez wrote:
> On Wed, Nov 19, 2008 at 01:00:46PM -0800, Luis Rodriguez wrote:
> > On Wed, Nov 19, 2008 at 12:30:19PM -0800, Johannes Berg wrote:
> > > On Wed, 2008-11-19 at 11:01 -0500, John W. Linville wrote:
> > >
> > > > Is there some way we could take that into account?  I'm sure there
> > > > are users who would prefer to have an AP (i.e. their laptop) that
> > > > can't support PS clients rather than not having an AP at all.
> > >
> > > That's a good question. The distinction here is between empowering users
> > > to do the wrong thing (AP without proper PS support) and enforcing the
> > > right thing (with the consequence of complete loss of AP functionality).
> > > The issue I see here is that users will see "ohh shiny, AP support"
> > > without knowing that it doesn't actually really support it. Not sure
> > > which side of the line we want to stand on, I prefer the correctness
> > > side but I can see arguments for the other side, would just like to have
> > > users know. Maybe we could have some way to tell hostapd this and then
> > > have hostapd print a huge warning about it when started up?
> > 
> > How about making it Kconfigable for broken AP support and add the
> > warning there?
> 
> That is have something like CONFIG_MAC80211_AP_HALF_ASSED

This is not acceptable, IMO, because distros will always enable it and users
still won't know about it.
We want _users_ to know.
So the idea of letting hostapd print a huge message is not that bad.

-- 
Greetings Michael.

  reply	other threads:[~2008-11-20 15:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 15:51 [PATCH ] zd1211rw: enable master mode. (wireless-testing) Rami Rosen
2008-11-17 17:40 ` Johannes Berg
2008-11-19 13:59   ` Rami Rosen
2008-11-19 14:49     ` Johannes Berg
2008-11-19 15:09       ` Rami Rosen
2008-11-19 15:17         ` Johannes Berg
2008-11-19 16:01           ` John W. Linville
2008-11-19 20:30             ` Johannes Berg
2008-11-19 21:00               ` Luis R. Rodriguez
2008-11-19 21:16                 ` Luis R. Rodriguez
2008-11-20 15:33                   ` Michael Buesch [this message]
2008-11-19 21:18                 ` John W. Linville
2008-11-20  6:37                   ` Johannes Berg
2008-11-20  8:27               ` Jouni Malinen
2008-11-20 17:52                 ` Johannes Berg

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=200811201633.59986.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=kune@deine-taler.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=ramirose@gmail.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.