Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932608AbVLFPEf (ORCPT ); Tue, 6 Dec 2005 10:04:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751691AbVLFPEf (ORCPT ); Tue, 6 Dec 2005 10:04:35 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:6635 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S1751681AbVLFPEe (ORCPT ); Tue, 6 Dec 2005 10:04:34 -0500 Date: Tue, 6 Dec 2005 16:04:16 +0100 From: Pavel Machek To: Jiri Benc Cc: Christoph Hellwig , Joseph Jezak , mbuesch@freenet.de, linux-kernel@vger.kernel.org, bcm43xx-dev@lists.berlios.de, NetDev Subject: Re: Broadcom 43xx first results Message-ID: <20051206150416.GA1999@elf.ucw.cz> References: <20051205190038.04b7b7c1@griffin.suse.cz> <4394892D.2090100@gentoo.org> <20051205195543.5a2e2a8d@griffin.suse.cz> <20051205191008.GA28433@infradead.org> <20051205203121.48241a08@griffin.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051205203121.48241a08@griffin.suse.cz> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1713 Lines: 38 Hi! > > Please stop beeing a freaking jackass. There are various projects using > > the current code. It's not perfect but people are working on it. > > Yes, and everyone implements his own softmac (this is the third one I > know about). I tried to put all of these efforts together (google > through the netdev archives) and wrote many patches. Well, unfortunately people seem to disagree about "what the right softmac is". And James's code is in kernel, thats _huge_ advantage. > > And please stop your stupid devicespace advertisements. If you think the > > code is so useful why don't you send patches to integrate it with the > > currently existing wireless code (after cleaning up the horrible mess > > it is currently)? > > This is what I'm doing last two months. But it's not so easy to clean it > up and it seems that nobody else is interested. But it has all of the > features you need (except active scanning) - this is the reason I > stopped to work on improving current in-kernel 802.11 code and focused > on Devicescape's code. It is several years beyond the state that current > code is at now. And it is not an advertisement, it is a fact. Another fact is that it is not in kernel, and by the time you get it cleaned up, in-kernel code will probably get advanced enough that your code will not be merged. If devicescape is really so much better, submit it _now_. It may be slightly buggy, but so is probably current code. -- Thanks, Sharp! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/