Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932743AbWANNsH (ORCPT ); Sat, 14 Jan 2006 08:48:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932241AbWANNsH (ORCPT ); Sat, 14 Jan 2006 08:48:07 -0500 Received: from khc.piap.pl ([195.187.100.11]:10511 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S932715AbWANNsF (ORCPT ); Sat, 14 Jan 2006 08:48:05 -0500 To: Johannes Berg Cc: Stuffed Crust , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: wireless: recap of current issues (configuration) References: <20060113195723.GB16166@tuxdriver.com> <20060113212605.GD16166@tuxdriver.com> <20060113213011.GE16166@tuxdriver.com> <20060113221935.GJ16166@tuxdriver.com> <1137191522.2520.63.camel@localhost> <20060114011726.GA19950@shaftnet.org> <1137230889.2520.82.camel@localhost> From: Krzysztof Halasa Date: Sat, 14 Jan 2006 14:47:54 +0100 In-Reply-To: <1137230889.2520.82.camel@localhost> (Johannes Berg's message of "Sat, 14 Jan 2006 10:28:09 +0100") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 569 Lines: 14 Johannes Berg writes: > Yeah, this is about what I thought of -- and it makes me wonder if the > stack really should be aware of the channelization, or if the WiPHY > driver might better just handle it itself. The latter, possibly using library functions from the stack :-) -- Krzysztof Halasa - 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/