Return-path: Received: from mail-ew0-f207.google.com ([209.85.219.207]:37704 "EHLO mail-ew0-f207.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751361AbZKDUL6 convert rfc822-to-8bit (ORCPT ); Wed, 4 Nov 2009 15:11:58 -0500 Received: by ewy3 with SMTP id 3so3516160ewy.37 for ; Wed, 04 Nov 2009 12:12:02 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <43e72e890911041204n55b54f8iace79938b40baa32@mail.gmail.com> References: <43e72e890911041204n55b54f8iace79938b40baa32@mail.gmail.com> Date: Wed, 4 Nov 2009 22:12:02 +0200 Message-ID: <40f31dec0911041212p16cfc78eia1ab1817e425e767@mail.gmail.com> Subject: Re: pci_set_mwi() and ath5k From: Nick Kossifidis To: "Luis R. Rodriguez" Cc: linux-wireless , ath5k-devel@lists.ath5k.org, Matthew Wilcox , Stephen Hemminger Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 2009/11/4 Luis R. Rodriguez : > Curious if anyone recalls the issues seen with enabling MWI on ath5k. > I could have sworn there was some discussion on this but for the life > of me I cannot find it. > >  Luis Maybe this one ? http://osdir.com/ml/linux.drivers.ath5k.devel/2008-07/msg00088.html -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick