Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751125AbWAOEmf (ORCPT ); Sat, 14 Jan 2006 23:42:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751316AbWAOEme (ORCPT ); Sat, 14 Jan 2006 23:42:34 -0500 Received: from mx1.redhat.com ([66.187.233.31]:37071 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1751102AbWAOEmd (ORCPT ); Sat, 14 Jan 2006 23:42:33 -0500 Date: Sat, 14 Jan 2006 20:42:11 -0800 From: Pete Zaitcev To: Ulrich Kunitz Cc: linville@tuxdriver.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, zaitcev@redhat.com, Subject: Re: wireless: recap of current issues (stack) Message-Id: <20060114204211.72942d45.zaitcev@redhat.com> In-Reply-To: References: <20060113195723.GB16166@tuxdriver.com> <20060113212605.GD16166@tuxdriver.com> <20060113213200.GG16166@tuxdriver.com> Organization: Red Hat, Inc. X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 19 On Sat, 14 Jan 2006 15:13:39 +0100 (CET), Ulrich Kunitz wrote: > [...] Register accesses in USB devices should be > able to sleep. However the 80211 stacks I've seen so far have a > fixed set of capabilities and do also assume, that at the driver > layer everything can be done in atomic mode, which is only true > for buses that support memory-mapping. If this problem is real, then it's serious. However, I'm not seeing it with prism54usb and Berg's softmac (yet?). Would you be so kind to provide the file name and function name for the code which makes these assumptions? Thanks, -- Pete - 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/