From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1753941AbZELNXW@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753941AbZELNXW (ORCPT <rfc822;w@1wt.eu>);
	Tue, 12 May 2009 09:23:22 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751274AbZELNXL
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 12 May 2009 09:23:11 -0400
Received: from smtp28.orange.fr ([80.12.242.101]:42449 "EHLO smtp28.orange.fr"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751095AbZELNXK (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 12 May 2009 09:23:10 -0400
X-ME-UUID: 20090512132309671.A3EBB80000AE@mwinf2823.orange.fr
Subject: Re: [madwifi-project] Death to MadWifi!
From: Xavier Bestel <xavier.bestel@free.fr>
To: Bob Copeland <me@bobcopeland.com>
Cc: Frans Pop <elendil@planet.nl>, "Luis R. Rodriguez" <mcgrof@gmail.com>,
       p0g0@madwifi-project.org, madwifi-project@venema.h4ckr.net,
       Cliff.Holden@atheros.com, mb@bu3sch.de, nbd@openwrt.org,
       mickflemm@gmail.com, proski@gnu.org, juhosg@openwrt.org,
       linux-kernel@vger.kernel.org
In-Reply-To: <20090512123826.GA19410@hash.localnet>
References: <43e72e890905111627r54fd4fa4r26d9511c1fd625a2@mail.gmail.com>
	 <4A0908AB.1070606@madwifi-project.org>
	 <4A0908AB.1070606@madwifi-project.org>
	 <43e72e890905112332j3e32fb8q942fb75f882b2384@mail.gmail.com>
	 <200905121114.24355.elendil@planet.nl>
	 <20090512123826.GA19410@hash.localnet>
Content-Type: text/plain
Date: Tue, 12 May 2009 15:22:33 +0200
Message-Id: <1242134553.2139.25.camel@skunk>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.3) 
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 2009-05-12 at 08:38 -0400, Bob Copeland wrote:
> For what it is worth, I find it rather counter-productive when people on
> irc suggest using ath5k to solve every madwifi problem, for example, for
> AP mode, which clearly isn't enabled in even 2.6.30 and has bugs with the
> TIM in the wireless-testing kernel[1].  That sort of thing just leads to
> pissed off users.

I'm one of them. Hours dealing with hostapd and ath5k, and then
realizing that AP mode just isn't there.
It'll be a while before I'll try it again, even if madwifi has its own
ways of pissing me off.

	Xav