From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-fx0-f221.google.com ([209.85.220.221]:53162 "EHLO mail-fx0-f221.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754573AbZKIIQl (ORCPT ); Mon, 9 Nov 2009 03:16:41 -0500 Received: by fxm21 with SMTP id 21so56494fxm.21 for ; Mon, 09 Nov 2009 00:16:45 -0800 (PST) Date: Mon, 09 Nov 2009 09:16:19 +0100 Message-ID: From: Holger Schurig To: Jan Kiszka Cc: Kalle Valo , linux-wireless@vger.kernel.org Subject: Re: ar9170 in AP mode In-Reply-To: <4AF6CC02.8080204@web.de> References: <4AF6C7CD.7060108@web.de> <878wehf85v.fsf@purkki.valot.fi> <4AF6CC02.8080204@web.de> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: > How common is the combination of powersaving and mcast in practice? > Given that quite a few useful scenarios are blocked right now (unless > you know what to patch), I would at least vote for a config option or a > module parameter. That gives a chance to warn the user about this > limitation without locking out people that are no hackers. In my case (hand-help devices) it's very common. Without power-save, the battery would be drained so fast it wouldn't be usable. And with power-save and an AP that can't handle this, you'd get weird errors. 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 :-) -- http://www.holgerschurig.de